DeviantART is counting down to its 100 millionth deviation! Join in on the fun and take a look back at some of the most noteworthy deviations we've seen along the way. The deviant who uploads the 100 millionth deviation could win a special prize, too. Hurry, we're going to hit the 100 million mark soon!














Comments
--
For people who want to buy a new camera, READ THIS
New Ape!!!!!!!!!!!!!!!!!!!!!
--
HARDCORE WILL NEVER DIE
Great start, this is realy helpful for complex scopes... Thanks a lot for creating this!
Boringly obvious suggestions
some of you probably know the "Resize" entry of normal windows' window menues.
when you select this, a WM_SYSCOMMAND message with wParam=SC_SIZE is sent to that window.
What my APE does is simply checking if the user clicks on the AVS editor's border and then sending that message to the editor window.
Unfortunately, sending that message centers the mouse on that window.
Normally, the editor window should be notified of that through a WM_SETCURSOR message, which i can intercept and then reset the mouse to the border.
That message is normally sent to the window/control directly under the mouse first and should normally be passed to the parent window and in the end, to the editor window.
However, some windows/controls do not pass this message to the editor window so i cannot intercept that message and reset the cursor properly. this was/is causing the mouse bug.
To work around this I simply made the dialog invisible while the WM_SYSCOMMAND is being processed and make it visible again when the WM_SETCURSOR message is received.
In short terms: The mouse bug occured because some messages went to the wrong receiver and was not forwarded properly
--
Visit My Website Submit Some Style
Previous Page123Next Page