qml scope is so broken I want all the people who are responsible for it to step on a LEGO brick. Or maybe a D4.
It's probably javascript original fault, but the qml team did nothing to mitigate the problem.
Discussion
Loading...
Post
Also looking for ref on a qml var in QtCreator is broken and it's fucking annoying. I don't know if any other ide does it better but I'm kinda stuck with qtc anyway.
Both fact combined means I have a var I have no idea where it comes from. And just doing a string research is gonna be a nightmare but it's still my best option.
tbf "objectName" is a pretty bad var name. But it wouldn't be an issue if qml scope was sensible.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled