This is just a question out of curiosity, but why is the ReleaseCallback handler always executed, even if the mouse hasn't moved a bit (and hence DragCallback hasn't been executed either)? It sort of seems to break expected behavior, given that all of the other callbacks have a specified, documented order. It doesn't particularly affect me, but it made me wonder.
It's also worth mentioning, I suppose, that the documentation for ReleaseCallback (in the WindowDragHandler() file) says this:
Maybe that should be "release the mouse button that was pressed in the hotspot rectangle"? It doesn't matter where the mouse is when you release it, the ReleaseHandler will still be called. It's a minor nit, obviously, but since I'm on the subject...
It's also worth mentioning, I suppose, that the documentation for ReleaseCallback (in the WindowDragHandler() file) says this:
Quote:
ReleaseCallback - the script function to be called when you mouse down in the hotspot rectangle
ReleaseCallback - the script function to be called when you mouse down in the hotspot rectangle
Maybe that should be "release the mouse button that was pressed in the hotspot rectangle"? It doesn't matter where the mouse is when you release it, the ReleaseHandler will still be called. It's a minor nit, obviously, but since I'm on the subject...