akee-rf

when i use the object key with the touch Q (113), its not working everytime.

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

max5-key-problem

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 reply
did you tried to hit others key and then to hit again on the Q??

weird i tried to reboot, remove the toolbox..


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

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

hey Emmanuel,
does that means you reproduced the bug?


> does that means you reproduced the bug?

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

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.

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?

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.

Is there something to win when we find bug?

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


the key code (2nd outlet) seems to ouput something very different from 

            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

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 Chamagne
mathieu.chamagne@free.fr

http://mathieuchamagne.com
http://www.maxobjects.com

> Is there something to win when we find bug?

Yes, of course, a fixed bug... (Or an explanation why it is a feature 

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

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 Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


max5 key problem