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).

I'm used to working with multiple windows spread across multiple desktops and my project files are set up to facilitate that. I think I will learn to like tabs, but for now, there are lots of occasions where I will be using multiple windows. So I have some questions about how TBX6 handles them.

1) In TBX5 when I reopened a project, all my windows and their positions were restored to their previous states, but in TBX6 only the window that was active on close reappears. Is there a way to have all my windows that were open at close reopen?

2) Is there an option or a modifier-key-combo that makes in-text links open into a note text window rather than switching the focus of the text viewer? The default behaviour takes me away from the note I'm working on. I then open the linked note in a text window and return to my previous note. Just wondering if there's a way to eliminate the follow-link/open note window/back-to-work loop.

3) In case there isn't a way to open links directly in text windows, is there an easy way (hotkey or menu option) to make the previous note active or to see back links (so I can click the one I need)? I haven't manually created in-text links "back" in most of my notes so returning to and selecting a previous note can involve an elaborate trip through multiple layers of my hierarchy in map view. (It's less difficult in outline view, but if there is a way to maximize my laziness with a hotkey, I'd prefer that.)

4) Working with TBX6, I've noticed that most the time the text viewers in all tabs and windows all show the same active note's text. But when using multiple windows, the viewers sometimes show the note text for the note that was last selected in its neighbouring tab/window regardless of which note is currently active in other windows. Which is the standard behaviour? (I prefer the second but it doesn't "stick" so I suspect it's not what's supposed to happen.)

>>1) In TBX5 when I reopened a project, all my windows and their positions were restored to their previous states, but in TBX6 only the window that was active on close reappears. Is there a way to have all my windows that were open at close reopen?<<

This is an issue that came up during the beta process. Like you, I've often used multiple open windows in TB5.

As a design-clarification point for MB: When you close a multi-window session with TB6, is it the window that was last active that reopens? Or the window that you first opened in the previous session? Thanks.

>>1) In TBX5 when I reopened a project, all my windows and their positions were restored to their previous states, but in TBX6 only the window that was active on close reappears. Is there a way to have all my windows that were open at close reopen?<<

Is there a way? One of the strengths of Tinderbox for me was (is?) the ability to work with different views of the data open at the same time: for example, work on an outline while at the same time having a map or timeline view open.

I finally figured out (not intuitive for me) that it is possible to accomplish that by going through a sequence of steps: add a tab, change its view, then right-click it to move it (actually it appears to "copy" it, leaving the original tab) to a separate window. So, with extra work, I've managed to get what I had before.

But then, when I go to File > Close to close the file, only that window closes (not what one would normally expect from that menu pick). And if I leave both windows open and quit Tinderbox and reopen the file, alas, only one window opens, so I have to go the sequence again.

From using it through betas over the months, I think TB6 is overall a huge step forward in functionality and elegance.

I think you've identified one of the few areas where, at the moment, it's not as convenient as the predecessor. In general, I've adjusted to the single-window/multi-tab approach of TB6 and see its convenience. But some times I do want to see several different windows at once. You can set this up, but as you point out it doesn't survive from one session to the next. I don't know whether that is adjustable-- if so, I hope it will be adjusted.

Again, in perspective this is one step back with scores of steps forward, but it's a little feature I miss.

As I've begun to adjust to the change (and said goodbye to my floating windows), I think I like the tabs! But they do change how I think about how I group my projects.

My work breaks down into three large "fields" that are distinct yet can frequently overlap or interact. In TBX5, I used one project file that was organized with three top level containers that corresponded to the three fields. In daily use, I treated each of these top-level containers as a mini-project file and opened each one up in a different desktop. The possibility of interaction between fields was there, but when I moved a window from one desktop to another, I didn't have to worrying about which project a particular window belonged to: there was only one project.

Now with TBX6's tabs and split view, there seems to be no possibility of confusion and I'm thinking of breaking my top level containers off into their own projects. My daily use would then involve opening the three projects (each with its own set of tabs) in three different desktops. I'd have the same level of access and complexity but in what seems to be a simpler interface that will work well on my MacBook Air.

Now with TBX6's tabs and split view, there seems to be no possibility of confusion and I'm thinking of breaking my top level containers off into their own projects. My daily use would then involve opening the three projects (each with its own set of tabs) in three different desktops. I'd have the same level of access and complexity but in what seems to be a simpler interface that will work well on my MacBook Air.

I have evolved toward something like this, too, and agree that it's very powerful.

There are still some cases when I would like to have different windows open on the same project or file, but most of the time the approach you describe does the job.

Thanks for explanations. Not being able to (easily) have different views open and visible at the same time (for me) takes much of the Tinderbox out of Tinderbox. I had thought for a moment that by dragging the divider to the middle I'd be able to have two major views side-by-side (à la Scrivener). But that right pane seems reserved.

If you want more 'major' views on display open a new window for each. You can move the splitter pane to give more room - N.B. the Window menu items that let you toggle (shortcuts too) all left pane, spit or all right pane. I do realise there's a slight issue about TB remembering which windows were open in the last session but I'm sure this will be resolved.

Six seems to be missing hoist: whether directly in Outline view or by opening a map from deep in the structure of an outline. I especially appreciated this ability to "narrow" the map view down to just a selected section. It would be a feature to restore in a future version.

In Outline, right-clicking the note icon reveals the list of prototypes (as in v5). To 'hoist' a container in Outline either double-click the note's icon or use Focus View in the Note menu.

The hoist/focus view operation only applies to containers:

So W,X and Y can be hoisted but not Z as it's not a container. Here Y is hoisted:

New to v6 is the 'cookie crumb' at the top of hoisted outline views (see above). Note that root elements can only be hoisted is there is more than one note/container at root level. So, clicking on W will shift view root focus to W - see how the cookie crumb indicators are updated too:

This hoist process also applies to chart view. Here the chart is hoisted to focus on X (note the cookie crumb indicator as view top):

The v6 map view also has a cookie crumb indicator:

In map view, as in v5, there are keyboard shortcuts to hoist (drill down) or un-hoist. Either the Up-arrow or Cmd+Up-arriw will un-hoist the current map, moving focus up one level of outline. To drill down (hoist), first select a container on the map and use the Down-arrow or Cmd+Down-arrow.