General and Desktop

I know no implem,entation for that. So my guess is you have to create your own plugin manager for that. Plugins in genereal can be done in Qt. But this storing of data and update on new files is not done there.

[quote author="Gerolf" date="1301100490"] For the UI, you can do nearly everything :-)... [/quote] @sergex check this link "Guitar Pro":http://blog.qt.nokia.com/2010/06/17/how-qt-can-turn-you-into-a-guitar-maestro/ BR.

Afaik, it's not possible by default. A dock widget always takes space inside the main window, whcih means, it uses space, the central widget can't use. The central widget is automatically using all unoccupied space. So if dock 3 gets bigger, it will loock like it uis over central widget, but in fact, central widget gets smaller (perhaps gets a scroll bar). If it should really bo "Over" the central widget, it must be floating and then it's not docked anymore.

Great! Thanks for help peppe and Gerolf. I'm going to recompile Qt right away. :)

Now I can see.... it works now.... I'm embarassed .... :) I need vacations..... I really thank you for all! All the best!!! Ricardo Sousa

It is mentioned in the docs for "QKeySequence":http://doc.qt.nokia.com/4.7/qkeysequence.html, but if you do not happen to stumble over it, it's unlikely you have read it. bq. On Mac OS X, references to "Ctrl", Qt::CTRL, Qt::Control and Qt::ControlModifier correspond to the Command keys on the Macintosh keyboard, and references to "Meta", Qt::META, Qt::Meta and Qt::MetaModifier correspond to the Control keys. Developers on Mac OS X can use the same shortcut descriptions across all platforms, and their applications will automatically work as expected on Mac OS X. BTW: Qt just switches to the Mac's standard behavior here - so, it is not really a surprise. A Mac user without knowledge of Qt's docs would have done it the correct way intuitively :-)

Anyone using multi threading is in a for a load of problems if you're not really, really careful and know what you are doing. I know I was when I first started with it! Anyway, that's how you learn, I guess. So be prepared you'll get more problems related to threading than you can possibly anticipate now.

Thank for report!

Good solution as well, and simpler than mine! :-)

ok.. thanx..

I know what QTimeLine is and his purpose. I am just trying to build an advanced timeline control (Widget?) built with advanced graphical components (images, text, etc) and have the timeline itself move over that complex graphic (something like Movie Maker or Sony Vegas does with his timeline moving over photos and videos you add to the project). this is the sony vegas timeline for example, with several "channels" for audio and video. the vertical bar is where the time is: !http://jefa55.zapto.org/images/vegas timeline.JPG(vegas timeline)!

Thanks, that did the job along with "Qt::TextWordWrap"

And please do not write topics in all caps. It's regarded like "shouting loudly" in a real-world conversation (and hard to read anyways). I've fixed it for now. Also, a more meaningful topic would help too. The one you've chosen is quite general. Please keep this in mind for future threads. Thanks. For your problem: look at VCsala's and Gerolfs answers, as well as on florent's, they're right!

Unfortunately, it is for sure an sqlite3 db. All the tools I'm using to look into the db are treating it as an sqlite3 db.

Thank you all for your help. I have formatted my computer and reinstalled everything from the beginning. Now everything works fine with Qt Creator. I have already started developing my application. However, I can still not run the application in Windows, meaning the extension .exe, I can't really understand what is causing this. I am happy though that at least the IDE works and maybe I will deal with this problem on a later stage. Again, thank you so much all.

I solved the problem. It was a problem in the server code that under some circumstances the put content was not received or better say flushed. Thanks for your help! Bernd

When the timer times out the Terminator enters the scene. Hasta la vista baby. The application may be severly hit. Continueing from here is dangerous and can lead to the land of pain. Was that too dramatic?

If you create the process variable on stack, it will be deleted when you go out of scope, unless you explicitely synchronize to wait until process is finished. Just for testing, replace your QProcess by a QProcess*, most probably you'll have a leak the message will disappear

yep load the images into QPIxmap or QImage, create a new QPixmap @ QPixmap newPix(x,y); QPainter paint(&newPix); paint.drawPixmap(..., pix1); paint.drawPixmap(..., pix2); paint.drawPixmap(..., pix3); // use newPix as background @