On terça-feira, 31 de dezembro de 2013 19:59:00, Till Oliver Knoll wrote:
> I've never played myself with that, but AFAIK all compiler/linker settings
> are in so-called "qmake specification" files, located in some subfolder of
> your Qt source directory. But I would not be surprised if the /MT swi
On quarta-feira, 1 de janeiro de 2014 01:14:36, Joe Liu wrote:
> I wish to compile Qt5.2 with /MT (multi-threaded) option (vc2010), so that
Replace "multi-threaded" in your statement with "static runtime". Qt already
uses the multi-threaded option, but the dynamic one.
> the Qt GUI dll can work
Hi,
I am new to this community, and didn't find answers to my question in
archinves, so hope I can ask for help here.
I wish to compile Qt5.2 with /MT (multi-threaded) option (vc2010), so that
the Qt GUI dll can work with our own project (also with /MT option).
So is there any simple way by sett
> I want to ask you if you have any ideas how to call Windows Managed Assembly
> (in DLL file) from Qt.
> I tried in several ways, but failed. Is it possible at all?
You didn't mention the ways you tried. You can of course use C++/CLR, but I
wouldn't recommend it. Qt Creator doesn't do a great
Dear all,
I want to ask you if you have any ideas how to call Windows Managed
Assembly (in DLL file) from Qt.
I tried in several ways, but failed. Is it possible at all?
Or I should create some sort of C# wrapper?
Any help would be much appreciated.
Best regards,
Igor Grivko
__
Thanks, everybody, for your replies. :)
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
That behavior looks reasonable to me -- the dialog must tell the system to
redraw it, but doing that with an unchanged dialog would be waste of time.
And obviously one can't change value of an indeterminate progress
bar/dialog as it doesn't have any value at all. :-)
Also the case when both minimu
eglfs has the evdev input handlers built-in, meaning that you will get
mouse/keyboard/touch support without any additional plugins give that it is
able to figure out the correct device.
In your case the touch events are coming from the evdevtouch plugin (the bits
of it that are built into eglf
Here is the search list of android apps that use Qt5:
https://play.google.com/store/search?q=Qt5&c=apps
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
