You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(7) |
Feb
(3) |
Mar
(3) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
(2) |
2005 |
Jan
(7) |
Feb
(1) |
Mar
|
Apr
(9) |
May
(6) |
Jun
|
Jul
(15) |
Aug
(7) |
Sep
(18) |
Oct
(3) |
Nov
|
Dec
|
2006 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
(7) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(15) |
2007 |
Jan
(2) |
Feb
(5) |
Mar
(2) |
Apr
(6) |
May
(6) |
Jun
(1) |
Jul
(2) |
Aug
(27) |
Sep
(11) |
Oct
(6) |
Nov
(6) |
Dec
(8) |
2008 |
Jan
(4) |
Feb
(7) |
Mar
(37) |
Apr
(15) |
May
(10) |
Jun
(8) |
Jul
(29) |
Aug
(8) |
Sep
(13) |
Oct
(8) |
Nov
(25) |
Dec
(38) |
2009 |
Jan
(9) |
Feb
(12) |
Mar
(13) |
Apr
(19) |
May
(23) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Keith, T. <ke...@um...> - 2005-07-19 14:20:15
|
Thanks, Micha. =20 I should clarify that the last two items were not build errors but run = time errors caused by SGI's compiler ... =20 Todd |
From: Micha B. <kri...@us...> - 2005-07-18 19:56:36
|
Ok, some of them are in fact fixed, but not yet backported. I'll incorporate your little list during the next days in the 0.2 branch. Release than with Qt 4.0.1 Thanks, Micha -- |
From: Keith, T. <ke...@um...> - 2005-07-18 19:40:07
|
We use qwtplot3d on a variety of platforms, including Win32, Mac-OSX, = Irix, Solaris, AIX, HPUX, Linuxes, etc. ... We use the typical build = environments on these platforms and the corresponding default Qt release = compiler options. Please consider the following minor changes to avoid = build errors with qwtplot3d. Thanks! =20 qwt3d_helper.h ---------------------- Please change name of MAX() function. "MAX" function name gets = clobbered by preprocessor macro in at least one build environment, which = then produces compilation errors. =20 qwt3d_openglhelper.h ------------------------------- Please change "list" to "lst" (or something else) in SaveGlDeleteLists. = "list" variable name gets clobbered by preprocessor macro in at least = one build environment, which then produces compilation errors. =20 qwt3d_types.h --------------------- Please remove the unnecessary comma after the last enum item (FLOORDATA) = in the FLOORSTYLE enum. Causes compilation error in at least one build = environment. =20 qwt3d_colorlegend.cpp --------------------------------- Please change the "orient" to "ori" (or something else) in = ColorLegend::setOrientation(). "orient" variable name gets clobbered by = preprocessor macro in at least one build environment, which then = produces compilation errors. =20 qwt3d_types.cpp ------------------------ Change #include "float.h" to #include <float.h> since float.h is a = "system" header. =20 qwt3d_types.h --------------------- Triple and Parallelipiped classes need explicit copy constructors and = operator=3D() functions. Irix 6.5 when compiling with optimization. =20 qwt3d_plot.cpp ---------------------- void Plot3D::createCoordinateSystem() { calculateHull(); Triple beg =3D hull().minVertex; Triple end =3D hull().maxVertex; createCoordinateSystem(beg, end); } Irix 6.5 when compiling with optimization ... =20 |
From: Micha B. <kri...@us...> - 2005-07-11 22:18:17
|
A new version of QwtPlot3D is out: This is a refactorized version of qwtplot3d 0.2.4 beta. It provides transparent, native Qt3/4 support. Look at http://qwtplot3d.sourceforge.net/ for details. Enjoy ! Micha -- |
From: Micha B. <kri...@us...> - 2005-07-06 08:28:42
|
Hallo Todd and all, Since around 2 days, a Qt4_ready branch exists in CVS. This is a refactorized version of 0,2.4. No new functionality there, some fixed errors only. Base library and simple plot example compile and run, but I have still some problems with moc generated code for the other examples. Anyway, the code is Qt3 and Qt4 ready. I have still to set up my main example to test some things more intensely. Reason for this intermediate step is the current (not very amusing, to be honest) state of Qt4. This way I have a testbed for this Qt version. That said, after almost a year I have finally found some time to continue with qwt3d version 0.3 more evenly. Please understand that I resist to add very much regarding timelines at this moment (having done so in the past was no good idea). I'm a freelancer with varying contracting commitments and what is good for making my life, might turn out bad for writing Open Source :-( For the next months it seems still to be a rather healthy equilibrium, so expect to hear more (and more specific) from my side. Anyway, first step is the release of 0.2.5 (see above). Version numbers 0.2.6 - 0.2.9 are reserved for bug fixes in this branch. When 0.2.5 is out (should I say, I plan it for this week ;), main work is on 0.3 - also with a common code base for Qt3/4. The examples there still have no high priority for me for the present. One implication is, that testing for the main branch will be carried out for Qt3 primarily in the beginning. The Qt4 variant might go down to 'base library compilation only' temporarily. Please understand, that I need a stable Qt code base for feature testing. Micha -- |
From: Keith, T. <ke...@um...> - 2005-07-06 02:02:10
|
Hi Micha, =20 I know Qt4.0.0 was just released last week, but was just wondering how = things are going with qwtplot3d development. Any more hints you can = give us wrt new features, Qt4 compatiblity, timeframe, etc? I notice = that the cvs code is several months old and not reflective of current = development. Any chance you can make what you have available via cvs if = a stable release is still a ways off? We might be able to provide some = useful feedback and ease your burden ... =20 Thanks! |
From: Stefan G. <ge...@mb...> - 2005-05-12 08:22:27
|
Sorry, this was too easy :-) Thanks, Stefan On Tuesday 10 May 2005 10:18, Micha Bieber wrote: > Tuesday, May 10, 2005, 09:53:22, Stefan Gerlach wrote: > > Is it possible to add "void mouseDoubleClickEvent( QMouseEvent *e)" > > like in Qt? > > As usual in C++, inherit from SurfacePlot and implement the member. The > widget provides only a standard implementation (still configurable, but > not including any double click functionality - I had no idea about a > general useful implementation). > > Micha |
From: Micha B. <kri...@us...> - 2005-05-10 08:20:06
|
Tuesday, May 10, 2005, 09:53:22, Stefan Gerlach wrote: > Is it possible to add "void mouseDoubleClickEvent( QMouseEvent *e)" > like in Qt? As usual in C++, inherit from SurfacePlot and implement the member. The widget provides only a standard implementation (still configurable, but not including any double click functionality - I had no idea about a general useful implementation). Micha -- |
From: Stefan G. <ge...@mb...> - 2005-05-10 07:53:47
|
Hi, I like to use mouse double-click events in a 3d plot but couldn't find it. There are only these functions in Plot3D : void mousePressEvent (QMouseEvent *e) void mouseReleaseEvent (QMouseEvent *e) void mouseMoveEvent (QMouseEvent *e) Is it possible to add "void mouseDoubleClickEvent( QMouseEvent *e)" like in Qt? Thanks, Stefan Gerlach |
From: Micha B. <kri...@us...> - 2005-05-02 17:54:39
|
Monday, May 2, 2005, 18:56:01, Stefan Gerlach wrote: > Hi, > Is it possible to change the range of a surface plot without changing the data > every time? No (but see below). Some early version of qwtplot3d implemented a set of cutting planes. The problem was, that people tend to have very different requirements (more than one cutting plane per coordinate, non-planar cuttings etc.). For the very same reason (in principle wishable) incremental updates are not supported straightforwardly. As soon as data have been loaded, the model becomes more or less static. This has some advantages regarding OpenGL optimization (e.g. you couldn't do more or less real time movements also with relatively large data sets). So, I outsourced the responsibility to the user to prepare the data sets in a suiting way. Nevertheless I see your point and it is also one reason for not giving public access to the libraries internal data structures. This way I'm able to claim the ground for other implementations in the future (to mention - not for the next versions). Anyway, it might be possible to mimick the behavior of your problem with Enrichments in implementing the usage of OpenGL clipping planes in Enrichment::drawBegin() (setting the plane(s)) and Enrichment::drawEnd() (removing). It should be efficient, because it can utilize hardware clipping. I still had to give them a try in code to be sure, though. Micha -- |
From: Stefan G. <ge...@mb...> - 2005-05-02 16:56:52
|
Hi, Is it possible to change the range of a surface plot without changing the d= ata=20 every time? If i use "loadFromData(data,10,10,0,10,0,10)" i like to change the range to= =20 only see a plot with the data from x=3D0..5 and y=3D0..5, etc. I can change the limits of the x axis but this only changes the axis (not t= he=20 surface plot). Thanks in advance. best wishes, Stefan Gerlach |
From: Dave C. <dav...@ce...> - 2005-05-02 04:09:10
|
Ok, thanks Micha. I have successfully implemented your suggestion. Apologies for the poor subject line to the previous post. Gold star for all your work, and thanks for the help. Dave. -----Original Message----- From: qwt...@li... [mailto:qwt...@li...] On Behalf Of qwt...@li... Sent: Saturday, 30 April 2005 1:22 PM To: qwt...@li... Subject: qwtplot3d-interest digest, Vol 1 #34 - 2 msgs Send qwtplot3d-interest mailing list submissions to qwt...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/qwtplot3d-interest or, via email, send a message with subject or body 'help' to qwt...@li... You can reach the person managing the list at qwt...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of qwtplot3d-interest digest..." Today's Topics: 1. RE: qwtplot3d-interest digest, Vol 1 #33 - 3 msgs (Dave Cooper) 2. Re: qwtplot3d-interest digest, Vol 1 #33 - 3 msgs (Micha Bieber) --__--__-- Message: 1 From: "Dave Cooper" <dav...@ce...> To: <qwt...@li...> Subject: RE: qwtplot3d-interest digest, Vol 1 #33 - 3 msgs Date: Fri, 29 Apr 2005 14:33:16 +1000 Reply-To: qwt...@li... Hi Micha and friends, I have implemented a similar scaling function as described in the emails below (Scaling of surface plots). The scaling works great, however I am left with a problem regarding the axes' scales. If I make a dataset that is of size (x = 4, y = 1000, z = 1000), then using the setScale method and algorithm documented below I can (correctly) show a "cube" of data (even though the dataset is actually a rectangle). However the scales on the y and z axes are blown completely out of proportion (i.e. the lines out from the data to the string labels are exceptionally long). Can anyone point me in a direction to correctly scale the axes lines? If anyone wants a screen shot then let me know and I'll forward it (I don't have access to the internet to upload it to a web page here at work). I apologise if this has already been answered on a forum, I can't get the internet here. Thanks for your help, Dave Cooper (Canberra, Australia) -----Original Message----- From: qwt...@li... [mailto:qwt...@li...] On Behalf Of qwt...@li... Sent: Tuesday, 26 April 2005 1:31 PM To: qwt...@li... Subject: qwtplot3d-interest digest, Vol 1 #33 - 3 msgs Send qwtplot3d-interest mailing list submissions to qwt...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/qwtplot3d-interest or, via email, send a message with subject or body 'help' to qwt...@li... You can reach the person managing the list at qwt...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of qwtplot3d-interest digest..." Today's Topics: 1. Scaling of surface plots (Stefan Gerlach) 2. Re: Scaling of surface plots (Micha Bieber) 3. Re: Scaling of surface plots (Keith, Todd) -- __--__-- Message: 1 From: Stefan Gerlach <ge...@mb...> Organization: MBI To: qwt...@li... Subject: Scaling of surface plots Date: Mon, 25 Apr 2005 09:59:05 +0200 --Boundary-02=_VNKbCYSmBbjNgLj Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,=20 =20 I have some difficulties to scale surface plots to the correct size.=20 I'm using "loadFromData(data,cols,rows,0,cols,0,rows)"=20 to make a surface plot with different cols/rows combinations. Depending on rows/cols and zrange of the data the plot is very tiny or too= =20 big. I tried some combinations of setScale(1/rows,1/cols,1/zrange), etc.= =20 but had no luck to find the right combination.=20 =20 Is there a way to scale the surface plot to the correct size (depending on= =20 rows,cols,zrange)? How can i scale the plot to have all axes with the same= =20 size (aspect ratio) and always fit on the screen? =20 Thanks in advance. Stefan Gerlach --Boundary-02=_VNKbCYSmBbjNgLj Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBCbKNVa9g3y2xF0AARAldBAJ9m8J24aEeHZPt4dy0+F/m9lviltQCfUqDB 3KFINp0tJD2jrN4BTjnS/Pg= =IdWw -----END PGP SIGNATURE----- --Boundary-02=_VNKbCYSmBbjNgLj-- -- __--__-- Message: 2 Date: Mon, 25 Apr 2005 14:30:59 +0200 From: Micha Bieber <kri...@us...> To: qwt...@li... Subject: Re: Scaling of surface plots Stefan, please check the forum for an answer. Micha -- -- __--__-- Message: 3 Subject: Re: Scaling of surface plots Date: Mon, 25 Apr 2005 09:22:54 -0500 From: "Keith, Todd" <ke...@um...> To: <qwt...@li...> Reply-To: qwt...@li... Consider something like this ... ***** Let minX and maxX be the minimum and maximum value, respectively, of = your data along the x-Axis Let minY and maxY be the minimum and maximum value, respectively, of = your data along the y-Axis Let minZ and maxZ be the minimum and maximum value, respectively, of = your data along the z-Axis ***** double rangeX =3D fabs(maxX - minX); double rangeY =3D fabs(maxY - minY); double rangeZ =3D fabs(maxZ - minZ); double maxRange =3D rangeX; if (rangeY > maxRange) maxRange =3D rangeY; if (rangeZ > maxRange) maxRange =3D rangeZ; double scaleX =3D maxRange / rangeX; double scaleY =3D maxRange / rangeY; double scaleZ =3D maxRange / rangeZ; double maxScale =3D scaleX; if (scaleY > maxScale) maxScale =3D scaleY; if (scaleZ > maxScale) maxScale =3D scaleZ; setScale(scaleX, scaleY, scaleZ); -- __--__-- _______________________________________________ qwtplot3d-interest mailing list qwt...@li... https://lists.sourceforge.net/lists/listinfo/qwtplot3d-interest End of qwtplot3d-interest Digest --__--__-- Message: 2 Date: Fri, 29 Apr 2005 09:54:49 +0200 From: Micha Bieber <kri...@us...> To: qwt...@li... Subject: Re: qwtplot3d-interest digest, Vol 1 #33 - 3 msgs Reply-To: qwt...@li... Friday, April 29, 2005, 06:33:16, Dave Cooper wrote: > out of proportion (i.e. the lines out from the data to the string labels > are exceptionally long). Yes, it is a known issue. The currently implemented automatism handles these cases not yet satisfying. It's one of the small points for version 0.3.0. However, you should be able to resolve the problem manually by iterating through the axes: Adapt the implementation for CoordinateSystem::setTicLength() to your problem (axes is a public vector, so you have access to single axes in order to address them individually). void CoordinateSystem::setTicLength(double major, double minor) { for (unsigned i=0; i!=axes.size(); ++i) axes[i].setTicLength(major, minor); } There is also an enum AXES, supporting you in identifying the correct axes - check the axes example to see an example. HIH, Micha -- --__--__-- _______________________________________________ qwtplot3d-interest mailing list qwt...@li... https://lists.sourceforge.net/lists/listinfo/qwtplot3d-interest End of qwtplot3d-interest Digest |
From: Micha B. <kri...@us...> - 2005-04-29 07:56:33
|
Friday, April 29, 2005, 06:33:16, Dave Cooper wrote: > out of proportion (i.e. the lines out from the data to the string labels > are exceptionally long). Yes, it is a known issue. The currently implemented automatism handles these cases not yet satisfying. It's one of the small points for version 0.3.0. However, you should be able to resolve the problem manually by iterating through the axes: Adapt the implementation for CoordinateSystem::setTicLength() to your problem (axes is a public vector, so you have access to single axes in order to address them individually). void CoordinateSystem::setTicLength(double major, double minor) { for (unsigned i=0; i!=axes.size(); ++i) axes[i].setTicLength(major, minor); } There is also an enum AXES, supporting you in identifying the correct axes - check the axes example to see an example. HIH, Micha -- |
From: Dave C. <dav...@ce...> - 2005-04-29 04:34:44
|
Hi Micha and friends, I have implemented a similar scaling function as described in the emails below (Scaling of surface plots). The scaling works great, however I am left with a problem regarding the axes' scales. If I make a dataset that is of size (x = 4, y = 1000, z = 1000), then using the setScale method and algorithm documented below I can (correctly) show a "cube" of data (even though the dataset is actually a rectangle). However the scales on the y and z axes are blown completely out of proportion (i.e. the lines out from the data to the string labels are exceptionally long). Can anyone point me in a direction to correctly scale the axes lines? If anyone wants a screen shot then let me know and I'll forward it (I don't have access to the internet to upload it to a web page here at work). I apologise if this has already been answered on a forum, I can't get the internet here. Thanks for your help, Dave Cooper (Canberra, Australia) -----Original Message----- From: qwt...@li... [mailto:qwt...@li...] On Behalf Of qwt...@li... Sent: Tuesday, 26 April 2005 1:31 PM To: qwt...@li... Subject: qwtplot3d-interest digest, Vol 1 #33 - 3 msgs Send qwtplot3d-interest mailing list submissions to qwt...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/qwtplot3d-interest or, via email, send a message with subject or body 'help' to qwt...@li... You can reach the person managing the list at qwt...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of qwtplot3d-interest digest..." Today's Topics: 1. Scaling of surface plots (Stefan Gerlach) 2. Re: Scaling of surface plots (Micha Bieber) 3. Re: Scaling of surface plots (Keith, Todd) --__--__-- Message: 1 From: Stefan Gerlach <ge...@mb...> Organization: MBI To: qwt...@li... Subject: Scaling of surface plots Date: Mon, 25 Apr 2005 09:59:05 +0200 --Boundary-02=_VNKbCYSmBbjNgLj Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,=20 =20 I have some difficulties to scale surface plots to the correct size.=20 I'm using "loadFromData(data,cols,rows,0,cols,0,rows)"=20 to make a surface plot with different cols/rows combinations. Depending on rows/cols and zrange of the data the plot is very tiny or too= =20 big. I tried some combinations of setScale(1/rows,1/cols,1/zrange), etc.= =20 but had no luck to find the right combination.=20 =20 Is there a way to scale the surface plot to the correct size (depending on= =20 rows,cols,zrange)? How can i scale the plot to have all axes with the same= =20 size (aspect ratio) and always fit on the screen? =20 Thanks in advance. Stefan Gerlach --Boundary-02=_VNKbCYSmBbjNgLj Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBCbKNVa9g3y2xF0AARAldBAJ9m8J24aEeHZPt4dy0+F/m9lviltQCfUqDB 3KFINp0tJD2jrN4BTjnS/Pg= =IdWw -----END PGP SIGNATURE----- --Boundary-02=_VNKbCYSmBbjNgLj-- --__--__-- Message: 2 Date: Mon, 25 Apr 2005 14:30:59 +0200 From: Micha Bieber <kri...@us...> To: qwt...@li... Subject: Re: Scaling of surface plots Stefan, please check the forum for an answer. Micha -- --__--__-- Message: 3 Subject: Re: Scaling of surface plots Date: Mon, 25 Apr 2005 09:22:54 -0500 From: "Keith, Todd" <ke...@um...> To: <qwt...@li...> Reply-To: qwt...@li... Consider something like this ... ***** Let minX and maxX be the minimum and maximum value, respectively, of = your data along the x-Axis Let minY and maxY be the minimum and maximum value, respectively, of = your data along the y-Axis Let minZ and maxZ be the minimum and maximum value, respectively, of = your data along the z-Axis ***** double rangeX =3D fabs(maxX - minX); double rangeY =3D fabs(maxY - minY); double rangeZ =3D fabs(maxZ - minZ); double maxRange =3D rangeX; if (rangeY > maxRange) maxRange =3D rangeY; if (rangeZ > maxRange) maxRange =3D rangeZ; double scaleX =3D maxRange / rangeX; double scaleY =3D maxRange / rangeY; double scaleZ =3D maxRange / rangeZ; double maxScale =3D scaleX; if (scaleY > maxScale) maxScale =3D scaleY; if (scaleZ > maxScale) maxScale =3D scaleZ; setScale(scaleX, scaleY, scaleZ); --__--__-- _______________________________________________ qwtplot3d-interest mailing list qwt...@li... https://lists.sourceforge.net/lists/listinfo/qwtplot3d-interest End of qwtplot3d-interest Digest |
From: Keith, T. <ke...@um...> - 2005-04-25 14:23:26
|
Consider something like this ... ***** Let minX and maxX be the minimum and maximum value, respectively, of = your data along the x-Axis Let minY and maxY be the minimum and maximum value, respectively, of = your data along the y-Axis Let minZ and maxZ be the minimum and maximum value, respectively, of = your data along the z-Axis ***** double rangeX =3D fabs(maxX - minX); double rangeY =3D fabs(maxY - minY); double rangeZ =3D fabs(maxZ - minZ); double maxRange =3D rangeX; if (rangeY > maxRange) maxRange =3D rangeY; if (rangeZ > maxRange) maxRange =3D rangeZ; double scaleX =3D maxRange / rangeX; double scaleY =3D maxRange / rangeY; double scaleZ =3D maxRange / rangeZ; double maxScale =3D scaleX; if (scaleY > maxScale) maxScale =3D scaleY; if (scaleZ > maxScale) maxScale =3D scaleZ; setScale(scaleX, scaleY, scaleZ); |
From: Micha B. <kri...@us...> - 2005-04-25 12:33:01
|
Stefan, please check the forum for an answer. Micha -- |
From: Stefan G. <ge...@mb...> - 2005-04-25 07:59:33
|
Hi,=20 =20 I have some difficulties to scale surface plots to the correct size.=20 I'm using "loadFromData(data,cols,rows,0,cols,0,rows)"=20 to make a surface plot with different cols/rows combinations. Depending on rows/cols and zrange of the data the plot is very tiny or too= =20 big. I tried some combinations of setScale(1/rows,1/cols,1/zrange), etc.= =20 but had no luck to find the right combination.=20 =20 Is there a way to scale the surface plot to the correct size (depending on= =20 rows,cols,zrange)? How can i scale the plot to have all axes with the same= =20 size (aspect ratio) and always fit on the screen? =20 Thanks in advance. Stefan Gerlach |
From: Micha B. <kri...@us...> - 2005-04-18 19:49:23
|
Monday, April 18, 2005, 20:54:40, Keith, Todd wrote: > Do you plan on the next release of qwtplot3d continuing to support the Qt3 series? At any rate. It's still my workhorse - in fact, I make a considerable amount of my money by utilizing Qt3, so don't be afraid that I stop the support of a tested system. I think, Trolltech has to spend some time yet in stabilizing Qt4 after releasing it. Also when preparing the sources for Qt4 compatibility, a stable Qt3 variant is still more important to me. Micha -- |
From: Keith, T. <ke...@um...> - 2005-04-18 18:54:52
|
Micha, =20 Do you plan on the next release of qwtplot3d continuing to support the = Qt3 series? =20 Todd |
From: Micha B. <kri...@us...> - 2005-04-18 18:29:58
|
Monday, April 18, 2005, 19:04:22, Stefan Gerlach wrote: > Hi, > I'm a little bit confused with the versions of qwtplot3d. > The website http://qwtplot3d.sourceforge.net/ says that version 0.2.4 (11 June > 2004) is the latest ("Next release planned : 01/2005") and the mailing list > states that "qwt3d 0.3.0 beta comes out in January '05." .The website seems a > little bit outdated here. > Did you plan to release a stable version of 0.2.4 or just continue with the > next beta version (0.3.0)? > I'm using qwtplot3d a lot in LabPlot and like to improve some things. I may > send some bug reports or wishes if desired. > Thanks so far. > best wishes, > Stefan Gerlach Your confusion is completely satisfied. I planned a release in January '05 and I made this public - a thing you should never do premature :-) In fact 0.2.4. beta is the current release. The next one will be 0.3.0. The release date depends on 1) Qt4 release 2) free time slots for implementing some of the gathered feature requests and my own wishes. Beside your bad experience with my last promise - I can say more or less definitely, what will come in the new version. I mentioned Qt4, so compatibility at least for the core library is an issue - the examples step by step, depending on what porting tools Trolltech will deliver. Next important is a new data model. Talking about the API it will manifest itself in even more general loadFromData versions. If you are common with cell complexes in a mathematician's sense, this will be the final underlying data structure. It includes all the yet provided variants + graphs (node+edges) + nodes+edges+faces and finally - not yet in the upcoming version - nodes+edges+faces+voxels are in my mind. A nice property here is, that this model supports also disconnected data sets, so e.g plots with more than one surfaces (multiplots) are automatically included. All this will also result in new specialized widget classes (the current one in the works is a graph plot) 3th thing is more interactivity, that means the possibility to implement more specific mouse handling (element based). To make it good (quick but also flexible enough) it has been turned out to be no small design challenge. The last issue are some other movement modii (arcball etc.). But this will very probably not yet come with the next version. Hope this can clarify things a bit. Regarding your friendly offered bug reports - I'm always interested in these things, also feature requests etc., so don't hesitate to contact me. Micha -- |
From: Stefan G. <ge...@mb...> - 2005-04-18 17:05:32
|
Hi, I'm a little bit confused with the versions of qwtplot3d. The website http://qwtplot3d.sourceforge.net/ says that version 0.2.4 (11 J= une=20 2004) is the latest ("Next release planned : 01/2005") and the mailing list= =20 states that "qwt3d 0.3.0 beta comes out in January '05." .The website seems= a=20 little bit outdated here. Did you plan to release a stable version of 0.2.4 or just continue with the= =20 next beta version (0.3.0)? I'm using qwtplot3d a lot in LabPlot and like to improve some things. I may= =20 send some bug reports or wishes if desired. Thanks so far. best wishes, Stefan Gerlach |
From: Gerard V. <ger...@gr...> - 2005-02-27 15:10:03
|
What is PyQwt3D? - it is a set of Python bindings for the QwtPlot3D C++ class library which extends the Qt framework with widgets for 3D data visualization. PyQwt3D inherits the snappy feel from QwtPlot3D. The examples at http://pyqwt.sourceforge.net/pyqwt3d-examples.html show how easy it is to make a 3D plot and how to save a 3D plot to an image or an (E)PS/PDF file. - it requires and extends PyQt, a set of Python bindings for Qt. - it supports the use of PyQt, Qt, Qwt, the Numerical Python extensions (either Numeric, or numarray or both) and optionally SciPy in a GUI Python application or in an interactive Python session. - it runs on POSIX, MacOS/X and Windows platforms (practically any platform supported by Qt and Python). The home page of PyQwt3D is http://pyqwt.sourceforge.net. PyQwt3D-0.1 supports: 1. Python-2.4 downto -2.3. 2. PyQt-3.14 downto -3.12. 3. SIP-4.2 downto -4.0, but SIP-4.2 is recommended. PyQwt3D does *not* support SIP-3.x (I tried, but failed). 4. Qt-3.3.4 downto -2.3.0. 5. QwtPlot3D-0.2.4-beta. Have fun -- Gerard Vermeulen |
From: Micha B. <kri...@us...> - 2005-01-05 23:14:37
|
@all Hope, I can clarify licensing issues a bit. I made the following change to Qwt3D's license: http://tinyurl.com/6om7m This constitutes essentially the zlib license. LGPL remains an alternative up to the release of the next version of Qwt3D. An alternative - feel free to use the new license for the recent and older versions of the library. Micha -- |
From: Micha B. <kri...@us...> - 2005-01-05 23:02:04
|
@all Hope, I can clarify licensing issues a bit. I made the following change to Qwt3D's license: http://tinyurl.com/6om7m This constitutes essentially the zlib license. LGPL remains an alternative up to the release of the next version of Qwt3D. An alternative - feel free to use the new license for the recent and older versions of the library. Micha -- |
From: John C. <jcu...@us...> - 2005-01-04 17:01:27
|
Micha, I noticed when using the custom color maps, that the legend does not get updated when changing colors. I believe this short patch solves this problem: cvs diff qwt3d_plot.cpp Index: qwt3d_plot.cpp =================================================================== RCS file: /cvsroot/qwtplot3d/qwtplot3d/src/qwt3d_plot.cpp,v retrieving revision 1.18 diff -u -3 -p -r1.18 qwt3d_plot.cpp --- qwt3d_plot.cpp 23 Oct 2004 14:09:46 -0000 1.18 +++ qwt3d_plot.cpp 4 Jan 2005 16:29:11 -0000 @@ -235,6 +235,8 @@ void Plot3D::setDataColor( Color* col ) datacolor_p->destroy(); datacolor_p = col; + if ( displaylegend_ ) + datacolor_p->createVector(legend_.colors); } /*! Try the Mesh2 example when changing to a different data set with a custom map. HTH John Cummings |