Automatic toolbars have been driving me nuts. Sometimes they work great, sometimes they do not.
I have a number of tab groups and when I look at the source for the folder format it quite rightly says it comes from the particular tab, and the toolbars work fine.
However when I look at the source for the first set of tabs in the list in my Preferences, it says that the format comes from the default folder and the toolbar performance is very erratic.
When I add a new tab list and call it A, to make sure it comes to the top of the list, I suddenly find that the folder format in the tabset that was previously top of the list comes from the tab, and the toolbars work as advertised.
Even if I hide A the situation remains the same.
I am happy because everything is working fine now, but it does seem a little odd.
When I look at any of the tab groups apart from the first - Downloads - by hovering and right clicking over the lock, I am told correctly, that the format comes from the tab
However if I look in the same way at the Downloads tabs this is what I see:
[quote="auden"]When I look at any of the tab groups apart from the first - Downloads - by hovering and right clicking over the lock, I am told correctly, that the format comes from the tab
However if I look in the same way at the Downloads tabs this is what I see:[/quote]
When I select an item from the drop down list on my toolbar that I mention in an earlier post the tabs appear at the bottom of the lister and I can use them. I thought this was how you loaded tabs into a lister. It has worked for years for me.
The real problem is when I close Dopus down and reopen it. The automatic toolbar function does not work. The toolbar stubbornly remains on the last tab that i had opened in the previous session. I need to re-open the appropriate tab from the list in the tabbar to get the feature to work.
You should get the same results from both menus, unless your custom menu is doing something unusual. (What command(s) does it run?)
When closing and reopening Opus, you're no longer loading the tab group (unless you then explicitly load it); instead you are loading a temporary layout saved from the last open lister(s). While those listers may have origtnally been the result of loading a tab group, they aren't the same thing when you save and reload them as a layout.
You are right. Both buttons operate identically. The confusion was caused by my not appreciating the tab groups did not automatically come back when you re-start Dopus.
Is there any method of achieving this. I have tried saving a lister layout with the appropriate tab set in it and loading that at start-up, but that does not seem to work.
I think any differences in behavior you're seeing is based on what you have set in the rest of those Launching Opus pages... and what happens and doesn't happen in listers depending on how you're loading them. Since you provided two of the prefs pages already, it might make sense to show the rest.
That said, from some quick tests here - something does seem like it might be wrong. I'll explain more later, but in a quick test... loading the tab group from a user command like you're doing still shows the folder format as coming from 'Default Format' (hovering over the format lock icon in statusbar). As opposed to loading that same tab group in a lister that is already opened using the same sort of command (Go TABGROUPLOAD=aTest)... where it then correctly describes the format as coming from Tab# 4 in Tab Group "aTest".
So my determination is that loading a lister via the 'Go TABGROUPLOAD' command in a user command is not behaving the same re: folder format derivation as the same command in an open lister.
Also, why it's probably important for you to take us through a scenario from start to finish... particularly since you mentioned having tried "saving a lister layout"? Well, I'm also seeing that if I have a layout that I've saved directly after loading the tab group in an open lister (with the toolbar that the tab in the tab group is set to load), load that layout (with the toolbar open) and then come and manually run the tabgroupload command, the toolbar actually shuts OFF. Actually same thing if I run the command as a user command as a startup or desktop-dbl-click setting.
Last note: your last screenshot shows you've got the default lister set to ignore it's folder format... so if NOTHING else I found in my tests above matter, loading that default lister layout will just inherit its format from your default settings - in addition to what Leo described about layouts not preserving the 'tab group' context - and just saving whatever format the tab group loaded into place as the format of the layout you're saving.
@Leo, there does seem to be an issue(s) here though - though I can't tell if it's related to the OP's problem since I have no idea how he's arriving at his results.
If you load a Folder Tab Group that has some specific formatting assigned to one of the tabs - using a command like 'Go TABGROUPLOAD=grpname' - the format lock shows the format as coming from the Tab Group as expected. THOUGH, I'm seeing the toolbar that I've added to one tab in the folder format flicker on then off again immediately.
Further, obviously - after loading the tab group as a layout (whether default or something else) won't retain any record of the format having been derived from the tab group, and it just becomes a format defined in the layout when you saved it, and again the format info from the format lock shows the expected derivation info.
But if you load the folder tab group as part of a user command set to run on one of the Launching Opus pages (say desktop dbl click), the format derivation info seems wrong sometimes. I saved the lister after loading the tab group using the raw command as the Default Lister. I then modified the Desktop dbl-click to run a user command that runs 'Go TABGROUPLOAD=aTest'. In the lister that opened on Desktop dbl-click - the format lock said the format was coming from the 'Default Lister'. I'd have thought since the lister that loaded was a result of the UserCommand to load the tab group, that it would have referenced the tab group in this case... but maybe launching a lister with a Go TABGROUPLOAD command is ambiguous and it is in fact loading the default lister?
Anyway, some confusing results depending how you mix things up... particularly the toolbar flicker on/off results mentioned just above...
