keycodes gone
Physical keyboard codes are gone -- as I already said, the codes are not ASCII, but an attempt to provide cross-platform identity of the symbol on the key. We are evaluating whether we want to continue this strategy or return to platform-specific, keyboard-specific codes. We may do something to provide both.
David Z.
Ok, I'll rewrite some 120 lines in coll files. ;-)))
However, the function keys yield different key codes, but the same ASCII 16. That was probably the reason why I used them. If the key codes are gone, function keys will go, too, and for my performance patch I need them.
Did I overlook something? Any workaround I can use?
Hans
Ah, forgot the final thought... actually the function keys are the only keys on my keyboard that yield a key code (a 5-digit one). I'm reacting to your statement that "key codes are gone", and encourage you to keep them in for the function keys.
Hans
Hello, I Like to emulate photographique-long-exposure (open-shutter;
pose B) frame by frame
i make a mix of jit.slide and jit.op in float divide by the number of
frames accumulate (512, 10124...), then i record one frame and ad it to
the movie.
Of course, it need several day for shoot few second...
The problem is: max hang before I save, or webCam stop to answer... I
lost what I shooted, again and again...several day eatch time...
any hint? Lake of memory? driver of webCam? serial problem?
It will work beter with max 5???
It was so easy with video-script...
I can send more info if you can help
PBaes, laPoseLongue
Date/Time: 2008-05-03 22:59:12 +0200
OS Version: 10.5 (Build 9A3115a)
Architecture: i386
Report Version: 4
Command: MaxMSP
Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP
Version: ??? (4.6.3)
Parent: launchd [93]
PID: 3461
Event: hang
Time: 5.53s
Steps: 30
Process: MaxMSP [3461]
Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP
[...]
David Zicarelli schrieb:
> Physical keyboard codes are gone -- as I already said, the codes are
> not ASCII, but an attempt to provide cross-platform identity of the
> symbol on the key. We are evaluating whether we want to continue this
> strategy or return to platform-specific, keyboard-specific codes. We
> may do something to provide both.
I love the new standard, even if it breaks old code. For me key codes
didn't work in OS X. They did though in OS 9....
Now I can use them again. That the model is an american ascii keyboard
layout is convenient and intuitive. There is only a lack of explanation
of that change...
Please do not go back to platform and/or country specific codes, they
are useless. If someone needs it country specific, I have a simplified
unshift abhaXion, to translate big letters to small ones:
Stefan
save as unshift.maxpat
--
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com