Wookey wrote:

Ah- My build of therion is missing that menu item, which would explain why I was confused. Looks like the Debian build of therion does not have this facility, no doubt due to missing libraries etc.

Yes. We are using modified version of one French OpenGL TclTk parser. Therefore it's included in therion distribution. In any case, I'm already working on a new version of therion 3D viewer written in wxWidgets, but it's going very slowly (I have to learn a lot of new things).

I had a lot of trouble with therion 'path not connected' type messages when trying to create the demo. We need to work out some much more reliable way of getting error information to users. Currently if you do something wrong with area paths or joins that don't work you effective get an error of 'something is wrong somewhere' which is hopeless if you have just drawn a big chunk of cave.

You are right. We did not face such problems very often, therefore we did not make error detection effective. If error is generated by metapost, it is very difficult to fix. It would probably help, if metapost will also report source position of errors.

Even when there is a simple error, the error gives the line number; whilst the xtherion viewer shows 'item number' next to each entry - there is no way to relate these. As the whole thing is integrated it could easily show you the offending line - or even put you there in one of the windows.

Yes, I wanted to do this several times, but it is not so simple (to connect line number and xtherion's item number). But it is possible, so I will put this on the TODO list. Thanx for your suggestions, S.