> Why would the item pool use `std::vector m_items;` instead of a QList
> ( Or QVector ) ? I imagine it was a performance consideration, but it always
> puzzles me to see stdlib in most qt code.
There were plans to migrate to pure stdlib and some parts of the code have been
ported already whi
On 9/6/22 12:20, hug-animals via Qbs wrote:
Encapsulation:
"Access into nested items isnt explicitly supported in QML"
Hard to know what you mean exactly, because you can set properties of nested
items. Could you give an example of what is explicitly prohibited?
If you've worked on even just a s
General Update
- It was very easy to start working on the project.
- Built the QBS project with Qt 5.15 (6.3 had issues with a legacy dependency
based on QtScript)
- Tested it with LD_PRELOAD=/Path/To/File.so
Responding to Иван Комиссаров"Maybe Object (or Gadget/smth else since JS has
“object”
+1 here.
Maybe Object (or Gadget/smth else since JS has “object” type already) as it is
not a generic Item used in other items would be better.
Otoh if we choose the Item { id/name: foo } syntax, Item would be fine.
Ivan
> Perhaps also:
>
> property MyItem prop
___
