> input commands. This implies that sequence of commands is often unimportant > in Therion?
In most cases, it is like this. Therion first creates all objects in surveys and afterwards it starts linking them together (e.g. controling map and station references). > Grid & Legend > I'm intrigued by the grid and legend input and map definitions. Have you > done something more refined than that generated with the thconfig export > command? What exactly would you like to receive? Here we have a lot of things in the TODO list. > Location of Maps > Do you create all of your maps in the INDEX file, or are some defined in the > lower hierarchal level survey.th files? My experiments so far have put my > single (unsuccessful) map definition in the lowest level survey.th file (to > keep it as close to it's source data as possible - and perhaps simplify my > INDEX file) Does this make a difference? Perhaps it is my mistake? I do it also usually like this. > Elevations > Completely irrelevant to bens example. But I just figured out why I could > not get projected elevations to work. > The syntax, complete with square brackets is; > > export map -projection [elevation 60 deg] -output cave.pdf > > (I was assuming the brackets denoted optional arguments, and so I was > leaving them out!) Well, we are also not very happy with input language - a lot of things are not intuitive... but it is too late to change it :( It was one of not very happy choices at the beginning. Regards, S.
