max5 key problem

May 2, 2008 at 4:08pm

max5 key problem

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

#37475
May 2, 2008 at 4:50pm

Q works fine for me.

#129543
May 2, 2008 at 5:22pm

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..

#129544
May 2, 2008 at 5:30pm

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

#129545
May 2, 2008 at 5:41pm

hey Emmanuel,
does that means you reproduced the bug?

#129546
May 2, 2008 at 6:11pm

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

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

yes, with french keyboard layout.

ej

#129547
May 2, 2008 at 6:48pm

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.

#129548
May 2, 2008 at 8:01pm

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?

#129549
May 2, 2008 at 8:52pm

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.

#129550
May 2, 2008 at 9:47pm

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

#129551
May 2, 2008 at 10:43pm

Just tested all keys and working well

#129552
May 3, 2008 at 7:11am

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

#129553
May 5, 2008 at 12:56pm

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

#129554
May 5, 2008 at 1:27pm

:D

#129555

You must be logged in to reply to this topic.