Thanks for the report! :-)
1. the list control in the project properties is huge (expands to the whole height of the panel) (but also see 4)
Mmmh... not for me. Mind sending me a screenshot? It is setup to be as width as the propeties dialog... but you really mean the height?!
2. it would be clearer if the custom sets list control appeared above instead of below the list of environment variables in environment settings (but also see 4)
Ok - can do that (had in mind to move the label, too...).
3. the environment variables show up in the child processes as they are supposed to. are they also subsituted in any of the build options?
Yes, they are. The project specific envvars are applied as soon as the project jets activated (consult the C::B debug console to see what exactly is going on - there is currently a lot of debug messages.). By using default user variable expansion, e.g.
$(MY_VAR) you can access the envvars during build.
4. it seems that the environment sets are kept in the program settings. would the projects be more portable if kept in the project settings?
Yes and no. I decided to do it like that for several reasons:
1.) You will need C::B anyway for this feature to work so it's easier to keep the sets in one place.
2.) You can easily share envvar sets between C::B users using the cb_share_config tool.
3.) I wanted to be compatible to the GCV's as they are working the same way (e.g.
#(My_VAR)).
In the end I believe maintaining them at one place is easier. Imagine you have an envvar set for a specific platform. If you have 10 projects you would have to maintain all 10 projects if *one* envvar changes. This seems not convenient to me. But I'm open for discussion...
With regards, Morten.