Re: [Iup-users] IupToggle has slow response to mouse in Windows

[Roald R. <ro...@ri...>]

Some mouse drivers have something named "Tap to click" enabled in their
context menu. Some have ClickLock in properties. Disable all "add-on"
functions for mouse clicking in your driver settings.

Follow these instructions: http://support.microsoft.com/kb/266738

Anything solved?

Roald


> This probably is the same bug as a have reported long ago, but i
> experienced it with buttons. Clicking two times fast on a button do not
> show any visual feedback the second time, and what 'fast' means can be
> changed with the double click speed in control panel. This bug has been at
> least since iup 3.0 was released.
>
> /Robert
>
> 2012/7/20 Noam Postavsky <npo...@us...>
>
>> On Mon, Jun 18, 2012 at 8:17 PM, Noam Postavsky
>> <npo...@us...> wrote:
>> > On Mon, Jun 18, 2012 at 2:44 PM, Antonio Scuri
>> <ant...@gm...>
>> wrote:
>> >>> So, for instance, a double click will change the state
>> >>> only once.
>> >>
>> >>  I really don't know what it is, because internal processing in IUP
>> is
>> >> minimal. I actually commented all internal processing and behaved
>> just
>> the
>> >> same.
>> >
>> > It looks like Windows is helpfully converting the second click into a
>> > double click event. Setting the doubleclick speed from the Control
>> > Panel changes the responsiveness of the IupToggle.
>>
>> I confirmed double click messages are being sent by adding some
>> printfs to winLoopProcessMessage and winToggleWmCommand. I can't
>> figure out where the double click messages are getting ignored,
>> though.
>>
>> static int winToggleWmCommand(Ihandle* ih, WPARAM wp, LPARAM lp)
>> {
>>   (void)lp;
>>
>>   switch (HIWORD(wp))
>>   {
>>   case BN_DOUBLECLICKED:
>>     fprintf(stderr, "BN_DOUBLECLICKED\n");
>>     break;
>>   case BN_CLICKED:
>>     fprintf(stderr, "BN_CLICKED\n");
>>     break;
>>   }
>> ...
>>
>> static int winLoopProcessMessage(MSG* msg)
>> {
>>   if (msg->message == WM_QUIT)  /* IUP_CLOSE returned in a callback or
>> IupHide in a popup dialog or all dialogs closed */
>>     return IUP_CLOSE;
>>   else
>>   {
>>       switch (msg->message) {
>>         case WM_LBUTTONDOWN:
>>           fprintf(stderr, "WM_LBUTTONDOWN\n");
>>           break;
>>         case WM_LBUTTONDBLCLK:
>>           fprintf(stderr, "WM_LBUTTONDBLCLK\n");
>>           break;
>>       }
>>
>>     TranslateMessage(msg);
>>     DispatchMessage(msg);
>>     return IUP_DEFAULT;
>>   }
>> }
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
>> Discussions
>> will include endpoint security, mobile security and the latest in
>> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Iup-users mailing list
>> Iup...@li...
>> https://lists.sourceforge.net/lists/listinfo/iup-users
>>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Iup-users mailing list
> Iup...@li...
> https://lists.sourceforge.net/lists/listinfo/iup-users
>