If I build some sort of drag/drop framework for the Guide, then I need to
define how drag/drop should *look*.
I've been experimenting with my Windows system, dragging stuff around and
seeing what happens to the mouse cursor.
There seem to be three broad options:
Approach A (Windows XP Native Drag/Drop)
- On pickup (button1 down), either nothing happens or the mouse cursor
changes to a little picture of the thing picked up.
- When it's dragged over other programs (or the screen background) either
the cursor does not change, or it changes to a no-entry sign.
- If I drop when the mouse is a little picture, then either (a) nothing
happens, or (b) the target says it can't handle it, or (c) it accepts the
drop and something changes on the target window.
- If I drop when the cursor is a no-entry, then nothing happens.
Approach B (see sample ooDialog drag/drop program "userDlg.rex")
- On pickup, the mouse cursor changes to a no-entry sign.
- When it's dragged over other programs (or the screen background) the
cursor stays as a no-entry sign, but if it's dragged over an ooDialog dialog
that will accept a drop, then the cursor changes to a little picture.
- If I drop when the cursor is a little picture, something happens (assuming
the ooDialog code is well-mannered).
- If I drop when the cursor is a no-entry, then nothing happens.
Approach C (a possible alternative approach with ooDialog):
- On pickup, the mouse cursor changes to a little picture of the thing
picked up.
- When dragged over any non-ooDialog window, the cursor remains as a little
window, but if it's dragged over an ooDialog dialog that will NOT accept a
drop, then the cursor changes to a no-entry sign.
- If I drop when the cursor is a little picture, then if the target is an
ooDialog dialog that will accept a drop then something happens. Otherwise
nothing happens.
- If I drop when the cursor is a no-entry, then nothing happens.
Which of these options should be used (for the Guide at least)? My own
preference is, I think, Approach B.
Any thoughts? I did check my dusty 20-year-old CUA manuals, and while it
seems to suggest approach C, I know that the context of was the OS2 desktop
(as opposed to use by applications). So not a lot of help there...
Thanks for any thoughts,
Oliver
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
