Yes and No—not reliably, only sometimes. Why that is it the mystery at the heart of this thread.
Yes, the ancestor container of the lest used branch item is now selected. Is it visible? Not reliably. In this case I suspect the tab’s stored map scroll settings (if there are any) may take preference.
The ‘last used map area’ is harder for the user to keep track of an a nice thing for the app to remember for the user (where it can). By comparison, the user will instantly know if they’d rather see (now, in this map) the current selection. If we give the user a quick method to allow this (shortcut—I realise a lot are already mapped for other things) and a menu option for non-typists, I believe this removes most of the friction.
IME in maps, I’m generally wanting to see where I was (last scroll state). It normally working on other people’s maps where I find I’m trying to find things†. But as we all use parts of the app differently, a ‘YMMV’ proviso applies to assuming that is the most common experience.
Other factors at play here is that we have more tabs and bigger maps. I quite often note users employing a tab per view type (it’s allowed!) yet ‘lest visited’ is stored in a tab. IOW, sensible assumptions from older Tinderbox may not have aged in the way we want. No criticism implicit there as the future is hard to predict.
†. As, inconveniently, ‘blanfdbindnland blind typing’ isn’t as helpful as intended for the dyspraxic/dyslexic typist!
Relatedly, is it possible for a new map to arrange notes so that they are all visible on the screen?
Specifically, I enter a bunch of notes in the Outline, then switch to the Map view to move them around and think about them. But before I can even get started, I have to deal with a long row of notes that runs off the edge of the window.
Certainly Tinderbox shouldn’t change the user’s intent, but perhaps its own defaults could be more sensible?
Notes are now in a grid. If you only want to re-order the last added ‘row’ of item, select only those and use clean-up.
When you add a note in Map view and then press Return a new note is added to the right of the current note. It has to go somewhere. If the current note has a note to its right, the app scrolls further right until there is space and adds the new note. It can’t guess what we as the user thinks is a nice layout. The app finds an open spot and add the note. It is then our job to move it where (only we know) it should go.
Adding notes, or moving a selection of notes, into a container in Outline view (or Chart, etc.) simply replicates the process above when adding the notes directly in the map.
The Cleanup is designed to help re-arrange notes into simple patterns to help with starting the real (human) task of moving notes where they need to go.
Automatic sounds neat but then you end up fighting against it to impose your own order.
Sorry, for the long answer but this old chestnut hasn’t changed over the decades though this is the first time in ages it has been raised so it is perhaps helpful to have some background context.
A tangential factor is that notes have got bigger (at default size) but laptop screens have not, so the point at which the human needs to get involved in map placement crops up earlier. If you drop 20 notes in a container and look at the map, even in a tight grid they likely won’t all fit in a standard size view pane. IOW, it’s not the app being mean or lazy.
I hope that clarifies some of the unseen background issues.