Twoje komentarze
There is something like Tabs Outliner v2 in development now.
I hope it will be published during this year.
And it's have this ability already.
This will actually be possible in next major version. It's not released meantime. And will be released as separate project with a notice in the original Tabs Outliner. In a month i hope.
I myself do not use auto scroll, so maybe this option is already somewhat buggy. Need retest. As every Chrome update brake something, sometimes a lot of something.... So it might be broken. But actually the idea is that it's auto-scroll on every Chrome window switch. And only if the other Chrome window is selected (not the same that was active last time). And only if it is switched by user outside of the TO (so switches using the TO does not counted). And selecting the TO itself must not be treated as switch to a new Chrome window.
If this is not work this way - then need to fix it...
There is an undo scroll button in the main toolbar.
But I think the best option for you would be just disabling the auto-scroll altogether (see the options).
TO will continue to perform the scroll to active window if you will press its action button in a Chrome window - so, just not call it that way, just do not close it, and activate from the OS toolbar (the place where is the all open applications listed - it has the own separate button on it when opened) or just by directly clicking its window if it is not covered.
Dont wont to mark this as rejected. Will see if this will catch some votes.
But It will be complex to implement unfortunately.
As in this case the Tree Style Tabs feature will stop works, or i will need to implement it in a form of some reverse tree - too much work for such a rare use case. And this will touch also a lot of other aspects.
Why not open new urls in just a new window? (Ok, i understand that habit is a sufficient reason, but just as a hint... ; )
BTW - maybe send a screenshot of your tree (can be blurred if your afraid of exposing the private titles of tabs), seems you have some very uncommon pattern of use for this thing. It will be helpful to see how people utilize this thing. Just to better visualize this case in mind.
I plan soon release new major version (as new extension), so maybe i will
take into consideration this scenario if something easy can be done to this problem. (most of the users hate when order of tabs is different in TO and in Chrome, it was actually a lot of efforts to make them always synchronized and straight)
Thanks for information.
Looks like this is really depends on available ram.
Anyway, in a day or 2 i will release a version which will automatically reload self after any TO view close, and on every hour. It is also will have some other performance improvements.
Hope this solve issue for some time. Also I really plan to do something about this memory usage - i am mostly have the TO View always visible. So reload is not a ideal solution. Have some ideas what can be done. But this will require more time.
Some other extensions that i use seems also start behave in this way. Looks like we have some serious changes inside Chrome regarding how JS memory is released.
Can i ask how much physical RAM do you have?
Looks like this "semi-stably" bound is depend on this.
This is really a serious issue, it's appears after one of the recent Chrome releases. Some memory leaks was present before, but after the latest Chrome updates they go completely out of control. Same problem for me. Working now on this.
Meantime the only advice - from time to time to go in chrome://extensions/ and disable and then again enable the TO - this will release all the memory leaks.
Maybe i will add automatic auto-reset. Which will do the same if all TO windows is closed - as quick solution
> This is more efficient than trying to remember the title of every window.
Actually if for this need to hover every single window to popup its thumbnail - it's not.
I am actually never feels that i need this feature. Not sure i want to bloat a simple program by such things. There is a lot of tabs manager with this features and they never satisfy me. The idea looks cool but only when you have 2-3 screens of such thumbnails, or 5-7 windows to hover.
To compare - my current tree meantime have ~20 000 saved tabs...
Customer support service by UserEcho
Please vote on this idea if it is really needed by many -- it will be implemented.
Yet before voting first consider that there is note functionality to add small, one line, comments to tab. And they have much better visibility than inline labels or custom titles.
Also this will make pencil icon (in hovering menu) visible on every line, now it is present mostly only on windows nodes, and this make things a little less cluttered, and more easy to aim on window node for edit (so this is not something totally positive, and have own drawbacks and compromises, and this is why this feaure is absent by the way).
Also, for quick inline marks, there is plan to add possibility assign several custom icons to nodes (that will make this feature even more useless).