Re: Color Legend issues

[Micha B. <kri...@us...>]

Monday, October 17, 2005, 11:22:52, ion vasilief wrote:

> Hello Micha,

> I would like to change the fonts of the numbers
> displayed by the color legend, but the API of this
> class doesn't provide a method to do this. It think it
> would be really usefull to provide a way to access the
> axis member of the legend.

> Another issue with the color legend is that it is not
> automatically updated when you change the colors or
> the transparency of the data, evan if one calls
> updateData() or updateGL(). The only way I could
> achieve this was to hide and then reshow the legend,
> but this results into disturbing flickering.

Ok, I could grant axis access like for the axes in coordinate system.
In mesh2 I adapt the colors simply by means of Plot3D::showColorLegend(bool).
This function also calls updateGL(). Could you check, if the flickering
remains ? If so, a compilable piece of relevant code would be a nice
thing (tm) ..

> I also have a question regarding the axis labels. I
> would like to display the label for the Z axes
> vertically and not horrizontally as it is displayed by
> default. How can I do this?

I think it's not easily doable for now without a hack. Maybe I'll
introduce in the future 3D labels in the sense you can find in some
other libraries/applications. That means, that labels are not longer
restricted to be projections on the background but can lie in x-y, y-z
or x-z plane (e.g.). I have this feature still not scheduled yet -
meaning it has low priority for the moment. If it comes to
implementation I'll take in account more degrees of freedom for
positions in the sense you requested.

> And finally, is it possible to implement multiple
> plots? I saw that there's a MultiPlot class available,
> but I'm not sure how to use this.

The final solution is in the pipeline. Nevertheless it should be
possible to emulate this feature for the current version by utilizing
SurfacePlot::loadFromData(Qwt3D::TripleField const& data,
Qwt3D::CellField const& poly).
If you provide the right CellField for the function you can produce
non-connected components - essentially a multiplot of surfaces. This is
not perfect (of course there are reasons for a specific implementations)
but should work.

Micha  
--