On 17/01/08 23:28, Christoph Praxmarer wrote:
Hi Moritz,
Great job on v.class and d.thematic.area!
about d.thematic.area:
I can't set bwidth to zero. My programming skills are very bad, and I haven't done any C anyway so I wasn't able to find the reason for this.
What are you trying to achieve: no borders ? If that's it, try bcolor=none. bwidth=0 is not different from bwidth=1 in the x-monitors or the PNG monitor, but you can see the difference in the PS monitor.
Moritz
Moritz Lennert wrote:
bwidth=0 is not different from bwidth=1 in the x-monitors
or the PNG monitor,
well, actually it is slightly. width=0 is a little cleaner.
see previous discussions about default render mode for d.vect.
this reminds me that we still need an answer for that question before
releasing 6.3.0.
but you can see the difference in the PS monitor.
Hamish
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Hamish wrote:
see previous discussions about default render mode for d.vect.
this reminds me that we still need an answer for that question before
releasing 6.3.0.
Realistically, I think that it needs to be "c". "g" doesn't work with
vector-based drivers. The others all risk exceeding the 16-bit range
of XDRIVER, and modifying XDRIVER to perform its own clipping is too
radical a change at this stage.
That still leaves the problem with clipping polylines (segments
introduced by clipping are stroked), which I'll look into.
--
Glynn Clements <glynn@gclements.plus.com>
Glynn Clements wrote:
> see previous discussions about default render mode for d.vect.
> this reminds me that we still need an answer for that question before
> releasing 6.3.0.Realistically, I think that it needs to be "c". "g" doesn't work with
vector-based drivers. The others all risk exceeding the 16-bit range
of XDRIVER, and modifying XDRIVER to perform its own clipping is too
radical a change at this stage.That still leaves the problem with clipping polylines (segments
introduced by clipping are stroked), which I'll look into.
My mistake. Clipped polylines are broken into individual line
segments. It's culled polylines where the problem arises, but that
isn't really an issue if the default is "c".
--
Glynn Clements <glynn@gclements.plus.com>