On Mon, Jan 9, 2012 at 7:23 PM, Chip Davis <[email protected]> wrote:
>
> BTW, just for completeness, the cursor should not change on button
> down. It should take button down plus dragging outside of the local
> box, right?
>
Right, it should be done that way. You don't want to start a drag
operation if the user is just clicking the button. And, it is almost
impossible to click the button down and release it without having moved the
mouse position while the button was still down.
One of the Mouse methods is dragDetect() which gives access to the Windows
DragDetect() API. What the OS does is track the mouse while the mouse
button is down and determines if the button stays down until the mouse
leaves the drag rectangle. If so, it returns true that the user is
dragging.
The size of the drag rectangle is configurable, it can be made larger or
smaller.
By using that method, you can hold off starting a drag operation until you
are sure the user really intends to drag something.
>
> One metric I use is the "How easy is this behavior to explain to my 84
> year old mother?" :-)
>
>
>
That's a good metric. <grin>
--
Mark Miesfeld
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
