Mobile and Embedded

I didn't resolved, sometime it does crash I don't understand.... but when I see a little delay while I close windows it do crash. The error is very generic. Have someone an idea? My Best Regards

Thanks; will mark this a Solved.

ahh okay :-) Have Fun !

This might be a bug since I managed to do a workaround, as it only occurs if menubars are changed via @setMenuBar(QMenuBar *menubar)@ without deleting the current menubar and if there are any methods that modify the widgets inside central's widget layout(deleting,adding) before adding a new menubar. In case someone bumps into this, here is my workaround: @/* this is the first menubar which I set by default, before login and after the the user disconnects / void mainwindow::setMenuBar1(){ / do nothing here / if(this->menuWidget()!=NULL){ delete this->menuWidget(); mb=new MenuBar1(this); setMenuBar(mb); } else{ mb=new MenuBar1(this); setMenuBar(mb); } / in case it's needed do something here */ } /* this is the menubar which I set after login / void mainwindow::setMenuBar2(){ / do nothing here / if(this->menuWidget()!=NULL){ delete this->menuWidget(); mb=new MenuBar2(this); setMenuBar(mb); } / in case it's needed do something here */ }@ This workaround works 80%-90% of the time unfortunately. If someone care to help I'm open for tips.

I found the site below and follow what they are doing. http://doc.qt.digia.com/4.6/network-broadcastsender.html I found my problem is because i created the socketUDP class object inside Mainwindow constructor, application cannot received. When i put the object creation outside mainwindow (in main.cpp), data is received successfully. Thanks

Hi, I am doing the same thing. I am working with the QGraphicsView/Scene. I want to add invisible rectangular areas, that has multiple properties, like clickable, repaintable, updatable, etc. Are only the event handlers option here or SIGNAL/SLOT mechanism still can be used?

When you say "not possible to be hardware independent", are you referring to the qmake.conf edition ? That's why I suggested to ask the Toradex folks whether they were aware of that issue.

I've had problems getting a cross compile to work with the latest 3.14.y kernel builds on BBB. I was using the Linaro toolchain on 32 bit debian linux to cross compile. Even though I was using a sysroot image for the cross compile, some of the kernel includes would come from the Linaro tool and it would fail. Compile the Qt library on the BBB. It takes about a day and a half, but it detects the Sgx graphics libraries and enables EGLFS.

Hi, You can compile by yourself following this tutorials. However if you compile Buildroot, or Yocto you'll get all the components to make your system and develop applications for it. By generating SDK on Yocto you have all the you needs to cross-compile and deploy your application, the same happens with the generated qmake with buildroot. But the most valuable thing you win by doing this is that your system generates automatically. If you need a Qt's library, you just add this in Yocto or Buildroot and both development's and system's machines will be updated with the new package. I hope I have helped you.

The documentation is being updated for iOS

Maybe through QAbstractFontEngine

I can only say good luck with that project

Hi, Do you have @QT += widgets@ in your pro file ?

[quote author="houmingc" date="1414875115"] @ while(5<6) < infinite loop ? connect(&timer1,SIGNAL(),this,SLOT (setvisible()); <- why two timers ? connect(&timer2,SIGNAL(),this,SLOT (setinvisible()); <- are the timers class variables ? } void setvisible() { ui->pb->setvisible(true); } voi setinvisible() { ui->pb2->setvisible(false); }@ [/quote] Simpler version @ connect(timer,SIGNAL(),this,SLOT (toggleVisibility()); } void toggleVisibility() { ui->pb->setVisible(!ui-->pb->isVisible()); } @

Even if you do, there's no sense trying to port QtWebKit on a platform where you won't be able to use it. You can re-use the iOS version in your code and modify it to suite your needs

Hi, AFAIK, if you are using Qt 5, then just a Widget based application. Some of the APIs from Qt mobility have been merged in Qt 5.

Hi, Did you add @QT += designer@ In your pro file ?