Your comments
I'm considering adding a "flatten branch" right-click action which would probably have the effect you're thinking of.
I'm also considering adding an option to essentially disable the automatic placing of opened tabs as children of their opener tabs. If this option was turned on, users could still manually organize their tabs into branches but Sidewise would just keep everything flat by default.
Ahh that explains it, thanks for that bit of research. Do you think this difference has something to do with the Metro UI?
My results are similar to Muntoo's.
Regarding pages with 'Sidewise' in the title: it certainly does seem that the only viable option would be to change the sidebar's title to something more unique, given that the TrayIt author has stated that no major development is planned and has not updated the app since 2008. This would be a pretty obscure option, but I will consider adding it in the "advanced" options.
Goran, regarding alt-tabbing: do you have the "keep Sidewise visible" option checked in the options page? That is specifically when I am seeing the alt-tab issue.
Planned.
I am also considering implementing the following options:
- Replace closed tab with its children in the tree (the current behavior)
- Promote first child of closed tab as new parent
- Replace closed tab with a new Folder row
You make a fair point. I am going to try using the approach you describe here for a while and see how it feels. Depending on how that goes, I will probably either replace the existing behavior with the behavior you describe, or add your described behavior as an option that the user can choose.
Most definitely a bug. Will fix.
Not sure about making the first opened bookmark the parent of the remaining bookmarks. I can see the usefulness of this approach, but I will need to research how practical this is to implement. Chrome doesn't really tell me "I'm opening these 5 bookmarks together right now", it just tells me that some bookmark is being opened 5 times in succession. So implementing as you suggest may involve a bit of a hack, which I prefer to avoid.
Since those opened bookmarks are opened into a new window, perhaps the fact that they are together under that new window is an equivalent effect?
Most definitely a bug. Will fix.
Can you explain what the desired behavior/goal is here?
Customer support service by UserEcho
I'll give this request some consideration. Two considerations:
- Chrome team is working on a keybinding API that extensions can use, but it is not yet out of the "experimental" stage. I am waiting to add any global keybindings of this type until they release this API, which will make it possible for such keybindings to work everywhere in the browser; without this, keybinds such as Ctrl+Tab would not work when viewing certain kinds of tabs, e.g. Chrome's own History, Downloads, Bookmarks tabs don't allow us to register keybinds without that API.
- I am debating whether this feature makes sense to add to Sidewise, rather than as a separate extension. My general rule for adding stuff to Sidewise is "does this affect Sidewise directly and work inseparably from Sidewise?" If not, then it suggests that feature might actually be something that would make more sense as a separate extension, so that for example somebody could install it to get that feature *without* needing Sidewise installed too.
So while I like this feature idea, I'm still considering whether to add it to Sidewise proper; and if I do it won't be for some time yet, until the keybinds API is released.