tringenbach

> For clarification, you found that some parts of the UI such as NaviCube were not multiplying their dimensions against `devicePixelRatio`? NaviCube is the only part looked at in any...

@oursland Currently, I am grabbing it with `m_View3DInventorViewer->devicePixelRatio();` in `NaviCube`. I haven't check if that is correct or not though, and I haven't figured out how to get hook into...

I am not really sure how to adjust the projection matrix. I also don't quite have my head around if that makes sense. I guess it's sort of like oversampling...

I posted a PR for the NaviCube changed I mentioned: https://github.com/FreeCAD/FreeCAD/pull/19929 With those changes, on my MacBook Pro, it now looks like this: If I change my Mac's settings from...

@JohnOCFII @oursland I think, based on reading the links I posted above on this issue, that it's important to know the devicePixelRatio for this discussion. So I opened an PR...

I opened a draft PR for the Sketch changes I mentioned earlier: https://github.com/FreeCAD/FreeCAD/pull/20038 Here's what it looks like for me: ``` OS: macOS Sequoia (15.3) Architecture: x86_64 Version: 1.1.0dev.40584 (Git)...

@hyarion and @oursland: > For OpenGL, can't we just adjust the projection matrix to compensate for the difference between logical and physical pixel sizes? I guess I'm not getting how...

> Maybe not relying on MQTT could open up a way to get access to the camera? I would support that project. Is the camera exposed over the Control4 https...

> looks like the resolver compat tests are also failing Whoops. I'll try to get this fixed. Looks like they're related to the "web" platform: > ● with package exports...

> in tests/metro-compat/resolver/resolve.ts change the following: Ok, I applied your fix, thanks! I was trying to understand if that was really good enough or not, but I guess it is....