I meant only one Lclick or Ldblclick, after Windows evaluates what the user has just done. That would of course mean that a Lclick would take as much as a Ldblclick, but you were asking what other way it would be possible.

Roman
Moderators: Hacker, petermad, Stefan2, white
I recognize that my idea of the click event is not directly supported by Windows. My idea was that a click event is defined as the moment when a mouse button is back in the upper position exactly for a certain period of time (double-click delay). I assumed this because in my opinion it would make sense and because some years ago I encountered a kind of click event in Visual Basic (which is not my preferred programming language btw). Now I learned that the application receives more elementary events and must figure out the click event by itself.Valentino wrote:There's no such event as "click". There are the following events: lbuttondown, lbuttonup and lbuttondblclk. If user double clicks, Windows produces the following sequence of messages:
lbuttondown
lbuttonup
lbuttondblclk
If TC activated EditPath feature on lbuttonup, then double click would activate both EditPath and DirHotList. That's why this delay is needed.
Even if you're not a programmer think yourself: how can Windows predict (after first click) if user is going to make second click in the next moment or not?
Yes, seems so.jb wrote:but TC seems to ignore it
Yeah, it's so funny! I clicked as a mad clicker a minute or so, almost broke my mouse, but couldn't produce any double click!jb wrote:Try it out! If you set 'Double-click speed' to 'Fast' (maximum) then the delay is so short (100ms) that it is quite difficult to produce a double-click event at all