On quarta-feira, 27 de dezembro de 2017 15:08:35 -02 René J.V. Bertin wrote:
> Hi,
>
> Is there a way to access the file names or, better yet, the metadata of the
> plugins that are currently loaded? QPluginLoader::staticInstances() and
> QPluginLoader::staticPlugins() return empty lists for me. M
Hi,
Is there a way to access the file names or, better yet, the metadata of the
plugins that are currently loaded? QPluginLoader::staticInstances() and
QPluginLoader::staticPlugins() return empty lists for me. Maybe they're
supposed to exclude the platform, platform integration and style plugin
Hi,
On 27.12.2017 13:36, Igor Mironchik wrote:
Hello folks,
Could you look at this short video, please?
What do you think about it?
Thank you.
Got it, seems that this is a bug...
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-
Nice, thanks a lot!
2017-12-27 13:36 GMT+03:00 alexander golks :
> Am Wed, 27 Dec 2017 12:47:01 +0300
> schrieb Oleg Evseev :
>
> > Hi all,
> >
> > According to documentation in qt there is a workaround lupdate_only{...}
> -
> > conditional statement so the lupdate tool sees some file (for exampl
Am Wed, 27 Dec 2017 12:47:01 +0300
schrieb Oleg Evseev :
> Hi all,
>
> According to documentation in qt there is a workaround lupdate_only{...} -
> conditional statement so the lupdate tool sees some file (for example .qml
> files) but the C++ compiler ignores them.
>
> I wonder if there is a op
Hi all,
According to documentation in qt there is a workaround lupdate_only{...} -
conditional statement so the lupdate tool sees some file (for example .qml
files) but the C++ compiler ignores them.
I wonder if there is a opposite workaround some conditional statement (or
something else) so the
