History for every tab

[Muroph]

I don't have the time to really play around with this, but I dislike the wrap around.

I very much prefer the setup used in most browsers, where Forward is only ever enabled if you have navigated Back in the history, and is disabled again if you rewrite history (by using Back and then going to a different folder than you would using Forward).

i second that.

[Trinsec]

I don't have the time to really play around with this, but I dislike the wrap around.

I very much prefer the setup used in most browsers, where Forward is only ever enabled if you have navigated Back in the history, and is disabled again if you rewrite history (by using Back and then going to a different folder than you would using Forward).

I haven't tried it yet, but from what I've read it sounds like I'd find it annoying as well. I do expect the same behaviour as in browsers, it's only sensible.

[jacky]

Well, I don't have time to try it now, but a couple of remarks anyways :

- the looping thing I very much dislike as well, I want the per-tab history to behave like the global one, when I can't go back/forward, than I can't.

- menu Go|History doesn't show bold when used from there (as opposed to popped up using KS)

- I'd like a way (e.g. CKS|Misc) to assign a KS to a History popup menu for the current tab only (as when using the little arrow on the button on TB)

- I'm also thinking I'd like the same for Hotlist - a way to get an Hotlist based on the current Tab history only. And again, I'll be fine with CKS|Misc, which allows one to have it both ways. Of course, just like for Back/forward buttons which should have their dupes for the current tab only, another TB button for Hotlist based on current tab history would be nice.

I think it's been mentioned before, like how the Back/Forward/Hotlist buttons could have exists in both flavors : green as today for global, and blue versions for local (current tab) only.
Found it:

And the buttons ctx menu? And the hotlist? All tabwise? Where can I see and use my global history then?

Well, as I said you could hold Ctrl to get them to work globaly instead. (Not to mention you could add items on the ctxt menu, such as "Global History..." and "Global Hotlist...")

What you could also do, and I believe I've also seen on other app, is to duplicate those buttons : the standard (tabwise) ones, and their global duplicates. For example, the same buttons would be available, but say in blue instead of green, to indicate that they are working on global history, not tabwise. (And for them, holding Ctrl would mean working tabwise.)
So every user can choose how its buttons work, and simply by holding one key has access to the other way.

[PeterH]

Basically History Per Tab is very fine, much better than before!
For me the wraparound looks a bit strange, too.
And: I'd prefer Lists per tab over one list for all tabs. While it can be fine to have the summary-list, too. Especially to refer to entries of a just closed tab, that would vanish otherwise, I think.

[j_c_hallgren]

Could there be a way in List Management to have the tab nbr that item is tied to shown? That might help to at least locate the desired entries, and when sorted, it would sort on that as major field....just an idea?

[serendipity]

I don't have the time to really play around with this, but I dislike the wrap around.

I very much prefer the setup used in most browsers, where Forward is only ever enabled if you have navigated Back in the history, and is disabled again if you rewrite history (by using Back and then going to a different folder than you would using Forward).

I haven't tried it yet, but from what I've read it sounds like I'd find it annoying as well. I do expect the same behaviour as in browsers, it's only sensible.

I dont agree completely because this has some advantages. Thinking about it, browser history have a major flaw. Once you navigate to another location your old tab history is lost. Let me give you an example:
In any browser: go to google and type XYplorer. Click the first entry and navigate a bit and go back to google results. Click second entry and navigate there and you see that your first navigation is lost.
And in XY, lets say we have on one tab 4 folders A,B,C and D and each have subfolders 1-4 respectively. When you start navigating to A\1, A\2 etc and then navigate to B\1 and B\2 then your history of A folder is not lost. So XY no matter where you navigate all those items are preserved in history as long as you dont hit the 64 items limit.
While I dont completely agree that this wrap-around is bad, there can be some improvement in how it is presented. My first thought is if it can be organized by levels. Like all navigated folders in first column, subfolders on second column, sub-sub folders third column and so forth. Just my first thoughts here.
Update: OK seems like I was addressing a different issue . But surely if one uses browser strategy like one suggested by others then you lose tab history for other entries. And, "wrap-around", is confusing. The forward arrow is still active when there is nothing beyond it. So i agree on that part, but dont agree on the browser style of history. All items of a tab are necessary.

[admin]

Okay, thanks for the comments! You see: Things become interesting once you really start to do them.

Some of the glitches mentioned are one time transition effects that will auto-vanish soon. I might write some code to keep it civilized...

Size is obviously a challenge. I will try to make the store much bigger (we'll see how that affects startup time...) so that many tabs can have there own history. At the same time I will reduce the height of the menus, i.e. the number of items shown at any one time. There are some factors here like screen height, font size... but I think I'll just go back to the old limit of 32 items max, because it seems to have worked for everybody for years now.

Cycling: Okay, looks like a universal thumbs down. Got it.

Pop up tab-wise history via CKS/Misc. Yep, I expected that one.

Different locations within one locked tab? Nope, sounds like a klingon approach to file management... (wanna say: too exotic).

Make them bold even if TPH is off? No, will frighten newbies.

Menu go / history: not bolded: Is not possible technically here.

[j_c_hallgren]

Make them bold even if TPH is off? No, will frighten newbies.

One word answer: Documentation! Compared to other parts of normal XY, I really doubt that would frighten newbies.

[jacky]

And what about the Hotlist based on current tab history only ?? I would like that one, too.

[admin]

And what about the Hotlist based on current tab history only ?? I would like that one, too.

Maybe later. Basics first.

[admin]

PS: Concerning LM: The numbers you see in front of every history menu item match the ones in LM/history. So there's some orientation built in... BTW, No. 1 is the oldest item.

[serendipity]

I just started to extensively use this feature and i should say its awesome. Thanks for implementing this Don. .
Some thoughts though:
1) Yep, LM would be nice. How about a button in LM|history called sort tab-wise? Or simply a right-click on the existing sort button? Thinking loud.
2) Based on what you said here, how about "close-tab-go-to-previously-used-tab" and ctrl+tab cycles to previously used tab rather than going right.

[admin]

I just started to extensively use this feature and i should say its awesome. Thanks for implementing this Don. .
Some thoughts though:
1) Yep, LM would be nice. How about a button in LM|history called sort tab-wise? Or simply a right-click on the existing sort button? Thinking loud.
2) Based on what you said here, how about "close-tab-go-to-previously-used-tab" and ctrl+tab cycles to previously used tab rather than going right.

1) Not easily possible. And I'm not sure what should be achieved by this. For me the history is a trace of action, so manipulating it defeats its very nature in a way. For hand-chosen permanent pointers to locations we have favorites of all sorts...

2) Somehow my workstyle is different (I was always happy with a global history), so you need to explain the use and context of this thing, and how it should be implemented (are you thinking of a new config option, or of an additional command?).

I have a somehow related question: When tab is closed, should "its history" be deleted?

[Trinsec]

I just started to extensively use this feature and i should say its awesome. Thanks for implementing this Don. .
Some thoughts though:
1) Yep, LM would be nice. How about a button in LM|history called sort tab-wise? Or simply a right-click on the existing sort button? Thinking loud.
2) Based on what you said here, how about "close-tab-go-to-previously-used-tab" and ctrl+tab cycles to previously used tab rather than going right.

1) Not easily possible. And I'm not sure what should be achieved by this. For me the history is a trace of action, so manipulating it defeats its very nature in a way. For hand-chosen permanent pointers to locations we have favorites of all sorts...

2) Somehow my workstyle is different (I was always happy with a global history), so you need to explain the use and context of this thing, and how it should be implemented (are you thinking of a new config option, or of an additional command?).

I have a somehow related question: When tab is closed, should "its history" be deleted?

Depends. I haven't used it yet (NO time! Can read stuff though!). I don't know if there is 'undo close last tab' option, in case you accidentally closed a tab. If there is, then history shouldn't be deleted, yet.

[j_c_hallgren]

I have a somehow related question: When tab is closed, should "its history" be deleted?

I would definitely prefer for it to remain intact, as I tend to have two tabs open most all the time, and open up temp "working" tabs as needed, so having that history avail when I reopen that/those tab makes using it easier.