Hello, May I ask for a new feature ? On extend maps, can you add to the join section the break command. On plan maps, we can specifie for different scraps the upper and lower putting “break” between the join commands. It’s refused for extended maps. This will allow to see easily if a gallery is behind or bellow an other. May be it’s not too difficulte for you ? The best thing will be to be able to position manually an extended scrap on the map (relatively to an other), as we can do it for none scraps. So we could avoid this problems. Thanks. Gilbert
Gilbert Fernandes (mailinglist) wrote:
On extend maps, can you add to the join section the break command. On plan maps, we can specifie for different scraps the upper and lower putting “break” between the join commands. It’s refused for extended maps.
??? I am sorry, I do not understand. Normally, break is inserted in the map and when this map is selected for output, these breaks are not ignored. Could you please send me some (minimal) sample, where this problem occurs - i.e. plan where it works and xelev, where it is refused.
The best thing will be to be able to position manually an extended scrap on the map (relatively to an other), as we can do it for none scraps. So we could avoid this problems.
It can be done using maps, at least I think. Example: Add to the source code: map my_map scrap1 break scrap2 endmap And to the thconfig: select my_map export map -proj extended ... and it should work. If there is some problem - just send me some small example and I can show you how it works (or may be there is some bug and it does not work.) Or may be I do not understand your problem? Regards, S.
Gilbert wrote:
The best thing will be to be able to position manually an extended scrap on the map (relatively to an other), as we can do it for none scraps.
Hello Stacho, I think that what Gilbert mention is something we already discuss once with you, namely be able to position several pieces of extended elevations on the same map, with translation lateral and vertical, specified by the user, between them. This is what we usualy do by hand for mostly all non-trivial extended elevations... Eric.
On 27.7.2007, at 10:08, Eric Madelaine wrote:
I think that what Gilbert mention is something we already discuss once with you, namely be able to position several pieces of extended elevations on the same map, with translation lateral and vertical, specified by the user, between them. This is what we usualy do by hand for mostly all non-trivial extended elevations...
But this is possible. Stacho did it - see examples: http://therion.speleo.sk/samples.doc/index.html Martin
Martin Sluka wrote:
On 27.7.2007, at 10:08, Eric Madelaine wrote:
I think that what Gilbert mention is something we already discuss once with you, namely be able to position several pieces of extended elevations on the same map, with translation lateral and vertical, specified by the user, between them. This is what we usualy do by hand for mostly all non-trivial extended elevations...
But this is possible. Stacho did it - see examples:
Looks good... I will have to invest more time in following these new things...! Eric.
Hello, I will study your special documentation. When I do my test, (adding break command on map block) may be I badly write the "break", I'm not sure now. Because Therion say it didn't know this command. I will try again. After my holidays, Thanks, Gilbert Stacho Mudrak a écrit :
Gilbert Fernandes (mailinglist) wrote:
On extend maps, can you add to the join section the break command. On plan maps, we can specifie for different scraps the upper and lower putting “break” between the join commands. It’s refused for extended maps.
??? I am sorry, I do not understand. Normally, break is inserted in the map and when this map is selected for output, these breaks are not ignored. Could you please send me some (minimal) sample, where this problem occurs - i.e. plan where it works and xelev, where it is refused.
The best thing will be to be able to position manually an extended scrap on the map (relatively to an other), as we can do it for none scraps. So we could avoid this problems.
It can be done using maps, at least I think.
Example:
Add to the source code:
map my_map scrap1 break scrap2 endmap
And to the thconfig:
select my_map export map -proj extended
... and it should work. If there is some problem - just send me some small example and I can show you how it works (or may be there is some bug and it does not work.) Or may be I do not understand your problem?
Regards, S.
_______________________________________________ Therion mailing list Therion@speleo.sk http://www.speleo.sk/mailman/listinfo/therion
participants (4)
-
Eric Madelaine -
Gilbert Fernandes (mailinglist) -
Martin Sluka -
Stacho Mudrak