Even with it attempting to be tab-specific, it still often doesn’t work and is buggy for me.
I think many users would like the option for it to simply function as a program-wide back button, with one consolidated history for all tabs. Couldn’t it simply remember the tab that each “page” was open in, and bring the user to that tab to show the page when using Back/Forward?
I disagree… You are producing a product… that product should meet the expectations (as closely as possilbe) of your clients…Just because Safari does it makes it a GOOD thing? A web browser and and IDE are totally different… and as such should act appropriately. XOJO needs to begin LISTENING to their clients… if they say something is “wrong”, then perhaps they have a reason for saying that… XOJO is in business to make money… We all realize that, and would be stupid to thing otherwise. By the same token, XOJO needs to realize WHERE that money comes from… and your product should reflect the desires of your clients… not some need to mimic Apple, or because one of the XOJO engineers thinks it might be “cool”.
I’ve been a loyal XOJO client for 7 years so far… and while there is not a lot of competition (my opinion)… it would not be in the best interest for XOJO to get “cocky”… I’m sure I could name a few companies that took that attidute and are either gone, or mere shadows of their former selves…
Your opinion of how this should behave and mine (and that of others) differ.
Neither is more or less “right” or “wrong” - they just differ.
And since these are opinions - not hard cold facts like 2+2 = 4 - they can differ without being “wrong”
There is a feedback request to alter the behavior #30602
[quote=45426:@Norman Palardy]Wrong is when its not functioning as designed - it is acting per tab as designed
The intent was to mimic Safaris per tab back & forward
I find that completely unintuitive for an IDE … and I think most do too… In RS I used back a lot… Now I don’t at all.
I don’t always remember what I did in what tab… When I want to go back. I want to be able to do so without trying to remember which tab I was in last (That is part of the “getting lost” thing) then having to click on that tab and THEN click on the back button…
[quote=45430:@Karen Atkocius]I find that completely unintuitive for an IDE … and I think most do too… In RS I used back a lot… Now I don’t at all.
I don’t always remember what I did in what tab… When I want to go back. I want to be able to do so without trying to remember which tab I was in last (That is part of the “getting lost” thing) then having to click on that tab and THEN click on the back button…[/quote]
My thoughts exactly. I can’t even use the back button, which definitely slows down my work within Xojo. At least the option for it to work globally or per-tab should make most users happy.
The reason for why Xojo’s behavior is plain wrong is that the explanation that Norman and Paul keep giving us is on a bad association with Safari, and they do not even realize that, apparently:
Whereas Safari’s tabs of web pages are indeed independent of each other, those in Xojo projects are not. If we use an action that looks up a method, and if that moves us to a DIFFERENT tab, then there should be no doubt that a Back button brings us back to where we previously moved away from, EVEN IF it was from a different tab. Anything else is just ignoring the usual workflow a programmer goes thru. And the fact that I’m not the only one saying so here and Feedback should open Xojo people’s eyes instead of keeping them blindfolded by referring to a concepts that’s not applicable here.
Furthermore, even Xcode, which is a much better analogy to this issue than Safari is, this works better: Xcode doesn’t switch Tabs when looking up identifiers (with cmd-click), so Xcode can adhere to the concept of tab-specific history because there, it doesn’t cause the grief that Xojo is doing to us.
In short, Xojo is justifying a non-working concept with a rule that applies well to some other context.