Max5 Newbie - key commands
I recently just upgraded from max4.6 to max5 and i'm finding out all kinds of things: objects that don't work anymore, new features that disrupt my old patches . . . It's all fine, really. Kind of a pleasant re-discovery of Max. But i'm currently wondering if there's a way to turn off max5 key commands. I used [keyup] to customize my own commands in most of my patches and now those commands (and some of my patches) are non-functional due to the max5 key commands. it's killing my efficiency. Any thoughts? Thanks!
drew
look in Cycling 74 folder, init, max-keycommands.txt:
max definecommand n patcher insertobj newobj;
max definecommand m patcher insertobj message;
max definecommand r patcher insertrecent;
max definecommand p patcher insertobjectpalette;
max definecommand b patcher insertobj button;
max definecommand t patcher insertobj toggle;
max definecommand i patcher insertobj number;
max definecommand f patcher insertobj flonum;
max definecommand c patcher insertobj comment;
max definecommand j patcher inserttextobj jit.;
max definecommand P patcher inserttextobj "newobj @presentation 1 @text ";
max definecommand l patcher inserttextobj live.;
so... easiest would be to just move the file elsewhere (probably out of any search path?). You have to restart Max to see the changes. Or you can remove some lines to free up certain keys.
I also tried renaming it to "blah.txt" but it still loaded. interesting, how was THAT found??
Then I took out the line for "m" making a message, resaved, restarted Max. Good, all the other commands worked, but not "m". Then I made a message box with the Palette, put in the same command to Max (with semicolon at start, not at end like it is in the init file):
;max definecommand m patcher insertobj message
clicked it, lo and behold, you can add new key commands on the fly. So the init file is just a bunch of these commands that are loaded on startup... well, now that I think of it, duh, what else would it be?
Probably in the docs but haven't looked for that specifically until now!
Have fun...
You could save everything in the "init" folder in one big text file and call it what you like, it would all still load as expected. They're only split up to keep things organised. Good to know you can allocate them dynamically though.
One thing I would suggest is that if you do redefine these commands you call your file something new, as updating max will replace the max-keycommands.txt file and any changes made directly to that file will be lost.
Awesome! Thanks all!
drew