How to get rid of the "Qt: Untested Windows version 10.0 detected!" warning?



  • I am currently using Qt 5.4.2 to build my application, but on Windows 10, I (obviously) get the "Qt: Untested Windows version 10.0 detected!" warning whenever I try to run my application.

    I was therefore wondering whether there is a way to get rid of that warning? FWIW, I already have the following in my code:

    qSetMessagePattern("%{if-debug}%{endif}"
                       "%{if-warning}%{endif}"
                       "%{if-critical}%{message}%{endif}"
                       "%{if-fatal}%{message}%{endif}");
    

    but that doesn't make any difference, I am still getting the aforementioned warning.

    Cheers, Alan.

    PS: sadly, to move to Qt 5.5/5.6RC is not an option for me (see here for example).


  • Moderators

    This should work. Are you sure you're calling it before QApplication object is created? Put it at the beginning of main().

    Also, are you sure it's a good idea to disable all warnings? That particular warning is rather harmless, so you can just ignore it.
    Personally I would really reconsider updating Qt. You can still use QtWebkit with newer versions you know. It's not removed yet.



  • This should work. Are you sure you're calling it before QApplication object is created? Put it at the beginning of main().

    Yes, this is the very first thing I do in main(). Just for 'fun', I thought I would try to put a couple of traces just before and just after calling qSetMessagePattern(), i.e.

    std::cout << "Before..." << std::endl;
        
    qSetMessagePattern("%{if-debug}%{endif}"
                       "%{if-warning}%{endif}"
                       "%{if-critical}%{message}%{endif}"
                       "%{if-fatal}%{message}%{endif}");
    
    std::cout << "After..." << std::endl;
    

    But when I try to run my application (from the command line), I am getting:

    Qt: Untested Windows version 10.0 detected!
    Before...
    After...
    

    ?!?!?!

    Also, are you sure it's a good idea to disable all warnings? That particular warning is rather harmless, so you can just ignore it.

    In principle, I wouldn't mind enabling warnings, but it happens that, in the case of my application, Qt generates another warning that can be safely ignored. Personally, I don't want my application (especially a release version of it) to generate 'ignorable' warnings. Also, in the case of the warning at hand, this is causing me problems with my testing strategy, which is done using the command line version of my application. On Windows, my tests currently fail because of that 'ignorable' warning (I check the output of my program against the expected output, and because of that warning, the test clearly fails).

    Personally I would really reconsider updating Qt. You can still use QtWebkit with newer versions you know. It's not removed yet.

    I really (I mean, really) wish I could upgrade to Qt 5.5/5.6RC. As it happens, I have spent most of last week working towards that goal (in preparation for the release of Qt 5.6), but as mentioned here, I am just facing too many issues with Qt WebEngine. It's definitely not ready for my particular needs (and those of many other people too, from what I have read here and there).

    At the end of the day, I am all in favour of switching to Chromium, but it would have been good to have a near 1:1 correspondance between Qt WebKit and Qt WebEngine before ditching the former.

    I know we can still use Qt WebKit in Qt 5.6RC, but it means building it from source. My application is cross-platform (Windows, Linux and OS X), so to build Qt WebKit on all three platforms is going to be a nightmare (I had a look at building Qt WebKit from source and it's rather involved!).

    So, right now and reluctantly, I feel like I have no other choice but to stick to Qt 5.4.2 (besides Qt WebEngine, there are a couple of other issues with OS X that prevent me from upgrading to Qt 5.5, although I might be able to address those other issues).


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.