On Monday, 23 November 2020 21:32:10 PST Ramakanth Kesireddy wrote:
> UI Application is Qt 5.6.3 widgets based on 4.14 linux kernel built with
> yocto meta-qt5 recipes.
Please retest with the latest first (latest Qt and latest Yocto).
And if you're not using X11, please be explicit on what backen
Hi,
UI Application is Qt 5.6.3 widgets based on 4.14 linux kernel built with
yocto meta-qt5 recipes.
For all different views like QTableView,QTreeView, am using the inbuilt
QScrollBar.
The mouse wheel works, the up and down arrows on the scroll bar work, but
unable to drag the scroll bar using t
i have a main window with the menu bar
then a secondary, separate window.
since i want both windows to come to front when the user switches into it, and
i also want the key shortcuts from the menubar to function in the second
window, i set the parent of the 2nd window to the main window. doing
that is exactly what i did and it worked like a charm.
> On Nov 23, 2020, at 10:25 AM, Matthew Woehlke
> wrote:
>
> On 05/11/2020 12.24, Jérôme Godbout wrote:
>> Maybe you can add an event filter and remove some of the events if
>> they are happening too close to each others. But I thing doing
I had a similar issue a long time ago and I didn't want to spend much
time so I used an ugly workaround. I'm interested in the proper
solution, but this works https://github.com/fferri/qt3d-thing/pull/1
I think Qt 3d needs a proper "Loader" (so you can do something like
this
https://doc.qt.io/qt-
We're in the process of migrating our Android builds from Qt 5.13.0 to
5.15.1. Something that has changed between these two versions is the
default naming scheme for target libraries built using qmake. In our .pro
file, we specify (for example):
TARGET = MyLibrary
In Qt 5.13.0, this produced an o
On 05/11/2020 12.24, Jérôme Godbout wrote:
Maybe you can add an event filter and remove some of the events if
they are happening too close to each others. But I thing doing that
logic into the event handler is a betetr idea, where you can either
cumulate and delay execution of the behavior.
This.
I pushed these files and the QtC project to
https://github.com/fferri/qt3d-thing
On 23 November 2020 at 17:49:17, Federico Ferri (federico.ferri...@gmail.com)
wrote:
Following your advice, I changed Array.qml to the following: (most notably:
added the repeater.model property alias)
[…]
Cheers,
Following your advice, I changed Array.qml to the following: (most notably:
added the repeater.model property alias)
Entity {
id: root
property alias model: repeater.model
property int length: 1
property Transform transform: Transform {}
property Component itemDelegate
Il 23/11/20 14:20, Federico Ferri ha scritto:
but of course in this example it is using a non-existent ‘index’ in the
PhongMaterial.diffuse binding.
Are you sure it's non-existing? The context in which that delegate is
going to be created should have "index" injected into it.
Needless to s
Hi,
I'm using qtcreator only for debugging. I always get "Semantic issue" markers
beside the source code line numbers, which interferes with the breakpoint
markers.
See attached screenshot. One can not easily see what is a breakpoint.
I want to get rid of the display of the "Semantic issue" marke
Consider a “basic” usage of NodeInstantiator:
NodeInstantiator {
delegate: Entity {
components: [SphereMesh {radius: index / 10}]
}
}
We can use the ‘index’ property in delegate’s properties bindings.
Now consider this custom Qt3D Entity (Array.qml, repeats the delegate n
ti
Can anybody take a look at this question:
https://stackoverflow.com/q/64964751/3405291
Thanks
☺
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
13 matches
Mail list logo
