I've got back to Therion after a long period of working all the time. I have a _lot_ of cave to draw up... Current Debian Status: You may recall that I discovered in October that the 0.3.3 version of therion I was building should have had the TOM/OPenGL stuff in it, but didn't. So I've started packaging the Tom library for Debian so that Therion can use it. This is not a trivial job to do properly, and I haven't yet succeeded in building a Debian Therion with 3D support, but expect to in the next couple of weeks. This probably won't quite make it into the imminend debian stable release (but the existing therion 0.3.3-1 is). Connecting scraps: My biggest problem at the moment with Therion is how to split up scraps and connect them nicely. I am drawing over previously-drawn-to-scale scans. given that I want to join scraps at convenient (low detail/logical) places and not the edges of scans, how can I best do this so they match up? I can keep adding background drawings into one file and draw all the scraps that way but I will end up with a huge file that is very slow to load and manipulate, even if I turn off some images which I am not longer directly using. As soon as I start a new file with new background images then I can't see where the old scrap ends so I don't know where to start the new scrap. How do others deal with this problem? How well does therion deal with the lines significantly overlapping, or not reaching each other? Do you always add in the adjoining scan so that you can see what it looked like? This still doesn't really help with remembering how far you drew up to on the last scrap. I feel I am missing something obvious here, as the existing system doesn't seem to work. How is everyone else managing it? How can we make it easier to use? Bugs: I found a couple of bugs, one serious. (using therion 0.3.3-1 on x86) 1) If I have an image (PNM) of size 1672x2333 then only about half of it is visible in the map editor. This makes it impossible to draw round. Is this expected? Should images be limited to some size before they can be importad as background? If so what is that size? 2) if keys used to change mode (F2, F1 etc) then menu top bar disappears.('normalize' window size fixes it). Can anyone else reproduce this Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/
On Wed, Dec 15, 2004 at 04:19:55PM +0000, Wookey wrote:
2) if keys used to change mode (F2, F1 etc) then menu top bar disappears.('normalize' window size fixes it). Can anyone else reproduce this
I believe I've seen that happen a couple of times, but couldn't work out how to reproduce it on demand... Cheers, Olly
+++ Olly Betts [04-12-15 17:18 +0000]:
On Wed, Dec 15, 2004 at 04:19:55PM +0000, Wookey wrote:
2) if keys used to change mode (F2, F1 etc) then menu top bar disappears.('normalize' window size fixes it). Can anyone else reproduce this
I believe I've seen that happen a couple of times, but couldn't work out how to reproduce it on demand...
I fogot to say that there needs to be no file loaded in the window you change to. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/
Wookey wrote:
succeeded in building a Debian Therion with 3D support, but expect to in the next couple of weeks. This probably won't quite make it into the imminend debian stable release (but the existing therion 0.3.3-1 is).
Do you need some support for this? In any case, I stopped developement of therion 3D viewer. I came to conclusion, that TclTk is too slow for that... I have started new project, but it will take some time again, there are a lot of problems. I have one question. Would it be possible to enter to survex .3d format an arbitrary triangulated surface, not just LRUD data?
where the old scrap ends so I don't know where to start the new scrap. How do others deal with this problem? How well does therion deal with the lines significantly overlapping, or not reaching each other?
When we were doing this, we marked scrap ends by red lines on the scan images. In fact, we usually prepare bitmats, that we are using as background. We have original scans at 300dpi, but for backgroud, we subsample them to 150dpi, adjust contrast and brightness, draw scrap ends with red line etc. If some detail is not clear, then we have a look at original scan.
1) If I have an image (PNM) of size 1672x2333 then only about half of it is visible in the map editor. This makes it impossible to draw round. Is this expected? Should images be limited to some size before they can be importad as background? If so what is that size?
Try "Auto adjust" button in drawing area toolbar :) The scrollable are is defined by user, when you insert picture, it is not automatically adjusted (probably should be).
2) if keys used to change mode (F2, F1 etc) then menu top bar disappears.('normalize' window size fixes it). Can anyone else reproduce this
It is a bug somewhere deep in Tcl/Tk (it happens only from time to time on Linux, each time after longer compilation on Win32). I have no idea how to solve it (I have tried reduced it a lot, but it still happens). Regards, S.
participants (3)
-
Olly Betts -
Stacho Mudrak -
Wookey