Re: SS_NOTIFY and mouse clicks

new topic     » goto parent     » topic index » view thread      » older message » newer message

Derek Parnell wrote:
> Tommy Carlier wrote:
> > Derek Parnell wrote:
> > > What's an "unclick" event? A click event is a combination of Mousedown
> > > followed by MouseUp, within the double-click period, and within a few
> > > pixels of each other.
> > Why does it have to be within the double-click period? If I press down
> > the mouse button, I wait a second, and release the button without moving
> > the mouse, shouldn't that count as a click?
> Maybe. On things like buttons and menus, things that have a specific 
> Microsoft generated click event, the time delay is not significant. But on
> things like bitmaps, windows, labels etc... it might be.
> 
> To me the 'concept' of a click is a short-sharp action (relatively speaking)
> which is different from a mouse up/down event. THat's why I choose to 
> implement it this way.
> > Certain people have heavy fingers, and when they press down a mouse button,
> > it's physically tough to lift their heavy finger to release the button.
> > 
> > I think it is important to make your applications accessible, also for
> > people with heavy fingers.
> Such people already tend to have set their double-click period to a
> reasonable length for themselves. 
> 
> However, I can easily set up Win32lib so that the coder has a choice over
> this aspect of a click event. It'll be in the next version for you.

Well, I don't need the feature, so you don't have to do it for me.
The reason I'm asking, is because I'm working on Win4Eu, and I've just
implemented the Click-event myself. I've looked at your implementation
in Win32Lib, and I've looked at Microsoft's implementation for the
.NET framework (which is a lot more complicated).
Their implementation doesn't even check the mouse movement. They just
check if the mouse cursor is still on the control. So if you press the
mouse button on a control, you move the cursor around (over other controls),
you move the cursor back over the original control and release the button,
a click-event is generated.

My current implementation is a bit of both worlds: it does check if the
mouse has moved a lot, but it doesn't check the time between pressing
and releasing the button.

--
Recycle your pets.
tommy online: http://users.telenet.be/tommycarlier
tommy.blog: http://tommycarlier.blogspot.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu