Re: Remember tree settings for each tab, and other search wi
Posted: 24 Jul 2011 14:32
Thanksadmin wrote:Simply put your whole app data folder to the secure location. You can use startup.ini for that (see Help).
Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Thanksadmin wrote:Simply put your whole app data folder to the secure location. You can use startup.ini for that (see Help).
I have a different point of view of this. I'd like to have such a feature but focused on the tabs-tree (no "mini-trees" here) relation as I think the tree should be strictly attached to what each tab does, did and keeps in tab history. Each tab sharing the same tree means several folders with tens or hundreds of subfolders being opened at the same time and when I have to scroll up or down after a folder to drag content into, I have to scroll through all of those folders who do not belong to that task in any way.(...)
Please, can these be fixed or config options created to allow these behaviors? What I'd like in summary:
Config option to keep tree state "per tab"
I can certainly see from the above that having the whole tree would be useful for this usage case. At the same time, I think the mini-tree version would be most useful for me (and for some others based on their comments).tiago wrote:I have a different point of view of this. I'd like to have such a feature but focused on the tabs-tree (no "mini-trees" here) relation as I think the tree should be strictly attached to what each tab does, did and keeps in tab history. Each tab sharing the same tree means several folders with tens or hundreds of subfolders being opened at the same time and when I have to scroll up or down after a folder to drag content into, I have to scroll through all of those folders who do not belong to that task in any way.(...)
Please, can these be fixed or config options created to allow these behaviors? What I'd like in summary:
Config option to keep tree state "per tab"
If the tree could just display the state and history of opened folders for each opened tab instead of global then I could have very smaller trees to deal with thus making my management easier.
Global tree as it is is the main reason why I keep apart from Catalog as I have to save space due to current behavior of the tree-tabs relation. Widescreen just made this worse.
When (hopefully) you will think about it, some day, might that be the time when you also think again about Dual Tree / Tree Per Pane or however it could be named?admin wrote:It's not that easy to do. Other things will have to happen before I even have time to think about it.
That's another story, much bigger and uglier...PeterH wrote:When (hopefully) you will think about it, some day, might that be the time when you also think again about Dual Tree / Tree Per Pane or however it could be named?admin wrote:It's not that easy to do. Other things will have to happen before I even have time to think about it.
As: when having tree settings per tab, and one active tab per pane, you have the data for trees of both panes. Then you had "only" to enable the display of a second tree - and many people would be happy
Remember how much time it took to add dual pane?PeterH wrote:Sorry: I wonder why? As the info you need for the 2nd tree seems to be there, then?
Any chance of this as an early present for 2012?Stilez wrote:Coding takes time...... Hopefully the above thread means this is something we can look forward to, even if not "tomorrow" - I am sure when it's done it'll look good!
Naah, not really.Stilez wrote:Any chance of this as an early present for 2012?Stilez wrote:Coding takes time...... Hopefully the above thread means this is something we can look forward to, even if not "tomorrow" - I am sure when it's done it'll look good!