Some versions back, we developed back and forward navigation by using hidden windows. We made it so any time you navigated or changed your found set, we "cached" the current window as a hidden window, numbered it, and stored the name in a global so we could get back (or forward) to it. Since we never really left the window, the found set, sort order, fronted objects and so forth are all still there when you restore the window. It works well still, but there are a lot of details, like identifying all the actions that should cause a caching, setting limits, and also tracking back and forward in multiple window issues. We have it working reliably and reusably in our solutions, but I don't think I'd wish the effort (at least unassisted) on anyone.
I've since been experimenting with the snapshot links. Caching an fmpsl in the temp folder is a bit easier. The drawback is that fmpsl files open after any running scripts are finished, so you need to take that into account. This is still a work in progress for me, although I have worked out proof of concept.
Thank you Mike, these navigation buttons are working well for me - appreciate it!
Thank you Extensitech, I am very curious to hear how your work in progress turns out! Sounds a bit over my head, but all the better thanks for your help!
This one is free, supports multiple windows, and is "modular", making integration easier.
That is super clever imo. One script, one object, one (optional) custom function. Multi-window history. No triggers. Only layouts with the object ( a button bar) affect the history.
That's basically gonna be in every solution I ever make.