[Interest] Qt3D: One-shot compute shader

[Daniel Proksch]

Hi all,

I'm trying to implement a Qt3D FrameGraph (QML) that allows for one-shot 
dispatch of a compute shader.
My current approach is to add a ComputeCommand component to my ComputeEntity 
whenever I want the dispatch to happen.
When the compute task is done (i.e. in the next frame) I want to remove the 
ComputeCommand component again, so that the shader is no longer invoked.

Is that approach reasonable?
And is there a signal that is triggered whenever a frame is completed (so that 
I can remove the ComputeCommand)?

Many thanks!
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] How to manage build.gradle content?

[Nelson, Michael]

I wanted to prompt user to enable location services if needed, so I followed 
the example 
here.

To successfully build, I needed to add the following to my build.gradle file:
implementation 'com.google.android.gms:play-services-location:16.0.0'

However, the build.gradle file is in the build directory, created on qmake, and 
I don't always keep this build directory around. So, how do I ensure the 
build.gradle file has the required line following every qmake? Or, am I 
approaching this problem of dependencies incorrectly?

Thanks,
Mike


Please be advised that this email may contain confidential information. If you 
are not the intended recipient, please notify us by email by replying to the 
sender and delete this message. The sender disclaims that the content of this 
email constitutes an offer to enter into, or the acceptance of, any agreement; 
provided that the foregoing does not invalidate the binding effect of any 
digital or other electronic reproduction of a manual signature that is included 
in any attachment.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QFontComboBox without preview?

[René J . V . Bertin]

Nikos Chantziaras wrote:

> Unfortunately, there is no way to disable the preview.

I run my own Qt version which isn't 100% stock anyway, so I introduced an env. 
variable check for QT_FONTCOMBOBOX_NO_PREVIEW in QFontFamilyDelegate::paint() 
which determines whether the font family and size are changed or not.

This is a user preference anyway (app devs can avoid QFontComboBox altogether 
as 
Konstantin pointed out), and one can assume that a dislike of font previews is 
not limited to a single app. (IOW setting QT_FONTCOMBOBOX_NO_PREVIEW globally 
should be good enough).

R.

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest