Hey guys,

thanks for taking a look at it!

@Ottawa:
How many hours it took me to do this? Well, the third attempt I would say something between 5-10 hours, including a *lot* of testing and debugging. All three attempts together... I really can't remember, it has been a long time since attempt #2 xD
To your questions:
1) It is an odd restriction "mouse_ent" has. I intend to do the selection in a different way in the next release, but "mouse_ent" seemed to be the easiest way to get things to work for now.
2) Hm... I think there is no way to exit the program without clicking the "X"... good point, I'll include that as well!
And the "bug" you've discovered: whoops, I completely overlooked that one... The thing is: The movement using the keyboard as it is now is very un-intuitive. Originaly I planned to use the mouse to move a tree, like it is done in WED for example. But it proved not to be as simple as I thought so I put the keyboard movement in place for testing purposes so I've been obviously a little bit careless when creating those info-images... sorry about that.

@Pappenheimer: As far as I know you can subdivide a terrain in MED or change the number of its vertices horizontally and vertically and you may also "resize" it by entering new values for hight and length in quants - but you can *not* scale the terrain using a scale factor like you can do with a model (at least not with the "Change Terrain Size" command, but I can't see any other commands which look like they could do that in my "Edit" menue...) You could get the size of your terrain in quants, get the scale factor from WED, calculate the result and enter the new size in MED, but I think in this specific case it is easier to convert the whole terrain into a model, scale it, and convert it back to a terrain afterwards. Please let me know if I'm mistaken here...

@Everybody: Besides all the positive aspects of TreeCreator, I'm facing one major problem. The "vegset.c"-files are basically lite-c-files with thousands of lines in them (1500 trees generate way over 10.000 lines of code in the exported vegset) and the compiler checks *every* one of them (like it does with any ordinary lite-c-file) which causes way longer compilation times - most probably the largest draw-back of TreeCreator. What I need would be a sort of a command which tells the compiler that the "vegset.c" is something like an "external source of code" which does not have to be de-bugged and checked for errors like the rest of the files. Any ideas about that?


Alan