qwtplot3d-interest

[qwtplot3d-interest] New features

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

The CVS contains some new stuff, maybe from interest for some users.
Look for 'Enrichment' in the online documentation (the mentioned
update of the API documentation isn't yet online). There is a new
example in examples/enrichments directory demonstrating the
techniques.

Pay also attention to:

http://qwtplot3d.sourceforge.net/web/navigation/issue.txt

because it affects some examples.


A new release for QwtPlot3D is planned around March 10th.


Micha
--

Re: [qwtplot3d-interest] labelling a surface plot

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

Sunday, February 22, 2004, 23:30:12, Jonathan Lees wrote:

JL> however now Id like to label a point on a surfaceplot with a label
JL> I cant seem to do this , tried quite a few different things

Not simple at this moment, but the next release (around March 10th, I
hope) will give you at hand a more general tool to add userdefined
objects.


Micha   
--

[qwtplot3d-interest] labelling a surface plot

[Jonathan L. <j....@ma...>]

Hi
Im quite new to qwt3d
but found it really quick and easy for the qt app im writing
however now Id like to label a point on a surfaceplot with a label
I cant seem to do this , tried quite a few different things

anyone know how

Cheers

Jon

Re: [qwtplot3d-interest] RPM spec file and g++ tweaks

[John C. <jcu...@us...>]

On Wednesday 07 January 2004 13:36, Micha Bieber wrote:
 >
 > I'm not an expert in spec files. If it works, I will include it in the
 > cvs and the distribution, why not ? Currently I use my linux (debian)
 > exclusively to see qwt3d compiling and whether the examples run -
 > mostly before releasing a new version.
 >

I used it to build the last release (0.2.0-beta) , with the changes I already 
mentioned and my own version of a doxygen file (since the doc/ directory was 
empty in the previous release), on Redhat 8.0, 9.0 and Enterprise 3.0. 

However, with the current CVS version, I am having problems with zlib files. 
To temporarily remedy the problem, I just removed zlib from CONFIG since most 
linux systems have it. Perhaps this should be a win32 only directive? FWIW, I 
know that libxml2 requires zlib for their Windows version. You may want to 
see how they handle the issue. I know that they have a version you can 
download if you only want to link against it.

 > JC> file: include/qwt3d_femreader.h. On lines 51 and 69, add "std::" to
 > ifstream. JC> I can send the diff output if you like, but the change is
 > simple.
 >
 > It's in the cvs now.
 >

I see that anonymous CVS is still behind the main servers. Ugh!

 > JC> have to doxygen files under the docs directory. I am not sure which
 > one to JC> use. Right now, the spec file uses the Doxyfile.doxygen file.
 >
 > The Developer.doxygen file turns on almost all possible doxygen
 > features (graphviz output, crosslinked source files etc.). Almost
 > useless and wastes a lot of time and space. I have it there only for
 > reasons of easeness regarding option switching.
 >

Sounds like I picked the right one then. It looks like I have to tweak the RPM 
spec file as a result. However, I'll wait until I get your CVS changes.

 > JC> Fourth, I am going to try compiling qwtplot3d on Windows with MSVC
 > .Net 2003 JC> shortly. I'll let you know how it goes. I believe that you
 > are using MSVC 6.
 >
 > These days I installed the VC .NET and it compiles fine :-)
 >

Sure does. However, I couldn't find the resulting library for a minute then I 
looked at the qwtplot3d.pro file and found it. It was just different from 
Linux (and from regular Qwt, FWIW) so it confused me. :-)

 > JC> Finally, I have encountered some errors when building with the latest
 > CVS JC> version:
 >
 > Fixed in cvs.
 >

Alas, maybe I'll get the update tomorrow.

 > Thanks,
 > Micha

You're welcome.

Re: [qwtplot3d-interest] Plot3D constructor does not assign a default value for mouse_input_enabled.

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

Friday, December 19, 2003, 16:13:00, Sta...@el... wrote:

SLec> but I think it would be preferable to assign mouse_input_enabled = true in
SLec> the constructor of Plot3D.

I think, that should be correct :-) - it it fixed in the CVS.

Thanks,
Micha   
-- 

[qwtplot3d-interest] Plot3D constructor does not assign a default value for mouse_input_enabled.

[<Sta...@el...>]

First of all - thanks to whoever is working on this package!

Second - I would like to pass along an experience I had building a test
case application with two SurfacePlots.  The mouse handler on the second
plot would only sometimes work.   Tracked problem down to fact that I don't
think the mouse_input_enabled member of Plot3D is ever assigned a default
value.  Callilng enableMouse(true) in my application solved the problem,
but I think it would be preferable to assign mouse_input_enabled = true in
the constructor of Plot3D.

Stacy.


*******************Internet Email Confidentiality Footer*******************
The contents of this e-mail message (including any attachments hereto) are
confidential to and are intended to be conveyed for the use of the
recipient to whom it is addressed only. If you receive this transmission in
error, please notify the sender of this immediately and delete the message
from your system. Any distribution, reproduction or use of this message by
someone other than recipient is not authorized and may be unlawful.

[qwtplot3d-interest] New release: QwtPlot3D 0.2.0 beta

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

A new version of QwtPlot3D is out:

New features:

    * Vector output (PS, EPS, PDF, TeX)
    * Shading
    * Color legends

Look at http://qwtplot3d.sourceforge.net/  for details.


Micha
--

Re: [qwtplot3d-interest] VS 7.1

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

Tuesday, September 9, 2003, 13:57:58, Wild, Michael (ESEC ZG) wrote:

WMEZ> Unfortunately it is not compiling under VS 7.1, because of iostream. There
WMEZ> is not iostream.h anymore!

You mean fstream.h, right ? It was legacy code. Fixed.

WMEZ> If I fix this and run an example I always get 
WMEZ> HEAP[colormodels.exe]: Invalid Address specified to RtlFreeHeap( 130000,
WMEZ> 1978b0 )
WMEZ> Unhandled exception at 0x77f97704 in colormodels.exe: User breakpoint.
WMEZ> at the shutdown of the sample.

Unfortunately, I've VC6 and gcc only to check. At the moment the error is unreproducible here.


I will release a new version of qwtplot3d within the next week or so. This will
hopefully fix some bugs too (and introduce new ones, of course:-)



Micha   
--

[qwtplot3d-interest] VS 7.1

[Wild, M. (E. ZG) <Mic...@es...>]

Hi

Great stuff
!
Unfortunately it is not compiling under VS 7.1, because of iostream. There
is not iostream.h anymore!
If I fix this and run an example I always get 
HEAP[colormodels.exe]: Invalid Address specified to RtlFreeHeap( 130000,
1978b0 )
Unhandled exception at 0x77f97704 in colormodels.exe: User breakpoint.
at the shutdown of the sample.

Tx

Mike



- NOTE - 

THE INFORMATION CONTAINED IN THIS MESSAGE MAY BE PRIVILEGED AND 
CONFIDENTIAL AND PROTECTED FROM DISCLOSURE.  IF THE READER OF THIS 
MESSAGE IS NOT THE INTENDED RECIPIENT, OR AN EMPLOYEE OR AGENT 
RESPONSIBLE FOR DELIVERING THIS MESSAGE TO THE INTENDED RECIPIENT, 
YOU ARE HEREBY NOTIFIED THAT ANY DISSEMINATION, DISTRIBUTION OR 
COPYING OF THIS COMMUNICATION IS STRICTLY PROHIBITED.  IF YOU HAVE 
RECEIVED THIS COMMUNICATION IN ERROR, PLEASE NOTIFY US IMMEDIATELY 
BY REPLYING TO THE MESSAGE AND DELETING IT FROM YOUR COMPUTER.  
THANK YOU - ESEC 

[qwtplot3d-interest] cvs issue

[Micha B. <bi...@tr...>]

The last sourceforge newsletter addresses the following topic:

-- snip ---
As you may have noticed, CVS is visibly having growing pains.  Due to
system load, we have had to move anonymous checkouts to our backup
server.  This has made the code of our 65,000 projects more
accessible.  However, since data is synchronized from the primary
CVS servers to the backup CVS servers at specific times during the day,
it has also caused up to a 24 hour delay in getting the
freshest code on the site.
...
The solution will be in place by the time I write you next month.
...
--- snap ---

Another issue is the currently yet broken project statistic (also
visibility of cvs checkins).
For the time being, please take this in account,

Micha   
--

RE: [qwtplot3d-interest] setResolution and Colours

[Dave C. <dm...@ce...>]

Hi Micha,

Thanks for the reply. Got the latest version from CVS this morning but still
had shading issues. I've now modified my source to address the issue,
basically just forced a color lookup for each point of the vertex in the
cell (previously only one color lookup per polygon).

I've pasted the changed function for you, changes are marked with a "//
CHANGED". I assume the non-grid dataview will also need to be changed...

Thanks - and keep up the good work. My plots look fantastic!

Cheers,

Dave.

void
SurfacePlot::updateGridData()
{
   int i, j;
   RGBA col1, col2, col3, col4; // CHANGED
   int cstep = resolution();
   int rstep = resolution();
   if (plotStyle() == FILLEDMESH || plotStyle() == WIREFRAME || plotStyle()
== HIDDENLINE)
   {
      glColor4d(meshColor().r, meshColor().g, meshColor().b, meshColor().a);

      for (i = 0; i < actualGridData_->columns() - cstep; i += cstep)
      {
         for (j = 0; j < actualGridData_->rows() - rstep; j += rstep)
         {
            glBegin(GL_LINE_LOOP);
            glVertex3dv(actualGridData_->vertices[i][j]);
            glVertex3dv(actualGridData_->vertices[i+cstep][j]);
            glVertex3dv(actualGridData_->vertices[i+cstep][j+rstep]);
            glVertex3dv(actualGridData_->vertices[i][j+rstep]);
            glEnd();
         }
      }
   }

   if (plotStyle() != WIREFRAME)
   {
      glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);
      glPolygonMode(GL_FRONT_AND_BACK, GL_QUADS);
      glEnable(GL_POLYGON_OFFSET_FILL);
      glPolygonOffset(polygonOffset(),1.0);

      bool hl = (plotStyle() == HIDDENLINE);
      col1 = col2 = col3 = col4 = backgroundRGBAColor(); // CHANGED

      glBegin(GL_QUADS);
      for (i = 0; i < actualGridData_->columns() - cstep; i += cstep)
      {
         for (j = 0; j < actualGridData_->rows() - rstep; j += rstep)
         {
            if(!hl)
            {
               // CHANGED (start)
               col1 = (*dataColor)(
                  actualGridData_->vertices[i][j][0],
                  actualGridData_->vertices[i][j][1],
                  actualGridData_->vertices[i][j][2]);
               col2 = (*dataColor)(
                  actualGridData_->vertices[i+cstep][j][0],
                  actualGridData_->vertices[i+cstep][j][1],
                  actualGridData_->vertices[i+cstep][j][2]);
               col3 = (*dataColor)(
                  actualGridData_->vertices[i+cstep][j+rstep][0],
                  actualGridData_->vertices[i+cstep][j+rstep][1],
                  actualGridData_->vertices[i+cstep][j+rstep][2]);
               col4 = (*dataColor)(
                  actualGridData_->vertices[i][j+rstep][0],
                  actualGridData_->vertices[i][j+rstep][1],
                  actualGridData_->vertices[i][j+rstep][2]);
               // CHANGED (stop)
            }
            glColor4d(col1.r, col1.g, col1.b, col1.a); // CHANGED
            glNormal3dv(actualGridData_->normals[i][j]);
            glVertex3dv(actualGridData_->vertices[i][j]);

            glColor4d(col2.r, col2.g, col2.b, col2.a); // CHANGED
            glNormal3dv(actualGridData_->normals[i+cstep][j]);
            glVertex3dv(actualGridData_->vertices[i+cstep][j]);

            glColor4d(col3.r, col3.g, col3.b, col3.a); // CHANGED
            glNormal3dv(actualGridData_->normals[i+cstep][j+rstep]);
            glVertex3dv(actualGridData_->vertices[i+cstep][j+rstep]);

            glColor4d(col4.r, col4.g, col4.b, col4.a); // CHANGED
            glNormal3dv(actualGridData_->normals[i][j+rstep]);
            glVertex3dv(actualGridData_->vertices[i][j+rstep]);
         }
      }
      glEnd();
      glDisable(GL_POLYGON_OFFSET_FILL);
   }
}

-----Original Message-----
From: Micha Bieber [mailto:kri...@us...]
Sent: Monday, 28 July 2003 6:33 AM
To: Dave Cooper
Cc: qwt...@li...
Subject: Re: [qwtplot3d-interest] setResolution and Colours


Friday, July 25, 2003, 06:58:04, Dave Cooper wrote:

DC> 1. setResolution is excellent for reducing the data. It would be nice if
it
DC> took a double and allowed for increasing the data set (ie. through
spline
DC> interpolation).

Interpolation doesn't increase the dataset per se. It smoothes
(mostly) but the user has to provide sampling points. But you are
right - a conceivable extension to the status quo lies in using of
splines on top of the existing datas. In fact, one reason for me in
writing the library originates from the wish to learn more about
OpenGL. The NURBS and evaluator implementation are still unknown
subjects to me. So, I think to delve into the problem :-)


DC> 2. Colour - I find that a polygon is always entirely filled with the
data
DC> colour of its lowest point. I'd really like to see the colour of the
polygon
DC> shaded over its surface. This is a real problem with small spikes in my
DC> plots.

Fixed (CVS). You should see real Gouraud shading now.


Micha
--

Re: [qwtplot3d-interest] setResolution and Colours

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

Friday, July 25, 2003, 06:58:04, Dave Cooper wrote:

DC> 1. setResolution is excellent for reducing the data. It would be nice if it
DC> took a double and allowed for increasing the data set (ie. through spline
DC> interpolation).

Interpolation doesn't increase the dataset per se. It smoothes
(mostly) but the user has to provide sampling points. But you are
right - a conceivable extension to the status quo lies in using of
splines on top of the existing datas. In fact, one reason for me in
writing the library originates from the wish to learn more about
OpenGL. The NURBS and evaluator implementation are still unknown
subjects to me. So, I think to delve into the problem :-)


DC> 2. Colour - I find that a polygon is always entirely filled with the data
DC> colour of its lowest point. I'd really like to see the colour of the polygon
DC> shaded over its surface. This is a real problem with small spikes in my
DC> plots.

Fixed (CVS). You should see real Gouraud shading now.


Micha   
--

[qwtplot3d-interest] setResolution and Colours

[Dave C. <dm...@ce...>]

Hi Peoples,

Firstly, this is a great tool, thanks for making it and letting it out into
the public domain.

I have a couple of questions/requests:

1. setResolution is excellent for reducing the data. It would be nice if it
took a double and allowed for increasing the data set (ie. through spline
interpolation). So a call of setResolution(0.1) would create 10x
interpolated points...

2. Colour - I find that a polygon is always entirely filled with the data
colour of its lowest point. I'd really like to see the colour of the polygon
shaded over its surface. This is a real problem with small spikes in my
plots.

Anyway, thanks again.

Dave Cooper
Software Engineer
CEA Technologies Pty Ltd
Phone: +61 (0)2 6213 0172
Email: dm...@ce...