As my eyesight gets older I notice that reading some if not most of the UI text labels etc. ( not source code) its too small for me to make out clearly. i.e
It's basically HiDPI mode, a 4K display with a 1920 x 1080 working area. So, things are easier to read, but I still have the resolution for working with images or Hype projects.
Yet, scaling the interface does seem like a good idea for Hype 5. That could be a lot of work to get right though.
Thanks, I filed a bug about this. In general there are certain paths that reset a lot of properties to work correctly when moving elements around, but I'm surprised this is the case since your group has zoom contents and therefore isn't technically "moving" its position in this case.
Symbols have their own engine, so the lookup determines which symbol the element is in and then returns that engine.
I believe a hidden secret is you could have "null" as the element and it will always get the top-level engine.
From an API design standpoint it seemed like doing it this way managed the tradeoffs a little better, but clearly arguments could be (and were) made for other ways to get the engine.
That works! I added… let engine = hypeDocument.getElementProperty(null, 'physics-engine'); …to v3 the test Hype project and the Physics bodies were bouncing as expected.
Ah, I see the logic now. While I would have preferred a simple… hypeDocument.physicsEngine() …that might be a problem in projects where there are different Physics worlds. So while null works, I'm not sure that I'd want to use it.