Tabsets - Small Bugs & Wishes Thread

[Borut]

2. The main menu's Tabset commands all apply only to the active pane. Only using scripting (SC tabset(...)) you can operate on the tabset of the inactive pane. Did you make an different experience? That would be a bug...

Can not tell at the moment. Maybe the problem is that I am constantly not counting on automatic save of the current tabset. It would be (at least for me) much easier to proceed with a version which would:

- Implement TheQuerty's idea: "it's disorienting and confusing that those already in use are not displayed";
- Have (for now at least) the same popup menu on the tabset icon for both left and right click (currently makes me nuts).
- This is maybe too much to ask: An option for a mode: No implicit tabset save of any kind under a user defined name. I would be happy if just explicit tabset saving (under a user defined name) would be available, so that potential messing after the save can not get saved in any implicit way.

[Marco]

- This is maybe too much to ask: An option for a mode: No implicit tabset save of any kind under a user defined name. I would be happy if just explicit tabset saving (under a user defined name) would be available, so that potential messing after the save can not get saved in any implicit way.

As Don told me, this is impossible since tabsets are constantly saved to their ini files.

[Borut]

- This is maybe too much to ask: An option for a mode: No implicit tabset save of any kind under a user defined name. I would be happy if just explicit tabset saving (under a user defined name) would be available, so that potential messing after the save can not get saved in any implicit way.

As Don told me, this is impossible since tabsets are constantly saved to their ini files.

Yes. As far as I understand, it was already so: under <xydata>/Panes, "1" and "2" have been saved in that way behind the scenes. So my (maybe naive) idea of the last minute feasible solution/option: This remains unchanged, so that "1" and "2" would be a kind of default up to date images of the current panes' 1 and 2 tabsets. However, additionally, user (and only user) would have the possibility to "freeze" one of these tabsets at a certain moment under a user defined name.

Isn't this the paradigm other programs (editors, word processors,...) are using: Autosave every few minutes behind the scenes under internal name and explicit save by the user under a user given name?

[admin]

- This is maybe too much to ask: An option for a mode: No implicit tabset save of any kind under a user defined name. I would be happy if just explicit tabset saving (under a user defined name) would be available, so that potential messing after the save can not get saved in any implicit way.

As Don told me, this is impossible since tabsets are constantly saved to their ini files.

Yes. As far as I understand, it was already so: under <xydata>/Panes, "1" and "2" have been saved in that way behind the scenes. So my (maybe naive) idea of the last minute feasible solution/option: This remains unchanged, so that "1" and "2" would be a kind of default up to date images of the current panes' 1 and 2 tabsets. However, additionally, user (and only user) would have the possibility to "freeze" one of these tabsets at a certain moment under a user defined name.

Isn't this the paradigm other programs (editors, word processors,...) are using: Autosave every few minutes behind the scenes under internal name and explicit save by the user under a user given name?

Either this "freeze" is nothing but "Save Copy As", or I have not understood it (and it's proably a bit too special a wish).

[eil]

Hmm, any better idea anybody?

how about a adding to Templates > Title bar <tabset_name> ?

Code: Select all

 Syntax: tabset([operation=open], [name], [pane=a])
"a" = active pane, "i" = inactive pane

after reading this i thought it would be great if it appeared some king of /a, /i parameters, so user could define while saving if he wants to save this tabset for active(current) panel or second one(inactive). if no parameter specified, currently active is used.

[admin]

Hmm, any better idea anybody?

how about a adding to Templates > Title bar <tabset_name> ?

Code: Select all

 Syntax: tabset([operation=open], [name], [pane=a])
"a" = active pane, "i" = inactive pane

after reading this i thought it would be great if it appeared some king of /a, /i parameters, so user could define while saving if he wants to save this tabset for active(current) panel or second one(inactive). if no parameter specified, currently active is used.

1. the titlebar might be to small if long paths are involved

2. Hä? You probably misread the syntax definition: [pane=a] means there is a pane parameter that defaults to "a" if it is missing.

Code: Select all

tabset("New", "Sue"); // active pane
tabset("New", "Sue", "a"); // active pane
tabset("New", "Sue", "i"); // inactive pane

[eil]

1. the titlebar might be to small if long paths are involved
2. Hä? You probably misread the syntax definition: [pane=a] means there is a pane parameter that defaults to "a" if it is missing.

Code: Select all

tabset("New", "Sue"); // active pane
tabset("New", "Sue", "a"); // active pane
tabset("New", "Sue", "i"); // inactive pane

1. agreed, that may be so, but still it would be great to have it there.
2. maybe i really misread something, but it seemed to me it refers to scripting, and i'm talking about UI =so when i use Tabsets Menu > Save As and window opens to specify name, i could type "Name /i" and it will be saved to list of other/inactive panel(no matter if it's pane1 or pane2 active now)= is it possible?

[nony]

Nice..Good to see it's finally implemented. Waiting for tabset mru

[Marco]

Will be possible to delete a tabset via scripting?

[admin]

Will be possible to delete a tabset via scripting?

Not planned. But maybe later...

[TheQwerty]

Given the above it would then be useful to be able to clone a tabset that is already in use

doesn't Save As or Save Copy As do that?..

Indeed! My point was to make it possible to do that from the open dialog.

As I said, I'd like to see Open show the used tabsets and if I select one offer to save copy as (in this usage "cloning" sounds better to me); Instead of forcing me to close the dialog, save copy as, and then return to the open dialog.

It's all about improving the workflow so that a user that forgets to "save copy as" before getting to the open dialog has a way to proceed forward that doesn't require going backwards.


EDIT:

Will be possible to delete a tabset via scripting?

Not planned. But maybe later...

Considering they're just files and folders, it's already possible.

[admin]

Given the above it would then be useful to be able to clone a tabset that is already in use

doesn't Save As or Save Copy As do that?..

Indeed! My point was to make it possible to do that from the open dialog.

As I said, I'd like to see Open show the used tabsets and if I select one offer to save copy as (in this usage "cloning" sounds better to me); Instead of forcing me to close the dialog, save copy as, and then return to the open dialog.

It's all about improving the workflow so that a user that forgets to "save copy as" before getting to the open dialog has a way to proceed forward that doesn't require going backwards.

The recent beta 0113 does offer cloning when you load a tabset that's in use. Looks like I forgot to menion it in the change log!

[Marco]

Considering they're just files and folders, it's already possible.

Yeah, you're right!

[admin]

Nice..Good to see it's finally implemented. Waiting for tabset mru

Conc. MRU I wonder whether to make a global MRU or one for each pane. Opinions?

[eil]

Conc. MRU I wonder whether to make a global MRU or one for each pane. Opinions?

with the current behaviour that all tabsets are seen in Open dialog, and only 2 defined to each of panels, how can this MRU be not global?. all undefined/unused tabsets are free to be opened in any of panels, so they are already global(as i see them)

by the way, as Open dialog is resizeable, shouldn't it remember size user set?