Forums > MaxMSP

max5 key problem

May 2, 2008 | 4:08 pm

hello,

when i use the object key with the touch Q (113), its not working everytime.
does anybody have the same problem???

macbook leopard

thanks

freeka



Eli
May 2, 2008 | 4:50 pm

Q works fine for me.


May 2, 2008 | 5:22 pm

thanks for the reply
did you tried to hit others key and then to hit again on the Q??

cause he works ok and then stop to work when i played with others keys, sometimes it works again sometimes not…

weird i tried to reboot, remove the toolbox..


May 2, 2008 | 5:30 pm

On 2 mai 08, at 19:22, freeka wrote:

> thanks for the reply
> did you tried to hit others key and then to hit again on the Q??
>
> cause he works ok and then stop to work when i played with others
> keys, sometimes it works again sometimes not…
>
> weird i tried to reboot, remove the toolbox..

Thanks for the report. We are currently looking into it.

ej


May 2, 2008 | 5:41 pm

hey Emmanuel,
does that means you reproduced the bug?


May 2, 2008 | 6:11 pm

On 2 mai 08, at 19:41, freeka wrote:

> hey Emmanuel,
> does that means you reproduced the bug?

yes, with french keyboard layout.

ej


May 2, 2008 | 6:48 pm

The problem concerns ‘a’ on US keyboard and whatever key is in that location on a non-US keyboard. It will be fixed in the next update.

David Z.



Eli
May 2, 2008 | 8:01 pm

Is the "key" object only going to have 2 outputs (1 for ASCII, one for modifiers) from now on since Key Code is being abandoned, or am I incorrect in that assumption?


May 2, 2008 | 8:52 pm

The key code outlet is not really ASCII. It is a platform-independent keyboard code that uses ASCII for letter keys and other values for things like function keys. The code is intended to be same on both Mac and Windows, at least where keys overlap. For example, if you type shift+B you will get the same thing out of the key code outlet as you will if you typed lower-case ‘b’ whereas the character code will be different.

Unfortunately, I didn’t realize the nature of the new keyboard code until today when I started looking at this ‘A’ bug, but we will document what the codes are soon. It’s possible the codes will change slightly on the Mac for non-US keyboards in the next update. We’ll let you know.

David Z.


May 2, 2008 | 9:47 pm

Is there something to win when we find bug?
:D


May 2, 2008 | 10:43 pm

Just tested all keys and working well


May 3, 2008 | 7:11 am

the key code (2nd outlet) seems to ouput something very different from
max 4.x :

(french keyboard)
max4 max5
key ascii key code key code
q 113 0 (not working…A bug…)
s 115 1 115
d 100 2 100
f 102 3 102
g 103 5 103
h 104 4 104
j 106 38 106

Mathieu

________________
Mathieu Chamagne
mathieu.chamagne@free.fr

http://mathieuchamagne.com

http://www.maxobjects.com


May 5, 2008 | 12:56 pm

freeka schrieb:
> Is there something to win when we find bug?

Yes, of course, a fixed bug… (Or an explanation why it is a feature
and not a bug… ;-)

If you look at how fast bugs are fixed, this is a lot. There is no
equivalent to that speed in the software industry as far as I know…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


May 5, 2008 | 1:27 pm

:D


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