Hi Pritpal, > The behavior of K_MBUTTONDOWN, K_MBUTTONUP, K_MDBLCLK is exactly > > as it should be and it's the same as K_[LR]BUTTONDOWN, K_[LR]BUTTONUP > > and K_[LR]DBLCLK in GTXWC and CL53. If you used some GT dirver which > > does not work like CL53 then it should be fixed. > > > > I had introduced these code way back in 2003 probably in GTWVT. > And these constants have been in use heavily since then. > > K_MMLEFTDOWN is generated when mouse moves while left button > is kept pressed, i.e., MouseMoveLEFTDOWN, .... > > A basic requirement if we are talking Windows.
But we're not. We're talking about a CUI window, which happens to be implemented in a Windows graphical window. Could be a Braille display, or a GTXWC display, it's an implementation detail the app doesn't have to know or care. Or if it wants to know, it should specifically request it. These broke compatibility, since some events are generated in place of some other events. Besides breaking compatibility, now to create an app which behaves the same under GTWVT and GTXWC and GTWIN, you'll have to add such ugly hack that iif( GTNAME == GTWVT, K_MMLEFTDOWN, K_MOUSEMOVE). Such is the root of unportable apps. I'm not saying to remove these, but we should have a mask to enable/disable it. Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
