I'd like it if anything starting with "USER" would be treated as a user variable instead of just USER1..USER32. The numbered variables are cryptic; it's hard to remember which is which and easy to end up using a password to find a plugin script. Also, it makes the commands overly dependent on a specific resource.cfg setup. With meaningful names, it would be easy to see what a given command requires, and it would be possible to copy commands between installations without needing to renumber all the user variables.
USER_PLUGIN_DIR instead of USER1
Tags: configuration
Comment
Comments (2)
Martin Fuerstenau said:
Sorry - but this is complete scrap. These are userdefined macros. what you are doing with it is your problem. You can store the birthday of your Mom in USER1 (or any other). To store the plugin directory is only a default and not a fixed assignment. I myselb use the complete path in the command difinietions because I have several plugin directories.
1 month ago
Steve Fink said:
I think you may have missed the point. Yes, these are indeed user-defined -- as are variables in any programming language. But at some point someone came along with this brilliant idea that you could allow programmers to name their variables whatever they wanted to. While certain programmers ignored this and merely named the variables with the number of the machine register they hoped the value would be stored in, others made use of the capability to name those variables by what they were using them for. Yes, this requires a translation layer that maps names to register numbers (or memory locations, or whatever), but computers are pretty good at that.
I am not saying that USER1 should be renamed to USER_PLUGIN_DIR. I am saying that the names of user-defined macros should be defined by the user.
1 month ago