How would you differentiate between normal vars and custom vars, if they all share the same syntax?
One solution would be to add in the
Project Options->Custom variables tab, split in two listboxs:
-Project variables-Global variablesI'm not sure a different syntax would be needed (from the user standpoint). You could replace the global ones from $(VAR) to $(#VAR) internally if it makes that more easy to code.
Another plus on using that: It'll be a bit more user-friendly, as you will not have to tell users: "If you want to create a global variable use it somewhere".
Hmm, nice, type in three edit boxes. Do you know of many common libraries that don't use the /lib and /include convention? I don't understand what the gain would be.
And about $(WX_PREFIX) you mentioned, Thomas already posted that some things will be changed in global vars to make them more adaptable.
Mm, now that I think, 3 edit boxes will not be necesary. See:
Example:
User creates
$(WX_DIR) Global Variable . With a default value of
empty string.
User creates
$(WX_INCLUDE) Global Variable. With a default value of
"$(WX_DIR)\include".
User creates
$(WX_LIB) Global Variable. With a default value of
"$(WX_DIR)\lib".
The "default values" would be entered from the "Create new global variables dialog" I suggest above
(@Project Options->Custom variables tab).
The main point of what I'm seeing the current ones as a shortcoming, is that appart from being (at first sight) more logical/user-friendly, it's not hardcoded to C++.
Please, don't take this as "the right/wrong thing", all I'm saying is that the global variables weren't discussed in the forum, and as I'm seeing shortcomings with it, better to discuss it now (better to be safe than sorry).
