On Thu, Jan 5, 2012 at 1:50 PM, Oliver Sims <
[email protected]> wrote:
> Back in CUA days, there was a move to call the left mouse button "Button 1"
> instead of "Left Button" on the grounds that for left-handed people it was
> not a left button but a right one. I suppose that particular battle was
> lost
> a long time ago, but if not, would it be a good idea in ooDialog to use the
> CUA standard?
>
(Sorry for the late reply, I started this yesterday, then didn't have time
to finish it.)
I'm open to discussion, but in my opinion the answer is no.
For a left-handed person, the button being used as the primary is still the
right physical button. But, it is only their primary button *if* they have
elected to ask the OS to swap the mouse buttons. For the ooDialog
programmer, it is unknown if the user is left-handed, or if they choose to
swap buttons.
If the buttons are swapped, then the OS generates the LBUTTONDOWN event
when the user presses the right button. You can try that yourself with the
mouseTrack.rex program. It is the same for other things related to the
mouse buttons. The OS handles this for the programmer, so that the
programmer doesn't have to worry about it.
So, in ooDialog you want to connect a mouse button event. You are going to
use a keyword to specify the event. There are already a lot of keywords in
ooDialog that use LBUTTON and RBUTTON, so it doesn't make sense to me to
use 1BUTTON or BUTTON1 here. It adds just one more inconsistency in
ooDialog. If we were starting from scratch, then it might be a good idea.
The other thing is, in the past keywords were chosen that differed from the
actual Windows flags they represent. Then, when I went to enhance a
functionality to bring it in line with what was available in Windows, I ran
into conflicts. My strong feeling now is that the keyword should be the
same as the Windows flag it represents. Using different keywords then the
flag leads to confusion in the implementation code and adds no benefit for
the user, the ooDialog programmer.
Using the same keyword as the Windows flag helps prevent future conflicts
when either Windows adds enhancements or enhancements to ooDialog are made.
--
Mark Miesfeld
------------------------------------------------------------------------------
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
