Referring to bug:
http://bugs.winehq.com/show_bug.cgi?id=434
Under normal circumstances the mouse button doesn't get released in certain applications. These include, Macromedial Flash 5, MS Visual Foxpro 5/6, and Adobe Illustrator 8.
I'm working with FoxPro 5. (I have a demo app in the bug report) In *MY* testing, I've noticed that the following command allows the mouse button to be released.
wine --debugmsg +scroll,+event,+toolbar,+gdi,+heap vfp.exe
If, while running under this command, I _hold_ the mouse button down - longer than a 'click', it will not be released. This seems like a timing issue to me, and started after functions were moved into the wineserver.
Not that I know anything about how Wine is setup, but could the 'buttonup' be 'lost', or sent out of sequence, causing it to not be executed? And that sequence is slowed by the debug message enough, that a longer 'buttondown' duration is needed before the bug shows up?
Where would be the best place to insert a delay, or extend the timing for a single click (So only the mouseclick function is 'slowed')?
I'm sure this isn't the best bug report ever sent, but any suggestions would be appreciated. ;)
Rick