General and Desktop

No problem. Don't hesitate to ask - we seldomly bite :-)

Another option would be small text files that you put into a resource file (.qrc). Either make one resource file for each language or make a subdirectory for each language.

Sorry, I don't have a clue why the auto completion doesn't work. I'd suggest to start a separate thread in the Tools forum, where the Qt Creator guys may catch up.

No problem to stealing my post, as long as it is profitable for all, and after reading your question, yes it is profitable. It is a good point and thanks to Andre and Volker for their answer. I will go with the first from from now on, to avoid a lot of corrections in the future when porting applications to Qt5 [quote author="sierdzio" date="1323324830"]I'll kind of steal your topic, if I may, Patrick. Please? OK, what I am, and always have been, curious about, are the "nested" includes like: @ #include <QtCore/QString> @ Are they any different from simple: @ #include <QString> @ ?[/quote]

Thank you all, now its working fine

Yes, I had checked the format of the dropped data and indeed on Windows/Mac OS X, the data had a text/uri-list format while on Linux it also had text/plain format. Anyway, for some reason, your message made me think of dragEnterEvent and testing the format of the data there, and decide whether to accept the event or not. In other words, I have created a new class which inherits from QsciScintilla and which overrides dragEnterEvent: @void QScintilla::dragEnterEvent(QDragEnterEvent *pEvent) { if (!pEvent->mimeData()->hasFormat("text/uri-list")) pEvent->acceptProposedAction(); else pEvent->ignore(); }@

That improved the performance a lot. Thank you!

I feel stupid... This particular part was used as a component, and used by one instance where the model hadn't been set. This was called first so it always seemed to crash at this call, though the reason wasn't the object I suspected.. :P Thank you for making me dig deeper! -Richard

Try this: @ setAttribute(Qt::WA_StyledBackground, true); setStyleSheet("QWidget { background-color: #FF0000; }");@

Both the problem is now solved. Previously i was not able to read from file because the file path was under different user and the second problem of extra character was due to the missing of text flag as suggested by "sierdzio". Thanks all.

It turns out that when loading an ActiveQt widget into an .NET forms in the designer view the content of the Q_PROPERTY is copied by visual studio and store in the .NET executable. If the default value of the Q_PROPERTY changes at a later stage, the .NET copy is not updated unless the component is reloaded into VS2005. Does anyone know how to prevent the .NET application from make a copy of the content of the Q_Property? I have tried to set DESIGNABLE, SCRIPTABLE and STORED all to false without it solving the problem. And yes, I have read the docs.

While the Qt documentation is very good, it does not cover everything. A QGLWidget can't have children widgets. The way a QGLWidget paints and the way other QWidgets paint don't work together automatically. While it is possible to "paint":http://doc.qt.nokia.com/latest/opengl-overpainting.html and "embed widgets":http://doc.qt.nokia.com/qq/qq26-openglcanvas.html, it can't be done by simply adding a child QWidget, and the other mechanisms come with performance consequences.

Just call @ setQuery(SQL_SELECT); @

Ok, I solved the problem but would be interested if anyone could provide me with an explanation. What I found was when the emit fullscreen is called and the windows state the first time (successful full screen) the widget window state is - Qt::WindowNoState. After reverting back to "normal size" the second call to enterFullScreen. The windows state was Qt::WindowFullScreen which is not correct. To fix my problem I added the line @ if(this->windowState()==4) this->setWindowState(this->windowState() ^ Qt::WindowFullScreen); @ to force the window state. After adding this line the full screen/normal screen switch works as expected every time. @ // SIGNAL 0 void VideoPlayerWidget::enterFullScreen() { if(this->windowState()==4) this->setWindowState(this->windowState() ^ Qt::WindowFullScreen); QMetaObject::activate(this, &staticMetaObject , 0, 0); } @ [EDIT: code formatting, Volker]

Sorry, I don't understand what you're doing. Do you compile Qt or your application? If you compile Qt, do not use the sources bundled in a prebuilt package for another compiler suite or version, but get the vanilla sources (qt-everywhere-xxx-src). While it may work to use VS2008 object code in VS2010 with some trickery, it is generally not recommended and you are likely to get no support for that here - despite being told to build Qt in VS2010 manually. Are you bound to Qt 4.6.3? It's quite old, and to my knowledge VS2010 was not supported with that version. I would recommend to use the most recent version 4.7.4, which can be built with VS2010 or 4.8 RC which has prebuilt binaries for VS2010.

I used QAction and it worked.. Thanks !!

Thank you! -- Richard

[quote author="Andre" date="1323256622"]Yes. Should be simple enough if you use a line-by-line parsing of your file. Did you try to create an implementation for that yet? Running into any specific issues?[/quote] Ya i have checked reading line by line to find some specific data it is working fine further i am trying some other operation on the data which i need.