key and keyup bug in Max5
Hi guys,
I've found a bug with the key and keyup objects in Max5 - when simultaneously clicking and dragging the mouse. It's currently effecting the performance of my glNavigator abstractions when used in Max5, so I thought I would post a simple example patch. See below.
Open it in Max4 and Max5 - notice the problem only occurs in Max5 (at least, on my machine).
Can anyone confirm?
best,
Zachary
It is a Mac only bug, and we are aware of it. Unfortunately, this is the way things are at the moment, and i'm not sure when it will be fixed, as it appears to to be something to do with the Mac OS key event implementation.
-Ben
Ok, thanks for letting me know Ben. That's quite an annoying bug, don't know how I'm going to get around it, but I'll trust that you'll fix it when you can.
Hmmm... You say it appears to be an issue with the OS key event implementation, but if that were so, shouldn't the bug also occur in Max 4.6.x on the same system? It doesn't, everything's fine in 4.6.x. That'w why I assumed it was a software bug in the first place.
best,
Zachary
Zachary,
From what I understand, this problem is due to fully supporting unicode in Max 5, which is a priority for us. It appears that this is something that Apple is going to have to fix.
You might have more luck with the hi object, though i understand how that could be dicey if you plan on supporting random computer setups.
apologies for the inconvenience.
-Ben
Hi Ben,
Are you aware of any progress made on this issue with Apple? Thanks.
best,
Zachary
I don't have any news regarding this. It appears to still be an issue in 10.6.1. Note that this isn't a problem on XP/Vista.
Again, apologies for the inconvenience, it appears that there is not a whole lot we can do about this right now.
-Ben
A year later, I am having the same problem in Max 5 on my macbook pro with OS 10.6.7 . has there been any development solving this issue? Any good workarounds?