XYplorer Beta Club

Ok.. so I have a couple questions on using tabsets - must say they are a bit more confusing that I thought they would be as compared to DOpus and their Listsets.

So - what I'm trying to do is setup 2 panes with 8-10 tabs each that I would want to open certain times during the day. In Dopus, all I had to do was setup the tabs the way I wanted them once, save the listset, and then hit one button to get both panes to display the tabs. On exiting the program, the tabs would revert back to the default set. Very easy and nice.

So, I'm trying to do the same in XY.. so, I created the first 8 tabs in pane 1 (top) and use the Tabsets->SAVE As to name it (Topset). I then pull down the tabset button and see my tabset (along with a 1). If I click the tabset, it tells me to copy to a clone? Not what I want.. just want it to load the tabset. Anyway, I choose the 1, then choose TopSet and it loads. Ok.. that's cool

So, I do the same for Pane 2 and create Bottomset...

Now, I exit the program and come back and hit the tabset button and now see 3 options... 1, Topset and Topset/t... where did the t come from? It appears to get auto-created upon exit? I don't want that....

Just curious why this approach was implemented to save panes? DO's approach appears much easier - just define, save and switch to it whenever you want those tabs. Workspaces are saved - both panes at the same time. While XY's approach is more flexible - why differentiate the panes as tabsets instead of the workspace?

If I can get this working, I would then like to script a button to load both tabsets together with one cilck... seemed like this could be done with something similar to: tabset("open", "topset"); but when I try that in the scripter it says it cannot find the ini file (but I can see it). If I try it on the topset\t - it works just fine.

Thx for the help...

As a tabset newbie I ask myself the same questions, seems like there should be at the very least a way to:

a) Save/load dual-pane tabsets.
b) Toggle read-only property for individual tabsets.
c) View tabsets directly on the menu (perhaps as a sub-menu), or the top 'X' most used tabsets.

Edit:
d) Define a default tabset (i.e. 'load this tabset on launch').

pesto12601 wrote:Ok.. so I have a couple questions on using tabsets - must say they are a bit more confusing that I thought they would be as compared to DOpus and their Listsets.

Thanks for the comments. Tabsets is a relatively new feature and I'm sure it can be streamlined.

Reading your confusion about the "Clone" prompt I immediately got an idea that should reduce the confusion. In the next version in the button's dropdown the current tabset will be marked by a black dot (aka radio-checked). This will prevent you from clicking it (= loading it again).

Concerning the "Topset/t" that's totally mysterious. Can you reproduce it? How?

Why tabsets per pane: Well, this came naturally to me (I don't know DO other than by the name). And I still think it's okay to have them per pane. OTOH I also see the use of loading dual tabsets to both panes simultaneously. It might be added in future.

Don

Thx Don... I look forward to the future enhancements.

I will try to reproduce the /t stuff... I know everytime I define a new tabset and then exit the program, it seems to create a "t" subfolder with a pane.ini folder within... I also tested this on another user machine and he also had a "t" subfolder... both running the latest version.

I guess for me, I would like the software to allow you to:
a) define a tabset (tabs could be just for the single pane - not a big deal)
b) switch to that tabset all the time (even if you already have that tabset loaded - if you click it, it would just reload the same tabs again)
c) load both pane's tabsets at the same time (again, I'm sure this can be scripted but it would make a nice feature)

I think the idea of cloning is nice but should just be kept as a menu item - if I switch to a tabset already open, would it not be easier to just open those tabs? It would eliminate the need for the "Revert" setting... if I happen to add/remove or change a tab and then reload the tabset, those changes would just be binned. If I wanted them to be retained, I would just save the tabset (perhaps a dialog asking if they should be saved before reloading).

Anyway.. just my thoughts. I know you may not wish to replicate ideas from other software and you mention you haven't used DO to see how it works... but I'm sure others that have used it will confirm that it seems to work in much the same way as your tabset implementation but in a more user friendly and I guess I could say logical manner for me.

Hope others will chime in as well. Thx for your time!

I'd like to hear some reactions from tabset users (I myself happen to not really use the feature apart from when making screenshots where it is very useful).

.

grindax wrote:I use tabsets, and I'd prefer that a single tabset applied to both panes.

Not opposed to this being possible but I prefer the existing single-pane to tabset relationship.

I have one pane displaying the tabs I'm using almost constantly, so I find tabsets useful for switching contexts in the other pane.

I'm all for multi-pane tabsets but only so long as XY retains the single-pane tabset abilities.

pesto12601 wrote:I will try to reproduce the /t stuff... I know everytime I define a new tabset and then exit the program, it seems to create a "t" subfolder with a pane.ini folder within... I also tested this on another user machine and he also had a "t" subfolder... both running the latest version.

FYI, that /t subfolder holds the temporary state of the current tabset before it is explicitly saved. I currently don't see how it did end up in your tabsets listing. It should be totally invisible to the user/UI.

I'll try to post some screenshots next time I use it - it was listed in the tabset dropdown.

I wouldn't have a problem with the single pane tabsets if the following were implemented:
a) the ability to open 2 tabsets (1 per pane) with a single click
b) the ability for the tabsets to just open via the dropdown or menu (in other words, just open the tabs for that tabset even if that tabset is already open - no clone/copy option and do not prevent the tabs from opening because the tabset is already opened).

Thx again for the discussion on this... nice to know the developer is listening and willing to make changes!

Maybe create a kind of a "logical" tabset, just being a reference to 2 physical tabsets for the two panes?

pesto12601 wrote:Thx again for the discussion on this... nice to know the developer is listening and willing to make changes!

Hi and welcome to the XY forums from me also!
That's why we love this product and Don! He's unusual in his responsiveness to us users...and that's why you should buy XY now if you've not with the special deal going on now on BitsDeJour.
See http://www.xyplorer.com/xyfc/viewtopic.php?f=3&t=7750

PeterH wrote:Maybe create a kind of a "logical" tabset, just being a reference to 2 physical tabsets for the two panes?

Read that quickly and what it made me think of was Moses and the two tablets...but that was a different situation.

Note that the tabset() scripting command has a pane parameter. So it's easy to make "dual tabset" one-line scripts...

pesto12601 wrote: b) the ability for the tabsets to just open via the dropdown or menu (in other words, just open the tabs for that tabset even if that tabset is already open - no clone/copy option and do not prevent the tabs from opening because the tabset is already opened).

If selecting the tabset that's already loaded: Do others agree that a "Reset to Saved?" would be better than the current "Make a clone?" prompt? Or should simply happen nothing (status bar message: "tabset already loaded").

BTW, note that there is always CTRL+Click to force the clone prompt.

.

grindax wrote:Yes, I agree. Although I'd call it "Revert to Saved?", just like what already exists in the Tabsets menu.

Yes, I also think that "Revert to Saved?" would be the best choice. Additionally, I would find it nice to be able to optionally suppress that question and simply do the reverting to saved "without questions asked". (Using these things from scripts, I very rarely encounter this "cloning question", since I have a habit of "parking" a pane to a default tab, when I no more need a project I had opened in the pane. So, it is only when I am not actually aware any more that I have a certain project opened already, that I try to "reopen" it.)