News:IMPORTANT MESSAGE! This forum has now been replaced by a new forum at http://forum.eastgate.com and no further posting or member registration is allowed. The forum is still accessible via read-only access for reference purposes. If you wish to discuss content here, please use the new forum. N.B. - posting in the new forum requires a fresh registration in the new forum (sorry - member data can't be ported).

After once again diving into OmniFocus I'm reminded that its implementation of "Perspectives" is terrific. The way I use Tinderbox requires a lot of window management and oh how nice it would be to save a configuration of open windows, views, etc. as a named Perspective (or whatever it should be called.) Certainly not an easy problem to solve, but I would find it very useful.

You have to control three (maybe) things: cursor location, menu selection and window position.

The first two are most easily controlled with some kind of macro program such as Keyboard Maestro, but are also Applescriptable via Universal Access. If you really wanted to go this route, I could post some basic examples.

Charles, thanks for the tip but this wouldn't entirely solve my problem.

I work on a one huge file (see recent post on splitting files in TB, it is rather annoying because prototypes are not preserved when merging files). "Perspectives" or bookmarks (as it has been termed in earlier posts) to me would serve two purposes:

- quick access to specific containers which are not readily accessible (i.e. oftentimes several levels deep into a container/child tree structure)- memorising window attributes as per last usage, in particular position of window(s), open columns and checkboxes in outline windows, and scrolling position in map window.

This is how I concretely imagine it being implemented:a menu option in the Window Menu, e.g., in which you can take a snapshot of the current window arrangement, which Tinderbox could save as a <windows></windows> element in the tbx file. These snapshots would then be callable from the same Window Menu.

PS: And no, keeping all the relevant windows as minimized is not really a workable option! I use Tinderbox for so many purposes that the dock would become far too crowded.

- quick access to specific containers which are not readily accessible (i.e. oftentimes several levels deep into a container/child tree structure)- memorising window attributes as per last usage, in particular position of window(s), open columns and checkboxes in outline windows, and scrolling position in map window.

For objection number one, just make yourself a top-level entry in your outline called "Perspectives" and put aliases to the relevant items in there. In other words, make your menu a piece of your outline instead of hoping for a menu.

For objection number two, the ones you mention are A-scriptable, so I'm not sure they're objections. I posted a scrolling script a while back, but it's more than 25 posts in the past and I'm too lazy to search for it.

@Manuel - something possible to do today (v5.7.0) to rapidly access deeply nested containers is to place an alias at root level (or wherever you want access). Then select and use 'Show Original'. I'm not suggesting this is the feature discussed here - just a workaround.

Fair enough, thanks for the tips to you both.I might have a go at KBMaestro-scripting the restoring of specific columns in certain windows, since this had proved the most bothersome to redo manually each time

I would be a huge fan of some sort of "perspective" solution. For example, when making a presentation, I might want quickly jump to a particular map view. When preparing for the presentation, I might want to open an explorer window and hide everything else.