Ваши комментарии
In theory there no need to restore everything if you not plan to read the tabs content immediately So my advise - try to restore only the tabs you plan to view immediately.
Of course i understand that it is easy to say then form such a habit...
This proposed feature conflict with some other cases. So unlikely it will be implemented. But i will think about this. Especially if it will gather some votes of other users.
UPDATE
After some thinking and reading i start to understand that maybe this case will represent some category of users who use TO in somewhat special way, not as tab addicts who open hundreds NEW tabs every day (as i am), but somebody who have own set of older tabs for many months and really like to restore it every day as as it was day before.
Well.. not sure why need to restore it every day now, this was needed before, as the only other option was to bury all the tabs in some sort of hidden list of some session manager, but in TO even saved tabs is present in current context, but... worth to think about this some more i think.
UPDATE
Seems it is really needed. And more, remembering the state of tab nodes (open/closed on their window shutdown) was needed for interoperability with Chrome restore feature. So very probably i need such functionality anyway.
Maybe a good idea is to done this as Alt-DblClick.
Will actually implement this..., but first there is real urgency to finally ship new storage engine. Have 30000 saved nodes and current one start to really slow down the application and user interface on periodic saves for such a big tree. I think this affect many users.
Also new engine will enable the road to cloud storage and undo redo and one more very interesting and worthwhile feature which will open a full new dimension actually for this project.
That rewrite also must finally fix the annoying crashed windows on restart and make Chrome restore feature to work smoothly with Tabs Outliner tree, by correctly merging saved in last session on exit windows with the windows reopened after restart.
So If you can wait a little (a month) i will be very grateful. I will do this despite you donation so if you decide to get refund - no problem. Simple send a email - i will refund. But meantime the priority is in the other places.
You are free to remind me about this my promise in a month : )
PS By the way, i am really interesting in how it is going for you and you one big window scenario is there some other annoying things and so on. But this thread is really worth to delete - it is too big and unreadable now - maybe start some other thread (if this is something which can attain some votes of other users) or simple write me directly on email.
Will actually implement this..., but first there is real urgency to finally ship new storage engine. Have 30000 saved nodes and current one start to really slow down the application and user interface on periodic saves for such a big tree. I think this affect many users.
Also new engine will enable the road to cloud storage and undo redo and one more very interesting and worthwhile feature which will open a full new dimension actually for this project. So If you can wait a little (a month) i will be very grateful. I will do this despite you donation so if you decide to get refund - no problem. Simple send a email - i will refund. But meantime the priority is in the other places.
You are free to remind me about this my promise in a month : )
In theory there no need to restore everything if you not plan to read the tabs content immediately So my advise - try to restore only the tabs you plan to view immediately.
Of course i understand that it is easy to say then form such a habit...
This proposed feature conflict with some other cases. So unlikely it will be implemented. But i will think about this. Especially if it will gather some votes of other users.
UPDATE
After some thinking and reading i start to understand that maybe this case will represent some category of users who use TO in somewhat special way, not as tab addicts who open hundreds NEW tabs every day (as i am), but somebody who have own set of older tabs for many months and really like to restore it every day as as it was day before.
Well.. not sure why need to restore it every day now, this was needed before, as the only other option was to bury all the tabs in some sort of hidden list of some session manager, but in TO even saved tabs is present in current context, but... worth to think about this some more i think.
UPDATE
Seems it is really needed. And more, remembering the state of tab nodes (open/closed on their window shutdown) was needed for interoperability with Chrome restore feature. So very probably i need such functionality anyway.
Maybe a good idea is to done this as Alt-DblClick.
And please, if you donate because I was saying that i will implement this - please, wright me right away from the email you make a donation. I will refund (please do this right now, or at list in a closest week, till I not spent this money).
Start to think about this case and seems it is introduce so many dependencies and weird scenarios that I am not very sure now it will be implemented actually.
So if you want i can done this only for you in separate private install.
Really devoted now completely to next major release which introduce cloud storage and many big features. And this small feature also of course.
Have no time to thoroughly retest everything to upgrade current branch confidently for everyone.
Yet i cannot promise anything specific of when this next major release will be released.
I think I found you donation : )
thanks once again.
Thinking about to done this feature quickly and dirty just for you....
How about separate private install ?
Is it ok for you (yet you will lost ability to upgrade)?
Or you will wait a litle more for it?
Also it is actually introduce a new type of node. A saved tab which was saved at a time of window close... yet I plan to do this anyway but there is some other plans also, and not only in this project but in my life in general.
Сервис поддержки клиентов работает на платформе UserEcho
Never test TO in incognito if for true, thanks for a bug report