Forums > MaxMSP

Max 5 – key obj – #65 sticks


April 23, 2008 | 6:37 pm

I’m hoping that there is a way around this and that it is only effecting my computer, but this is a really annoying bug:

*how to reproduce*
1. Create a new patcher
2. Create a key object and a print object
3. Connect the leftmost key outlet to the print object
4. Hit any keys you want and it should work as normal
5. Try hitting "A" either shift-a or caps[on]-a
6. Max will recognize the first press but won’t respond to shift-a again until you relaunch Max 5.

I’ve seen this bug in every patch that I have that uses the key object when I load them in Max 5.

Any ideas?


Joc
April 23, 2008 | 9:17 pm

I get the same on Mac OS X Tiger, however the it seems to reset if you press another letter with shift i.e. press Shift-F then you can press Shift-A again, but only once.

Joc

April 23, 2008 | 9:50 pm

That’s so weird. I get the same thing where I can push command-a after shift-a sticks and it will unstick shift-a once.

Maybe this has something to do with new keycommands?


Eli
April 24, 2008 | 1:40 am

For me, the key object only sends out ASCII code.

The first outlet sends out the normal ASCII code AND the second outlet, which should send out the Key Code, also sends the same thing (except for a difference between enter and return).

That’s a pretty big problem, and hopefully it has been addressed already.
Anyone having the same problem?

tl;dr

Key object only outputs ASCII code for me.

Viewing 4 posts - 1 through 4 (of 4 total)

Forums > MaxMSP