Open GoogleCodeExporter opened 9 years ago
Current behavior has changed slightly:
1) WZ usually appears near the cursor.
2) WZ appears near in the old default position if no cursor info. is available.
3) Desktop boundaries are, of course, still observed.
The only thing left to do:
* A "stick" option to stick the main/sub window to another window. I need to consider how to handle this with respect to alt-tabbing. Also, dragging the parent window will require AttachThreadInput of something similar.
* Sub-task: WaitZar is a top-level window, so sticking to "the last used window" might be hard to detect. This task should still be relatively easy to add for 1.8.
Original comment by seth.h...@gmail.com
on 18 Aug 2010 at 6:55
Now that we can click on windows, I want to add:
1) A config option for enabling the "stick" feature.
2) A button which appears (sentence window? main window?) --when you click on it, it captures the mouse and lets you move around. When you click once more, it takes the window you clicked and locks to that.
Original comment by seth.h...@gmail.com
on 22 Aug 2010 at 4:01
The two items above are easy. Actually tracking the window is harder. I can see
two approaches:
A) Set WaitZar's main/sentence windows as child windows to whatever is shown. This will NOT destroy them, as they are not "owned" by the window.
http://msdn.microsoft.com/en-us/library/ms632597%28v=VS.85%29.aspx#parent_owner_handle
B) Use AttachThreadInput to capture the WM_MOUSEMOVE (or similar) message. Then, use if (hwnd==capturedHWND) { track(); } in the code. We'd have to take care to release the hwnd as required.
I'll try option A first. This will definitely be turned off by default. Still,
should be fun to play around with.
Original comment by seth.h...@gmail.com
on 20 Sep 2010 at 11:14
Original issue reported on code.google.com by
seth.h...@gmail.com
on 2 Jul 2008 at 3:53