Scripting: History for tabs?

Hi guys. I'm sure you have a bunch of other pressing to-do's still.

Hoping you'll consider exposing the back and forward history of tabs as a property of the Tab object someday... perhaps something like:

Property Name: backlist
Return Type: collection:Path
Description: Returns a collection of Path objects from the tab's folder history. This is the same list you would see using the 'Go BACKLIST' command.

Property Name: forwardlist
Return Type: collection:Path
Description: Returns a collection of Path objects from the tab's folder history. This is the same list you would see using the 'Go FORWARDLIST' command.

Seems like a reasonable idea.

What sort of thing would you use it for? (Might boost it from "sure why not" to "let's do it sooner".)

Ah, well not sure I'll gain much love fessing up to what I want it for right now :slight_smile:...

Both NavLock and my NavSync script suffer from some strange behavior when sync has been lost and then a user does different combinations of 'Back' operations in the source vs dest linked tabs. I've got a few test cases I'm going to send you guys videos of along with some scripted repro scenarios that show the strangeness.

In the meantime, I'm still looking to maintain and enhance my NavSync script, because I make heavy use of dual monitors for awhile now and really enjoy having NavLock like functionality between different listers. I can fix some of what I know is wrong in NavSync by having access to the history so I know when it's ok to use Back/Forward/Up commands on the linked tab in order to PRESERVE the histories of each tab as much as possible, but to AVOID using it blindly once I'm in an out-of-sync condition where it will cause further strange loss of sync.

As an aside, thanks for adding the format object to the Tab properties... that's helped me to add some features to return the tab to it's previous format after I've changed it in my script in order to achieve a more subtle sync-loss notification (background color of linked tabs file display).

We'd rather improve any cases where NavLock still goes wrong, if it's just for that. :slight_smile:

Oh no!

So instead of going from "sure why not" to "let's do it sooner", I went to "nah, we'd rather work on other stuff".

LOL!

I'll start a new thread for some of the navigation weirdness video...

Better to fix the underlying problem (whatever it is!) for everyone than to add ways for you to fix it via workarounds. :slight_smile:

Any time you're ready... :wink: