Your comments
While Chrome is active, can you use Win+Right / Win+Left keys or Win+Shift+Right / Win+Shift+Left keys to move the Chrome window and Sidewise sidebar to the desired monitor? These key combinations are built into Windows 7 to allow you to move things between monitors even when you can't see them.
That's a good idea; the extension API allows me to specify a minimum version, and I've been working on the assumption that everybody will be using at least the current stable version of Chrome.
As far as stuff vanishing, please let me know if you see it again. Meantime I am looking into improving how Sidewise stores its data, as I think Sidewise may be sometimes bumping into a max-storage-quota issue with its current method. And/or Chrome may have recently developed a problem with the storage mechanism I use that causes it to sometimes lose all the extension's saved data.
Fix is published.
--
Fixed, will release shortly.
--
Confirmed. Can you please give me a URL where you are experiencing this problem?
Fixed, will release shortly.
--
Confirmed. Can you please give me a URL where you are experiencing this problem?
I don't have a date for this, but consider it on the priority todo list.
What I would really like to do is just rethink how the tab-ordering/nesting logic works overall, and create options for each specific case, e.g. "where to place new tabs opened via address bar", et al.
Confirmed. Can you please give me a URL where you are experiencing this problem?
What OS are you using?
I'm running Windows 7 here and the text in the Notepad pane does wrap as one would expect for me.
Remembering window positions accurately between sessions is on the todo list.
Well, try enabling "Keep sidebar visible next to dock window". Even in 'undocked', this should cause Chrome and Sidewise to raise together when you focus either.
This will not cause Chrome and Sidewise to minimize together however.
Customer support service by UserEcho
I understand your frustration. I'm not sure exactly why it's forcing things onto monitor 1 for you; on my machine Chrome/Sidewise open on the same monitor (monitor 2 for me) that they were on during the previous session. It's definitely a bug, and not working as intended.
For what it's worth, the monitor detection routine is only present because of limitations in Chrome which have prevented extensions from accurately obtaining the resolution of the current monitor as you suggest. In short, Chrome would often report the resolution of the wrong monitor when asked for it, which could badly break things. The existing monitor-detection routine was the best workaround I could figure out for this issue.
These "wrong monitor" Chrome bugs have been largely fixed recently, so I have a rewrite of the monitor/resolution code on my priority todo list. My hope is that when the rewrite is done, I will be able to do exactly as you suggest, and can drop the existing monitor detection routine entirely.