paulthetall wrote: > > dimesio wrote: > > > > paulthetall wrote: > > > > > > Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive. > > > > Report it to Codeweavers. > > > Already done that. I catched in the conversation with them that on the Mac mousinput does not go back to xinput when it sees that xinput2 is not supported. that could be part of the problem. While XQuartz does have Xinput2 support, its not fully supported because there are certain functions that the information just isn't available to it... so in some cases it would need to fall back to Xinput
