Extended version of QwtPlot3D 0.3.1 is available to download at Sintegrial Technologies web site: http://sintegrial.com/qwtplot
Short change log:
- common performance optimizations (up to 50%)
- added VolumePlot implementation
- added volumeplot example
- support for Qt 4.8 and Qt 5.2
Please note:
it is a fork based on the official version 0.3.0 build 259.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be nice if this version would be clearly distinguishable from the "official" version, i.e. something like a QWT3D_*_VERSION change in include/qwt3d_global.h, or something else you can scan for with cmake/autotools/preprocessor. You can't make sure that a scan for version 0.3.0 provides a VolumePlot.
I don't know if changing the version, e.g. the patchlevel, is the right approach to this, but I guess something like that would be comfortable.
EDIT: Oh, and VOlumePlot is a nice thing. Finally one can plot a set of triples.
Last edit: Comphuter 2014-08-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great update. Thanks for posting this updated version and for creating the new examples. I did note 3 problems with this version during compilation though. Under Linux, you'll have problems compiling/linking due to missing switches in the makefiles and openGL/GLU. The example makefiles need to be updated to add -lGLU
Under VS2008, most of the examples in the VS solutionfile have paths to qtmain.lib hard-coded to look for this particular lib at c:\qt_4.8.5\lib. This should be changed to $(QTDIR)\lib instead, to avoid dependence on QT version 4.8.5
Under VS2008, the release versions of the library and examples compile just fine but refuse to run. The debug versions run without any issues. Not sure why, so I'll just stick to the debug versions until someone smarter than me figures it out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used Ubuntu 12.10 to compile the Linux versions. I don't get any error messages at all when I try to run the release versions of the examples under Windows, even when I invoke them by the command line. Yes, the %QTDIR%\bin directory is defined in my Windows PATH.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, I'll just continue to use the debug binaries for now. It may be something specific to my Windows 7 x64 development system but I haven't had a chance to see if it occurs on my other systems yet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Sintegrial
Thank you for the update. I have made a few changes to the code and would like your opinion on that:
a.) Made it CMake compatible so that we can use CMake to build the library/examples
b.) Separate libraries for debug and release builds
I was wondering if you have any example for creating a Legend? If so, can you please share it with the community. Better still, a legend in the Volumeplot example would be ideal.
How do I share my changes? Do you want to create a github page for that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would be great if you could put your source on GitHub so the community could add in patches. I have some that are specific for Mac that I would like to commit.
Tahnks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally got around to converting QWTPLOT3D to an x64 build under QT4.8.7 and VisualStudio 2013. Easiest method is to use the x64 compiler command prompt and run qmake on the qwtplot3d.pro file and then executing nmake to build the link library. After building the link library, copy it to each example folder, run qmake on each respective example's .pro file and then run nmake in each example folder. All the examples compiled and worked great using this method. Using QTCreator and opening the .pro files was a fail as was opening and converting the VS2008 solution files. There's probably an easier way to convert the library to x64 but this worked for me and wasn't too tedious.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
currently integration of GL2PS is out of the scope because we are thinking about switching to another 3d plotting technology (mostly due to performance reasons). The repository is however open for contributions so you could make the changes you wish and put them into the repo.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, that's probably a good move as generating PDF output using GL2PS can eat up an enormous amount of memory, file space AND time. On large data sets I've seen PDF generation take hours, tie up gigabytes of RAM and result in files well over 200MB in size. Postscript generation is much faster but still results in large files. Large file sizes are inherent to the LIDAR point clouds that I'm playing around with but when it takes 12 hours to generate a PDF it's time to look for other solutions. I'm an intermediate level C/C++ programmer so I probably don't have the skills to to add a 3D or 2D printing solution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Extended version of QwtPlot3D 0.3.1 is available to download at Sintegrial Technologies web site: http://sintegrial.com/qwtplot
Short change log:
- common performance optimizations (up to 50%)
- added VolumePlot implementation
- added volumeplot example
- support for Qt 4.8 and Qt 5.2
Please note:
it is a fork based on the official version 0.3.0 build 259.
It would be nice if this version would be clearly distinguishable from the "official" version, i.e. something like a QWT3D_*_VERSION change in include/qwt3d_global.h, or something else you can scan for with cmake/autotools/preprocessor. You can't make sure that a scan for version 0.3.0 provides a VolumePlot.
I don't know if changing the version, e.g. the patchlevel, is the right approach to this, but I guess something like that would be comfortable.
EDIT: Oh, and VOlumePlot is a nice thing. Finally one can plot a set of triples.
Last edit: Comphuter 2014-08-29
http://sintegrial.com/qwtplot link is not active, please suggest new one.
Great update. Thanks for posting this updated version and for creating the new examples. I did note 3 problems with this version during compilation though. Under Linux, you'll have problems compiling/linking due to missing switches in the makefiles and openGL/GLU. The example makefiles need to be updated to add -lGLU
Under VS2008, most of the examples in the VS solutionfile have paths to qtmain.lib hard-coded to look for this particular lib at c:\qt_4.8.5\lib. This should be changed to $(QTDIR)\lib instead, to avoid dependence on QT version 4.8.5
Under VS2008, the release versions of the library and examples compile just fine but refuse to run. The debug versions run without any issues. Not sure why, so I'll just stick to the debug versions until someone smarter than me figures it out.
Hi Steve,
thank you for the feedback!
I used Ubuntu 12.10 to compile the Linux versions. I don't get any error messages at all when I try to run the release versions of the examples under Windows, even when I invoke them by the command line. Yes, the %QTDIR%\bin directory is defined in my Windows PATH.
Hi Steve,
unfortunately we could not reproduce the issue :(
Have you already figured it out? Or it is still active?
No, I'll just continue to use the debug binaries for now. It may be something specific to my Windows 7 x64 development system but I haven't had a chance to see if it occurs on my other systems yet.
Turns out that somehow the QT debug DLLs were copied into my windows system directory. I removed them and now the problem is gone.
Hi Everybody,
a new bugfix update is available (0.3.1 build 322)
http://sintegrial.com/qwtplot/pages/en/index.php
Hello Sintegrial
Thank you for the update. I have made a few changes to the code and would like your opinion on that:
a.) Made it CMake compatible so that we can use CMake to build the library/examples
b.) Separate libraries for debug and release builds
I was wondering if you have any example for creating a Legend? If so, can you please share it with the community. Better still, a legend in the Volumeplot example would be ideal.
How do I share my changes? Do you want to create a github page for that?
Hello Sintegrial,
Would be great if you could put your source on GitHub so the community could add in patches. I have some that are specific for Mac that I would like to commit.
Tahnks
Thanks for the update. Has anyone tried compiling this under VC2008 as a 64-bit project?
I finally got around to converting QWTPLOT3D to an x64 build under QT4.8.7 and VisualStudio 2013. Easiest method is to use the x64 compiler command prompt and run qmake on the qwtplot3d.pro file and then executing nmake to build the link library. After building the link library, copy it to each example folder, run qmake on each respective example's .pro file and then run nmake in each example folder. All the examples compiled and worked great using this method. Using QTCreator and opening the .pro files was a fail as was opening and converting the VS2008 solution files. There's probably an easier way to convert the library to x64 but this worked for me and wasn't too tedious.
Hi Everybody,
GitHub repo is now here: https://github.com/sintegrial/qwtplot3d
Will you be reintegrating GL2PS back into your fork? I miss being able to generate output files.
Hi Steve,
currently integration of GL2PS is out of the scope because we are thinking about switching to another 3d plotting technology (mostly due to performance reasons). The repository is however open for contributions so you could make the changes you wish and put them into the repo.
Yeah, that's probably a good move as generating PDF output using GL2PS can eat up an enormous amount of memory, file space AND time. On large data sets I've seen PDF generation take hours, tie up gigabytes of RAM and result in files well over 200MB in size. Postscript generation is much faster but still results in large files. Large file sizes are inherent to the LIDAR point clouds that I'm playing around with but when it takes 12 hours to generate a PDF it's time to look for other solutions. I'm an intermediate level C/C++ programmer so I probably don't have the skills to to add a 3D or 2D printing solution.
add deb (and possibly others) package plz