1. General
  2. Idéer
+2
Under vurdering

Don't replace the tab when I click link there - add child node instead

Nikolay Ugarov 11 år siden • opdateret af vladyslav volovyk 11 år siden • 0
I use TO for a while, and as I'm adapting, I start to get more and more of it.

But one thing I cannot overcome: having saved tab open, I just click links there, instead of opening in new tab. Then I realize my "bookmark" is gone and I have to dig through history to restore it.

To solve this I'd propose to have the tab "pinned". And if you click a link in pinned tab, it doesn't replace it in tree but added as a child. How exactly you pin it  - I'm not sure - might be explicit button. But better just have the rule - if it was saved once (explicitly or implicitly), have it pinned till I delete it.

Svar

Svar
Under vurdering
vladyslav volovyk 11 år siden
Yes, such problem exist. I sometimes also annoyed by this behavior.
Need to think what will be the best way to deal with this problem, i for example thinking about adding a separate history list for tabs in Tabs Outliner.

Also there is already implemented yet not released meantime possibility to view tree in any point in the past, a history view of the tree. It will of course not a solution, but at least information will not lost and can be easily restored by dragging from history view to the current view.

Take note that there is 2 additional ways to restore tabs without affecting the source hierarchy.
  1. You can alt/ctrl drag the whole hierarchy - this will create a copy, and then restore the copy.
  2. You can shift/ctrl click on tabs and this will restore a link in new window (shift) or as new tab in last selected window (ctrl), without affecting and activating the source node.
Under vurdering
vladyslav volovyk 11 år siden
Yes, such problem exist. I sometimes also annoyed by this behavior.
Need to think what will be the best way to deal with this problem, i for example thinking about adding the separate history list for tabs in Tabs Outliner.

Also there is already implemented yet not released meantime possibility to view tree in any point in the past, a history view of the tree. It will of course not a solution, but at least information will not lost and can be easily restored by dragging from history view to current view.

Also take note that there is view additional ways to restore tabs without affecting the source hierarchy.
  1. You can alt/ctrl drag the whole hierarchy - this will create a copy, and then restore the copy
  2. You can shift/ctrl click on tabs and this is also will restore the link in new window (shift) or as new tab in last selected window (ctrl) without affecting and activating the source node.
Svar
Under vurdering
vladyslav volovyk 11 år siden
Yes, such problem exist. I sometimes also annoyed by this behavior.
Need to think what will be the best way to deal with this problem, i for example thinking about adding a separate history list for tabs in Tabs Outliner.

Also there is already implemented yet not released meantime possibility to view tree in any point in the past, a history view of the tree. It will of course not a solution, but at least information will not lost and can be easily restored by dragging from history view to the current view.

Take note that there is 2 additional ways to restore tabs without affecting the source hierarchy.
  1. You can alt/ctrl drag the whole hierarchy - this will create a copy, and then restore the copy.
  2. You can shift/ctrl click on tabs and this will restore a link in new window (shift) or as new tab in last selected window (ctrl), without affecting and activating the source node.

Kundesupport af UserEcho