soundcyst

Hi, this has happened to me a couple of times since 5.0.1 or 2.

Every time I install the latest build (just went from 5.0.4 to 5.0.5), the max-keycommands.txt file gets reset to its default value.

I understand this is because upgrading is like reinstalling the application, but is there a way to configure it to keep the previous keycommands file?

I know I could make a copy to a different folder before upgrading, but I always forget to do that and always wind up having to reprogram my keycommands.

losing-keycommands-txt-every-time-i-upgrade

You can add your own personal key commands to a new file, perhaps called something like "my-keycommands.txt" and place it in the init folder with the original. This way it won't be overwritten when you upgrade.

ok. that sounds like it'll work, but it leaves the question of what happens to duplicated keys?

for instance, the default for 'i' is to insert a number object, but in my setup it inserts an int object.

if there are two lines present for the same key, which one takes precedence?

i'd imagine the most recently parsed line, but then there's the question of which order the files are loaded in..

In that case I'd recommend you just backup your max-keycommands.txt file to a different location outside of max's grasp and remember to copy it back to the init folder after every update. It's a bit of extra work but not exactly back-breaking and will solve any priority problems you might otherwise encounter.

Quote: the reverend wrote on Mon, 29 December 2008 22:18

----------------------------------------------------

> if there are two lines present for the same key, which one takes precedence?

I don't know, but the behavior ought to be deterministic and determinable.

In general, files in the same folder are read in alphabetical order (that's on Mac OS, on Windows I think it's creation order but I'm not sure). The other question is what Max does when it reads a second key definition. It seems pretty likely that the second definition will simply overwrite the first, although there's a slight change that the second definition is ignored. There aren't many other alternatives.

In short, you ought to be able to determine the behavior by one or two experiments.

Quote: the reverend wrote on Mon, 29 December 2008 22:18
----------------------------------------------------
> if there are two lines present for the same key, which one takes precedence?
----------------------------------------------------

In short, you ought to be able to determine the behavior by one or two experiments. 

ok, so after some experiments, it seems that files are read alphabetically (on mac os anyways) and that the most recent keycommand definition is the one that sticks (within file or between files).

Losing keycommands.txt every time i upgrade