General and Desktop

Ahh, adding Q_OBJECT to the subclass did the trick. Thanks panosk.

Great Maxoreli! That's the problem, appears to be a Bug? Or Not? Thanks a lot!!

@Boysie: I can not follow your description of the problem you ran into. You mention cmake... what has that to do with anything? If you set up a cmake project then creator will of course not run qmake as that is a completely different build system. Creator will make sure the Qt binaries are in the PATH whenever it runs anything. So far I never got any complaints that this fails to work, you are the very first. So what exactly are you doing? What kind of project is it? Did you open it via a CMakeLists.txt file or a whatever.pro file? Yes, development on Linux is much simpler than on Windows, I fully agree with you there. We can not ship the MS tools for building software for legal reasons. There is no way around that. We did put the mingw tools into the Qt SDK, but IIRC don't do so in the stand-alone Qt Creator installer. That is supposed to be as small as possible... people do complain about the download sizes when we include extra stuff, especially those that have a mingw set up already.

thanks. It works! Alife! Alife!

Thanks TheloniousBonk, this solved my problem! Now appears other: @ process_begin: CreateProcess(NULL, bin\rcc.exe -name Resources ..\SistemaAssistenciaTecnica\Resources.qrc -o debug\qrc_Resources.cpp, ...) failed. make (e=2): O sistema não pode encontrar o arquivo especificado. mingw32-make[1]: *** [debug/qrc_Resources.cpp] Error 2 mingw32-make: *** [debug] Error 2 09:33:48: The process "C:\MinGW\bin\mingw32-make.exe" exited with code 2. Error while building/deploying project InoveBEV (target: Desktop) When executing step 'Make' @ [quote author="TheloniousBonk" date="1352509613"]I hit the same problem today when I attempted to build my app with MinGW for the first time. I got around the problem by adding the following line to my .pro file: CONFIG += exceptions [/quote]

I, for whatever reason, thought you've raised the initial question, so I've wondered why you've shown such an example. But you are obviously not, and it starts making sense now. ;-)

Use QDomNode nextSibling() while nextSibling's QDomNode will have the tag name 'passwords' and append to it your QDomNode. References: http://qt-project.org/doc/qt-4.8/qdomdocument.html#createElement http://qt-project.org/doc/qt-4.8/qdomdocument.html#toString http://doc.qt.digia.com/qt/qdomnode.html#appendChild http://doc.qt.digia.com/qt/qdomnode.html#nextSibling And read a bit about QtXml.

Glad to know it.

Answer: Changing boundingRect() to return QRectF(x, y, w, h) fixed the problem.

Thank you. I'll be trying soon reply to you what happened.

No problem! Be sure and retitle the thread as [Solved]. Thanks!

[quote author="MrDev" date="1352484489"]Hi, tucnak. Thank you for your reply. yes, that was my version... @void MyWidget::keyPressEvent(QKeyEvent *event) { switch (event->key()) { case Qt::Key_X: if (event->modifiers() & Qt::ControlModifier) { qDebug() << "yep"; } break; default: QWidget::keyPressEvent(event); } }@ It doesn't work again. When I change the Qt::Key_X with Qt::Key_Z for example, it is ok. But with the letters X,C,V it doesn't. [/quote] Hm... it should be interesting. Sorry, I am busy today, so you should wait for other users or tomorrow)).

This is the "link":http://qt-project.org/quarterly/view/location_and_mapping_services to the tutorial.

Don't think you need to recompile openCV. If that is the problem, the program woudn't run anyway and give a "couldn't find dll" stuff errors. As mrdebug says it is probably caused by Win7 and how it handles webcams. Maybe install Qt on a Win7 and start testing it there. Greetz

Hi, ~dev_jiang! Evaluating JSON with QScriptEngine is not the best idea. If to be honest - it's a bad practise. Why is? Just cos it takes too much memory. Use it only if you need to evaluate JavaScript code, not it's notation. There is one of my favourite libraries - QJson. It allows to work with JSON on the QVariant* level. Read, write, serialize, etc. Project link: http://qjson.sourceforge.net/

I found the cause, and a workaround. My "Compilers" list contained MinGW GCC 4.4 (manually added), which I was using alongside the pre-built Qt 4.8.3. I believe this was somehow causing trouble when I tried to add my new qmake.exe, which was built using GCC 4.7. GCC 4.7 is in my PATH, and is also auto-detected, but I guess Qt Creator tried running GCC 4.4 first. When I removed GCC 4.4 from the list, Qt Creator happily added my new qmake.exe

You mean those lines in this Udp sing thing? @rBytes = this->socket->write(buf,maxl); //only for connected state? Where is the destination ip/port? this->socket->flush(); this->socket->waitForBytesWritten();@

Worked properly, thank you: implementation: @ int dpi=QPaintDevice::physicalDpiX(); int fontsize=dpi/12; //change to your liking QFont myf=QApplication::font(); myf.setPixelSize(fontsize); QApplication::setFont(myf); @ [Edit: Added @ tags -- mlong]