For those who end up looking here : It seems that this is a Qt 5.6 bug, it works fine in Qt 5.14 Edit : The bug itself may be related to the use of QSurfaceFormat::setDefaultFormat after application startup : Qt 5.14 warned me about a piece of code I was not aware saying that it could cause context sharing issues. Having it removed seems to have solved the bug when i got back to Qt 5.6

@Yash001 That is beyond my experience level. No help possible from my side.

@JonB I'm sorry, I thought it would be helpful if people saw the entirety of the code. I didn't know which part of the code I was lacking. Ohhh. thank you for the instruction. I'll work on the changes.

@SGaist Thank you for answer. From your suggestion, I need to create my own Dialog box.

@Konstantin-Tokarev The problem has been solved. I change the float strategy from neon to vfpv3 and everything works well.

http://doc.qt.io/qt-5/plugins-howto.html#the-low-level-api-extending-qt-applications

@mrjj yes. Everything correct. Thanks for the help

@KroMignon said in Update from Qt 5.4.2 to 5.6.3 on Windows7/XP: Is some one aware about those issues? Probably it is better to check on JIRA if those are known issues. @KroMignon said in Update from Qt 5.4.2 to 5.6.3 on Windows7/XP: Is here the right place to post this kind of questions? Also on JIRA you may find already work arounds or discussions. If you do not get feedback within a reasonable time frame, you may want to check with the developer mailing list.

Thanks for the help. I unistall and reinstall the qt 5.6 along with ESRI ArcGIS. The error goes away. Thanks for the tip. Mathan

Hello @SGaist, Thanks for the tip I will post also on the interest mailing list. Nevertheless I did not modified the qt sources and builds were working fine after compilation for Linux 32 bits and QNX, I just had to add QtWebKit from the community release because it is not a part of official release anymore. Actually for QtWebkit on QNX, the app seems have found the module but not the proper version (3.0). For Virtual Keyboard I did nothing more than compiling and try to use the exemple provided with Qt sources, first on Linux 32 bits then on my QNX arm v7 target. I did that with several others QML examples also provided with Qt sources and I did not encounter that kind of behaviour, no other modules where missing. Maybe i missed something on my target configuration (libs install, Path, ...), I just would like to know if there is a way to list which modules and version are properly installed on a specific system (Linux, QNX).

@mvuori Tried to build *.apk on Qt 5.7.0 RC - the same error. I think, that bug for a long time.

Apologies to Diamond Platypus, I must not have had this post flagged as watch. Anyway, I did add: QMAKE_CXXFLAGS += -static-libgcc -static-libstdc++ To my .pro file I still have missing dlls: libgcc_s_dw2-1.dll libwinpthread-1.dll libstdc++-6.dll

I had issues making these solutions work for the QML TreeView. I ended up setting the root path of my QFileSystemModel to the directory I wanted to view. Then I set the rootIndex in the TreeView to the parent of the index for that directory. This is of course showed its siblings. Then I did the following to filter those siblings away. I also made this optional through a property as there are times when I want that behavior: bool filterAcceptsRow(int source_row, const QModelIndex &source_parent) const { FileSystemModel* tmodel = qobject_cast<FileSystemModel*>(parent()); if(tmodel){ QModelIndex index = tmodel->index(source_row, 0, source_parent); QModelIndex rootIndex = tmodel->index(tmodel->rootPath()); if(!rootIndex.isValid() || !index.isValid()) return false; return ((index == rootIndex) || !(tmodel->filtersiblings() && isSiblingOf(index, rootIndex))); } return false; } bool isSiblingOf(const QModelIndex& index, const QModelIndex& parent) const { if(!index.isValid() || !parent.isValid()) return false; QModelIndex sibling; int row=0; do{ sibling = parent.sibling(row,0); if(sibling == index) return true; ++row; }while(sibling.isValid()); return false; } I took more of a blacklist approach versus a whitelist approach.

@Zakaria Thanks! Still working in 5.9.2.

Hi and welcome to devnet, How did you compile that module for your BBB ?

No problems as such, but a launcher application named Start was perhaps not compatible with Android 6 and managed to make my app lose texts on pushbuttons... That application was not updated when the OS was updated and the mechanism how it managed to do mess up another app is unclear... (Of course it can be that Qt 5.6 has a deficiency that makes it vulnerable to environmental issues in Marshmallow.)

Thanks !

Did you install MSVC2015 before or after Qt ? Can you see it in the Compilers tab ?

I didn't notice it ... silly mistake. Many thanks for the hint and best regards, Marek

@jpnurmi thx forthe info. then I will remove this for mobile app development

hi and welcome If you right click mainwindow there is css editor and u can set stylesheet there. This then applies to all child's of window. As far as I know there is no way to have Designer do on all forms.

Thatt did the trick, thanks!

That did it, Thanks!

@krzaq I'm surprised anything changed at all with the c++14 flag. Are you using 5.6.0-rc ? In my caseCONFIG += c++11 c++14 doesn't seem to do anything at all when compiling to Android. I'm using 5.6.0-rc and with CONFIG += c++11 c++14 I'm just getting -std=c++11. With Qt 5.5.1 CONFIG += c++11 c++14 I get -std=c++1y added to the mix and I can use relevant functionality (std::make_unique).

Hi and welcome to devnet, Qt3D being in tech preview, I'd recommend posting your question on the interest mailing list. You'll find there Qt3D's module maintainers/developers (this forum is more user oriented)

Hi, There's a WIP branch in the qtbluetooth module for Windows, you can check the state there.