3rd Party Software

You are, unfortunately, very right. This library of mine is still very static and the redesign is slow-going (work responsibilities are picking up towards the end of the year). With regards to interaction, have a look at the Qt Chart example if you haven't done so yet:

http://doc.qt.nokia.com/stable/itemviews-chart.html

Enjoy and good luck!

Ok
I started a new topic about this problem.
http://developer.qt.nokia.com/forums/viewthread/10343/

One other thing, no spaces in any of the directory names. This can cause weird issues as well.

I am currently working on this for you! Sorry for the late reply, I have run into other issues on another project :(

I have it now!!! Thanks! :-)

I try it, but it is dont work too:
@connect(zoomer, SIGNAL(zoomed(const QRectF&)), this, SLOT(replot()));@
But slot is calling, i tested it

"this":http://qwt.sourceforge.net/ is the website you need.

both ways are possible. "This topic":http://developer.qt.nokia.com/forums/viewthread/7597/P15 might help you.

By the way other interesting topics on devnet can be found using the qwt tag on the right of this site.

im also a real beginner and i wanna know if there's any clear advice about how to use the qserialdevice library in a project?
i cant compile the examples i guess i have to build the buildlibrary first but the problem is that i get errors inside the codes and so building the library doesnt get successful and when building the examples,i get this error : cannot find -lqserialdevice
how shuold i correctly build the library so that i can compile examples of qserialdevice and also use the library?
is there a step by step guide for that or can anybody plz tell me in detail?
ill be so thankfull for that.

I try it but it is dont work:
@plot->enableAxis(QwtPlot::axisCnt);@

[quote author="matthazley" date="1314876103"]I had a lot of comms coming in so maybe I was triggering too many signals too fast and this was growing the event queue??? I'm not sure... [/quote]

This could be the reason, ort perhaps you had some wrong connect statements (which threads are processing the comm's data? how did you do the connect, etc.).

No problem! Glad to help. Good luck with the rest of your code!

OK :)
And once more: thank for your help!

Events not being handled properly sounds like an event-loop-reentry problem. Do you call exec() on dialogs or QApplication::processEvents() somewhere?

If you can anything that displays this issue, please submit it. It is very hard for us to help you without any code we can read or (even better) try.

Please be sure to wrap all your code in @ tags. Thanks!

Yes, Qwt, another good reason ;-)

A QwtPlot should behave like any other QWidget in a QLayout. Do you use an ui file with Qt Designer or only code?
Can you show us one of them?

I have used QextSerialPort for many years and am very happy with it. Usually one would build it as a shared library and link your own applications and libraries to it in the usual way (ie edit the LIBS variable in your .pro file).

As for your second question, how you receive the data back is entirely dependent upon what protocol your serial device is using layered on top of the standard RS232 comms protocol. A library like QextSerialPort and the OS take care of the RS232 part but you are responsible for anything above that.

If you can get the bytes of your 128x128 greyscale image then you can create a QImage from them (see the many QImage constructors). You can then use a QLabel (or your own custom widget and QPainter) to show the image.

HTH

Thanks but not it. I ended up cheating and pulling it off my other machine. However, I beleive I have to load the full QT development package and then copy it to the local /lib
CT