General and Desktop

So I think there is a bug. If I set my main app with: @ ( Qt::FramelessWindowHint | Qt::WindowSystemMenuHint | Qt::WindowMaximizeButtonHint | Qt::WindowMinimizeButtonHint )@ Whe I call showMaximized() i get fullscreeen. If I remove FramelessWindowHint flag everything works great but I get a frame and I don't want that. The problem is still about how to catch taskbarmenu/systemenu messages....

You should implement detection part with native API's for different systems (like udev for Linux).

[quote author="Jeroentje@job" date="1317726501"] That is something I'm wondering about. Not real much to find in this forum :-( Got any ideas Volker? greetz[/quote] You asked this "here":http://developer.qt.nokia.com/forums/viewthread/10307/ already, so please wait for an answer over there and don't mix topics here. Thanks.

Caution! The model does not always delete the items! If you use one of the takeXX methods, like "QStandardItemModel::takeItem() ":http://doc.qt.nokia.com/4.7/qstandarditemmodel.html#takeItem, the item is removed from the model, but it is not deleted! You get back a pointer (or a list of pointers) to the item(s) and you can reinsert the item in the same or another model or you must delete it manually to avoid a memory leak.

No problem. I asked because I suspected you did mix VS2008 and VS2010 code by accident (which can easily happen with multiple Qt versions installed). Glad that it works now. Enjoy coding with Qt, and if you have further questions, we're happy to answer them, of course.

Please don't necropost to threads that ended over a year ago. Thanks.

There are no signals and the functions are enterEvent and leaveEvent. What's wrong with those?

The other method would be to get rid of the qualification in your connect and class definition. The SIGNAL and SLOT macros are triggering simply said a string matching. If you are using at one point the qualification and in the other not, it has to fail. So the code should look more like: @ connect(th,SIGNAL(MatUpdate(cv::Mat)),pct_frame,SLOT(update(cv::Mat))); @ @ public slots: void update(cv::Mat img); @ @ signals: void MatUpdate(cv::Mat it); @ or the other possibility: @ connect(th,SIGNAL(MatUpdate(Mat)),pct_frame,SLOT(update(Mat))); @ @ public slots: void update(Mat img); @ @ signals: void MatUpdate(Mat it); @

The "raster" engine is one of the QPaintEngines available inside Qt. When you paint on a QPaintDevice, that device must provide an engine to paint on it. The raster is a software engine which backs painting on QImages and QWidgets/QPixmaps on Windows (and/or other systems when you set the raster graphicssystem; it'll be the default in 4.8). X11 and OpenGL are implemented in other QPaintEngines, and used respectively by QWidget/QPixmap under X11 and QGLWidget/QGLPixelBuffer everywhere. (Actually, there are two OpenGL engines, but that's a different story).

I usually like the warnings, the can give a hint to a possible design flaw leading to hard to debug errors.

Sounds like an SQL database solution would be much more appropriate for your problem. If I was bound to the log files, I would take that in regular intervals and copy the contents into a database. The search in a DB is much more efficient than navigation such a huge file.

Bitwise ORing that two flags together yields an integer, that holds a value for LeftButton and MidButton together. Your case statement will only be executed if the event yields back that value, which would only happen if the user pressed the left and middle button simultaneously. The [[Doc:QFlags]] subclasses are not constructed to be used easily in switch statements. The testFlag() method would be a more elegant and reliable solution for you problem. You need to change your switch/case statement to a if/else if then.

@LiamMaru thx for your answer that's what i was looking for...i know i can open the file and readall then write them in new file but if the file is a 1GB size...it won't be nice :D

try declaring the mutex like @mutable QMutex _listMutex;@ I am not sure, just a tought

No, I don't think so. I think your best bet is using a QSqlTableModel subclass or a proxy model.

I think the pixelater example can be of good use for you. There they use the grey value of color pixels to determine the diameter of circles replacing the pixels. In your case you could translate them to z-values.

Wow..its wounderfull... Thanks for your valuable inputs... Its working fine now..