Re: [Interest] clang in Visual Studio Codegen supported?

On quinta-feira, 2 de fevereiro de 2017 15:02:41 PST Hamish Moffatt wrote: > Is Microsoft's clang add-on for Visual Studio 2015 (CodeGen) supported > for compiling Qt applications? (With Qt 5.8?) clang-cl is still buggy and not working properly. Some people reported some level of success after fi

Re: [Interest] using QSetting when host application is using it as well

Hi Frank. Looks like the host application uses QSettings::setPath() (http://doc.qt.io/qt-5/qsettings.html#setPath) to enforce a specific directory for configuration files. Calling that method from your code is obviously a bad idea (high risk of screwing up the host application), so your "fallback"

Re: [Interest] using QSetting when host application is using it as well

In the meantime I am falling back on using this: os.path.expanduser('~/.config/companyName/appName') While this does not give me the OS' native support directory for the respective user at least it's consistent :) I'd still be interested in a QSettings solution though. Cheers, frank On

[Interest] clang in Visual Studio Codegen supported?

Is Microsoft's clang add-on for Visual Studio 2015 (CodeGen) supported for compiling Qt applications? (With Qt 5.8?) I tried (qmake -tp vc, change settings to CodeGen etc) but didn't get far; the very first source file failed to compile with: 1> In file included from ..\..\..\..\qt\Qt5.8.0

[Interest] using QSetting when host application is using it as well

Hi all, I have been using QSettings for reading/writing user settings. All works well until I run my (PySide) application inside a host application that is also written in QT, and which also uses the QSettings object. I am now struggling to understand how I can properly differentiate between

Re: [Interest] QDateTime Issue in Qt5.8.0 msvc2013,msvc2015

On Wed, Feb 01, 2017 at 09:46:13AM -0800, Thiago Macieira wrote: > Em quarta-feira, 1 de fevereiro de 2017, às 16:33:33 PST, Günter Michel > escreveu: > > OK my fault, qDebug() results are also ok here, seems debug view related. > > I have looked at debugger Output in Qt Creator 4.2.0 ( dt (invali

Re: [Interest] QDateTime Issue in Qt5.8.0 msvc2013,msvc2015

Em quarta-feira, 1 de fevereiro de 2017, às 16:33:33 PST, Günter Michel escreveu: > OK my fault, qDebug() results are also ok here, seems debug view related. > I have looked at debugger Output in Qt Creator 4.2.0 ( dt (invalid) ) The internal format of QDateTime changed in Qt 5.8, so it's possibl

Re: [Interest] QDateTime Issue in Qt5.8.0 msvc2013,msvc2015

OK my fault, qDebug() results are also ok here, seems debug view related. I have looked at debugger Output in Qt Creator 4.2.0 ( dt (invalid) ) Am 01.02.2017 um 16:02 schrieb Mike Chinander: On Wed, Feb 1, 2017 at 8:44 AM, Günter Michel > wrote: This simple code re

Re: [Interest] QDateTime Issue in Qt5.8.0 msvc2013,msvc2015

On Wed, Feb 1, 2017 at 8:44 AM, Günter Michel wrote: > This simple code returns an invalid date compiled with Qt5.8.0 msvc2013: > > QDateTime dt = QDateTime::currentDateTime(); > > Compiling with mingw results in correct date but wrong time. Code works in > Qt5.7.1 > What's going on here? > Thi

[Interest] QDateTime Issue in Qt5.8.0 msvc2013,msvc2015

This simple code returns an invalid date compiled with Qt5.8.0 msvc2013: QDateTimedt=QDateTime::currentDateTime(); Compiling with mingw results in correct date but wrong time. Code works in Qt5.7.1 What's going on here? ___ Interest mailing list Int

[Interest] QWaylandCompositor showFullScreen at app startup

Hello, I noticed that when I try to show an app fullscreen at startup that it loses its decorations but doesn't go fullscreen(maximized) (I enabled QT_WAYLAND_USE_XDG_SHELL). But if I delay the showFullScreen with a QTimer singelshot it works fine. Is it not possible with Wayland to show an app fu

Re: [Interest] 5.8.0 Segfault on setPersistentCookiesPolicy

Hi. I would suggest running the python application under a debugger, and try to get a backtrace. That might give insight whether it is a Pythong binding issue of a Qt issue. An alternative would of course be to rewrite the small example in C++, and check if that works. > On 01 Feb 2017, at 04: