Thks mrjj it fixed my problem

I have the same issue too,have you sloved it, if you sloved it , please teach me, thanks a lot!

@nnzz
Qt is platfom-independent. Therefore it's only going to supply common information, e.g. DirectX is Windows only. If QSysInfo does not have what you want you are going to have discover what the native C library calls are for your platform and call them. [Edit] Or, as @raven-worx has shown, maybe there's a command you could run and parse its output (though obviously that's slower than a native call).

I don't see any relations to Qt programming here. Also I don't see any QtDesigner screenshot here...

@Gert-van-der-Zwan Well, an RC is newer than current stable version. Simply remove the RC version of QtCreator in Maintenance Tool and then select "Qt/Tools/QtCreator" there,

Hi @SGaist and @aha_1980

The issue was solved. Its related to linux OS problem. Its will work well with linux mint 19 OS. Before the earlier version of linux, the data received as encoded format only. In Linux mint 19, it will work fine in both cutecom as well as Qt application. Thanks for the support to solve the issue.

@Loc888 You should simply install MinGW 7.3 through Qt Maintenance Tool together with Qt for MinGW 7.3 - this will work.

Update: The reason changes to the application palette do not affect QMacNativeWidget is that its constructor sets the palette explicitly. Once the palette is set explicitly, changes to the application palette no longer propagate through the widget.

The simple solution is to just reset the palette to the default palette

setPalette( QPalette() );

Once this is done, change to the application palette start affecting the widget and its children.

[edit: fixed class name SGaist]

Hi,

What easy deployment are you talking about ?

On macOS, you can use macdeployqt for the deployment of your application.

@s002wjh
http://doc.qt.io/qt-5/qwidget.html#enabled-prop
http://doc.qt.io/qt-5/qplaintextedit.html#readOnly-prop

okay so here's what i found for my existing libs:

Z:\kJams\External\boost_1_68_0\stage\lib>dumpbin libboost_thread-vc141-mt-gd-x64-1_68.lib /headers | findstr machine 14C machine (x86)

and i'm like... WHAT? this bin file SAYS "x64" in it's name, yet it's geared to an x86 machine?? How is that possible? why would that happen? any idea? that's not something i would have ever thought to question.

Okay so i'm going to rebuild the whole boost kitt'n-kaboodle. fine.

since i'm rebuilding, i'm going with 1.69.
when i build, running the command line tools for VS2017, of course. i'm just doing the default everything, like this:

bootstrap .\b2

right? i am assuming it's going to build 64bit, am i wrong?
but i see this quite a bit:

c:\python27\include\pymath.h(22): warning C4273: 'round': inconsistent dll linkage C:\Program Files (x86)\Windows Kits\10\include\10.0.17134.0\ucrt\corecrt_math.h(533): note: see previous definition of 'round'

should i be worried?

this build results in the following:

Z:\kJams\External\boost_1_69_0\stage\lib>dumpbin libboost_system-vc141-mt-gd-x64-1_69.lib /headers | findstr machine 8664 machine (x64)

and that seems more like it.

AND HOLY CATS that was the whole problem!!

Thanks everyone for the hints and tips. I hope this topic helps someone in the future!!

Hi,

Also, you should use QUrl::fromLocalFile. It will build the proper URL.

@mrjj
Hi, thanks for the tip.

I just implemented needed methods for the pinch gesture, but I still have the same problem. The gesture is just an event and the mousePressEvent still gets triggered too.
In the mousePressEvent I do plenty of important stuff, so I need to find a way of knowing in the mousePressEvent, weather a gesture is triggered at the same time (and ignore then) or something like that.
Does someone know a workaround or how this problem is typically handeled?

@J.Hilk yeah, I did see that; I guess I just didn't fully understand its implications. I probably mis-designed this part of the app anyway - the socket I/O is lengthy enough to be in a separate thread.

@Pablo-J.-Rogina I did an error, it works with time->stop

@J.Hilk
In the example code I provided hours, minutes, etc, are all integers. Time in nanoseconds is fetched and the values extracted.
This version does not have QtDateTime but does have QTime. I noticed that the underlying format is not explicitly stated.
This is a strip chart function and most, probably all, the parameters to be charted arrive with a time stamp as a double. That time may be in millisecond, micros, or nanos so I wrote the basic code to work with any. Simple switch statement. Formatting was easy once each part was handled separately. Just a bit ugly 'cause there are four sets of if statements. Then just concat them:
qtime = qdays + qhours + qmin + qseconds
I am going to leave that code in place for now. This time I'll remember to mark the thread as resolved.
Thanks again for your time.

First thanks to all who commented.

I have now had a chance to see what the dialog looks like. I am under Linux. Apart from the fact that the dialog looks rather different, I have had to give up on the whole principle of using QFileDialog::getSaveFileName(). This is because (under Linux) it cannot handle correctly appending a file suffix/extension for the selected file type (as it can under Windows/MacOS), and IMO this makes that dialog "unusable" for my users. This is all covered in e.g. the comments to https://stackoverflow.com/a/1953781/489865. Since I cannot be bothered to give up on the convenient static getSaveFileName() and start writing my own sub-class and do it all via an instance, it works for my current situation to just present my own dialog asking which format to export to and I can get away without asking the user for a path. Ho hum.

@alexqt143 said in qtcreator: includes not displayed:

works, thanks!

Please don't forget to mark your post as solved! Thanks.

Thank you J.Hilk, it works perfectly!