qwt 6.0.2 on osx

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

_______________________________________________
qwt-interest mailing list
qwt-interest <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qwt-interest

Aw: qwt 6.0.2 on osx

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

_______________________________________________
qwt-interest mailing list
qwt-interest <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qwt-interest

Re: Implement selection of multiple points on QwtPlotCurve

Sent from BlackBerry® on Airtel

-----Original Message-----
From: Sergey <popov <at> ilt.kharkov.ua>
Date: Tue, 31 Jan 2012 13:27:57 
To: <qwt-interest <at> lists.sourceforge.net>
Reply-To: List for both Qwt users and developers
	<qwt-interest <at> lists.sourceforge.net>
Subject: Re: Implement selection of multiple points on QwtPlotCurve

Thank you, Hendirk!

Just before getting your letter I finished new version of
implementation based completely on the QwtPicker without re-coding
internals. Here is code from my Plot():

//Picker with click point machine to provide point selection
    QwtPicker *picker=new QwtPicker(canvas());
    picker->setStateMachine(new QwtPickerClickPointMachine);
    connect(picker,SIGNAL(appended(QPoint)),SLOT(selectPoint(QPoint)));

//Picker for selecting range of points (Shift+LMB)
    QwtPicker *rangePicker=new QwtPicker(canvas());
    rangePicker->setStateMachine(new QwtPickerClickPointMachine);
    rangePicker->setMousePattern(0,Qt::LeftButton,Qt::SHIFT);
    connect(rangePicker,SIGNAL(appended(QPoint)),SLOT(selectRange(QPoint)));

//Picker for append/remove additional points to/from selection (Ctrl+LMB)
    QwtPicker *appendPicker=new QwtPicker(canvas());
    appendPicker->setStateMachine(new QwtPickerClickPointMachine);
    appendPicker->setMousePattern(0,Qt::LeftButton,Qt::CTRL);
    connect(appendPicker,SIGNAL(appended(QPoint)),SLOT(appendPoint(QPoint)));

I already had selectPoint, selectRange and appendPoint slots that works
as I want them to work.
Thanks you for your help! I would expand description of QwtPicker class
and send it as patch to Uwe to make documentation better.

Kind regards,
Sergey P.

В Tue, 31 Jan 2012 12:17:37 +0100
Hendrik Vennekate <HVennekate <at> gmx.de> пишет:

> You are very welcome and thanks for considering my suggestion.
> Unfortunately, it is true that the Qwt documentation is sometimes a
> bit meager, but considering the size of the library and the fact that
> Uwe Rathman seems to be the only maintainer, I'd say it's still
> pretty good.  In the case of the picker it's -- of course -- even
> worse as its "only" an example and not part of the core library
> (although there is a picker in the core library as well...).
> Sometimes it really helps to look into the code itself instead of the
> documentation ;)
> 
> So you want all the comfort, you can get, huh?  That's what I do in
> my program (with a less sophisticated point picking), so it should
> work.  My guess is that your issue is not to be resolved within Qwt
> but QT itself.  Take the documentation of void
> QObject::installEventFilter(QObject *filterObj).  There it reads:
>         If multiple event filters are installed on a single object,
> the filter that was installed last is activated first.
> In other words: you want to connect the zoomer (connecting via its 
> constructor) BEFORE the picker.  Alternatively you may want to
> redesign the handling of mouse buttons in the picker to return false
> if a button has been used that is to be passed on to the zoomer (in
> my case I use the middle button for the rectangle and the right to
> zoom out again).
> 
> Additionally, you will probably want to modify the zoomer a little.
> I put the following lines into the constructor of my subclass of
> QwtPlotZoomer: setMousePattern(QwtEventPattern::MouseSelect1,
> Qt::MidButton) ; setMousePattern(QwtEventPattern::MouseSelect4,
> Qt::MidButton) ; setMousePattern(QwtEventPattern::MouseSelect2,
> Qt::RightButton, Qt::ControlModifier);
> 	setMousePattern(QwtEventPattern::MouseSelect3,
> Qt::RightButton); (again:  select with mid button and zoom out with
> right button; alternatively, there is also a function that takes
> const QVector<MousePattern>& as argument). This changes the role of
> the mouse buttons.  I'd like to refer you to the documentation of
> QwtEventPattern (from which the zoomer inherits) as my memory of what
> I did back then is rather dim...
> 
> Best wishes and success,
> 
> Hendrik

-- 
Sergey Popov
B. Verkin Institute for Low Temperature Physics and Engineering
Kharkov, Ukraine

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
qwt-interest mailing list
qwt-interest <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qwt-interest
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
qwt-interest mailing list
qwt-interest <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qwt-interest

Re: Implement selection of multiple points on QwtPlotCurve

Hi guys!

Again and again... I'm trying to find a way to make my qwt-base app
work the way I want it. There's wonderful event_filter example that
shows how to handle events and how to mark points without replotting.
It's great! But!.. I need a way of selectig many points in my app.
I implemented the code for keeping selection and adding/removing points
to/from it.
Now I can select many points on my graph. I reimplemented replot() like
this:

void Plot::replot()
{
    canvas()->setPaintAttribute( QwtPlotCanvas::ImmediatePaint, true);
    QwtPlot::replot();
    canvas()->setPaintAttribute( QwtPlotCanvas::ImmediatePaint, false);

    if (selectedCurve!=NULL && !selectedPoints.isEmpty()) {
        markSelectedPoints();
    }
}

void Plot::markSelectedPoints()
{
    if (selectedCurve==NULL || selectedPoints.isEmpty()) return;

    QwtSymbol *symbol = const_cast<QwtSymbol
    *>(selectedCurve->symbol());
    //remember brush
    const QBrush brush = symbol->brush();
        symbol->setBrush(QBrush(QColor(Qt::red)));
        QwtPlotDirectPainter directPainter;

        for (QMap<int,QPointF>::const_iterator
        i=selectedPoints.constBegin();i!=selectedPoints.constEnd();i++)
        {
            directPainter.drawSeries(selectedCurve,i.key(),i.key());
        }
    symbol->setBrush(brush); // reset brush
}

This works with acceptable speed on X11 but it's really slow on
Windows. I thought this could be cased by expensive QwtPlotDirectPainter
initialization which is called for each point I have to repaint.
I introduced new method to repaint all "marked" points with single
QwtPlotDirectPainter object and interation cycle for my
QMap<int,QPointF). But it's still really really slow on windows (and
fast enough on x11)
For test I selected approx. 1000 points and it took 5 secods to mark
points as filled red triangle on size 7,7. It tooks few
(hundreds of) miliseconds on x11.

I must note that when I select interval of points and call drawSeries
with from and to then it paints really fast. But it's slow to call
drawSeries(curve,index,index) :(

So the question is: How can I improve speed of repainting of number of
points on the graph if I'm not sure that selection does not have gaps?

Second question is: How can I draw new data on plot with
QwtPlotDirectPainter without replot? I tried same method but it plots
symbols only, and I need it plotted as CurveStyle:Lines

To Uwe:
I found that if I have something painted with QwtPlotDirectPainter on
plot and if plot looses focus then directly painted items are moved
slightly up (2px) and left (2px). You can test this on
event_filter example on windows when you have point selected and you
pressed Alt+Tab which calls window switch selector. At least I have
this bug on Windows XP SP2. Same could be achieved on x11
Here is screenshot from windows:

--

-- 
Regards, Sergey Popov
B. Verkin Institute for Low Temperature Physics and Engineering
Kharkov, Ukraine

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

_______________________________________________
qwt-interest mailing list
qwt-interest <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qwt-interest

Re: Implement selection of multiple points on QwtPlotCurve

On 02/03/2012 03:25 PM, Sergey wrote:
> This works with acceptable speed on X11 but it's really slow on
> Windows. I thought this could be cased by expensive QwtPlotDirectPainter
> initialization which is called for each point I have to repaint.

On Windows you can't paint outside of paint events ( design by Qt ), so 
Qwt has to send a dummy event ( including what Qt does to initialize 
painting )
for each call of QwtPlotDirectPainter::drawSeries. So in your situation 
of drawing all points one by one I can imagine to have such an effect.

What about introducing a second curve, that holds the selected points only.

Uwe

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

mouse release event in example:event_filter

Hi,

   I am trying to write a App similar to event_filter example in Qwt5,
but with PyQwt5. I followed the cavanspicker class. However my
"select" and "move" works well, but the selected point did not get a
changes to be released. I defined the  add an extra handle in
eventFilter for "MouseRelease", to clear selected curve and point
index. In this way it works but the key board control does not work
any more, because the "select" with mouse now has reset the curve and
point index in MouseRelease before I move to control with keyboard.

  My question is. In the C++ version, where is the trick to "release"
the selected moving point ?

Thanks.

Best regards,
Forest.

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

QwtPlotMagnifier: Scaling canvas by click-and-drag on the axis

Hello,

My app should have yLeft and yRight axes. For plot navigation simplification I would like to make have
QwtPlotMagnifiers for yLeft and yRight axes only. And I would like to activate them by click and drag on the
appropriate QwtScaleWidget. What is the best way to do it?

I tried the following and failed:

   QwtScaleWidget *yLeftMagnifier=new QwtPlotMagnifier(canvas());
   canvas()->removeEventFilter(yLeftMagnifier);   
   axisWidget(yLeft)->installEventFilter(yLeftMagnifier);

But this don't work as I expected because there's condition in qwt_magnifier.cpp:
bool QwtMagnifier::eventFilter( QObject *object, QEvent *event )
{
    if ( object && object == parent() )
      { ... processing event  } 
}

So event filter is only processed if object == parent(). What's the reason of limiting event filter to
process only parent's events? Probably this be removed in future versions of qwt.

Other question: How to make scaling xBottom and xTop axes with click and drag mouse in _horizontal_
direction? Should I subclass QwtMagnifier and QwtPlotMagnifier to achieve this?

--
with best regards,
Sergey P.

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

Re: QwtPlotMagnifier: Scaling canvas by click-and-drag on the axis

On 02/06/2012 12:08 PM, Sergey P wrote:
> My app should have yLeft and yRight axes. For plot navigation simplification I would like to make have
QwtPlotMagnifiers for yLeft and yRight axes only.

magnifier->setAxisEnabled( QwtPlot::yLeft, true );
magnifier->setAxisEnabled( QwtPlot::yRight, true );
magnifier->setAxisEnabled( QwtPlot::xBottom, false );
magnifier->setAxisEnabled( QwtPlot::xTop, false );

> And I would like to activate them by click and drag on the appropriate QwtScaleWidget. What is the best way
to do it?

Derive from QwtMagnifier ( instead of QwtPlotMagnifier ) and implement 
YourMagnifier::rescale() yourself.
Simply copy the code from QwtPlotMagnifier::rescale() and adopt it to 
the situation of having the scale widget as parent.

Uwe

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

Problems with performance - Qwt - Xorg with 4 or 6 screens

Hi to all.

In our organization, Elettra - Synchrotron Radiation Facility, Trieste,
Italy, we have used Qwt since many years now...

After introducing four and six screen computers, working with large
control panel applications with plots displaying data at a refresh rate
of 10Hz has become painful... Two or three of such applications can hang
the whole machine. This is not an issue if the same scenario takes place
in a "traditional" computer with one or at most two screens.

Xorg process is the one that takes 100% of the CPU usage in 4/6 monitor
machines, things getting even worse when the application window (i.e.
the plot inside it) grows in size.

Reading the past messages in the mailing list, there seems to be no way
of using the hardware acceleration to draw Qwt plots.
Nonetheless, we need to find a way to speed up the Xorg drawing process
in order to make our workstations usable even in the case of computers
connected to four or six screens.

In conclusion: is there any hint to optimize Xorg or Qwt paint process
in order to make our applications run smoothly?

In machines with 4 and 6 screens Xorg is slow and takes 100% of CPU also
when other applications require fast repaint of an area, such as a web
page being scrolled...

Thanks for any help 

---
Hardware configuration:

Intel(R) Core(TM)2 Quad CPU Q9550  <at>  2.83GHz

4GB RAM

nVidia NVS 450
4 * 20" displays 1600x1200 (DVI-I)
2 * Full HD TVs  <at>  1920x1080 (DVI-I/HDMI)

Ubuntu 10.04 + KDE 3.5.12 + Qt 4.6.2 + qwt 5.2.0

Thanks, Giacomo.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

win32/MSVC Qwt Polar installation

We are trying to install qwtpolar per the documentation on some Win7 development machines and have run into
a few problems.  I've read the qwtpolar INSTALL as well its pointer to
http://doc.qt.nokia.com/4.7/qmake-advanced-usage.html#adding-new-configuration-features
(and several older forum posts).

But unless I've missed something, I think there are a few small changes to qwtpolar 1.0.0 that are necessary
for it to build/install out of the box using Windows/MSVC.  We're using Qt 4.7.3, qwt 6.0.1, MSVC 9.0 (VS
2008).  We installed qwt 6.0.1 (nmake, nmake install).  I've edited qwtpolarconfig.pri to just build the
core library (no plugins or examples).  I didn't see much else to change in any of the qwtpolar .pro/pri files.

After some effort, I got qmake to find qwt.prf, but building still fails (either from the command line or
within qtcreator):

C:\qwtpolar-1.0.0>nmake
<snip>
qwt_polar_item.cpp
.\qwt_polar_item.cpp(346) : error C2027: use of undefined type 'QwtScaleDiv'
        c:\qwtpolar-1.0.0\src\qwt_polar_item.h(23) : see declaration of 'QwtScaleDiv'
<snip>
qwt_polar_curve.cpp
.\qwt_polar_curve.cpp(11) : fatal error C1083: Cannot open include file: 'qwt_polar.h': No such file or directory
<snip>
qwt_polar_layout.cpp
.\qwt_polar_layout.cpp(352) : warning C4146: unary minus operator applied to unsigned type, result
still unsigned
.\qwt_polar_layout.cpp(352) : warning C4146: unary minus operator applied to unsigned type, result
still unsigned

I'm not sure if the last warning is a concern or not, but can be fixed by being more verbose: -1.0*d_data->margin.

The first (QwtScaleDiv undefined) I believe is MSVC being more finicky about when forward declarations
are sufficient.  If I add a #include <qwt_scale_div.h> to qwt_polar_item.cpp, that error goes away.

A little more perplexing is the second issue:  it appears to have something to do with the fact that MSVC
creates separate debug/release subdirs and the compilers working dir.  If I change the offending
#include in qwt_polar_curve.cpp to <../qwt_polar.h>, everything builds successfully (subject to fix
above).  What bothers me is I have no idea why that particular header and that particular source file is the
only one that is a problem!  And clearly my "fix" for this isn't right--I'm not sure what the right
cross-platform tweak is the correct one.

I hope this is helpful.  Uwe, I didn't bother with an official diff/patch submission since the changes are so
simple, assuming you think the changes are acceptable for 1.0.x inclusion.  Thanks,

Ed

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/