-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation cube seems to get wrong mouse coordinates when built with qt6 #13494
Comments
Left or right click? Are you using a mouse, touch pad, touchscreeen? |
Mouse. Neither left nor right clicking works. I'll see if I can get a weekly build going and report back shortly. |
@maxwxyz Okay, I've built and tested whatever commit that latest weekly build you linked there is based on (a4dd600). The cube's behavior has changed in that now the cube and associated controls highlight whenever my pointer hovers over them, but still nothing up there responds in any way to any left or right mouse clicks/click+drag or anything at all. See attached video:
|
I cannot reproduce on my system and never heard about this behavior. Could you try temporarily rename your user.cfg file? |
I've got this issue on multiple machines (desktops and laptops). Granted, these are all pretty similar setups: Arch Linux, gnome desktop environment, intel graphics, freecad from official Arch repos (and now the one test I did where I built from a4dd600) |
Wait a sec. This is probably just a duplicate of #13303 |
@greyltc related to this one? https://gitlab.archlinux.org/archlinux/packaging/packages/freecad/-/issues/3 |
@greyltc, yes, it's a duplicate. |
I consider this issue to be better at describing the navicube issue than the above and would advise to have this one open and close the other one instead. @Rexbas would you have any clue why the navicube doesn't properly register mouse events when built with qt6? |
I have no idea but I am trying to compile with qt6 right now. |
It seems that the behavior of Lines 936 to 937 in eb3e83b
|
could it be related to dpi scaling? |
Don't know if it is dpi scaling. If I write the
here: Line 930 in eb3e83b Then with qt5 I get this: But with qt6 I get this: So I think something is wrong with |
I'm currently investigating this issue, from my observations this is split in two problems. One is that there's no mouse interaction with the navigation cube, so this means that at least one of SoQt or Qt6 is the culprit. The other is that reading from the framebuffer object returns invalid data, @Rexbas from what I can check is that |
Could be related coin3d/soqt#80. |
I think it is one problem. The mouse interaction with the navigation cube is not working because it can't decide which face is hovered/selected in |
Good news @Rexbas! I've found the reason why this happens. It turns out that what Qt has done might be correct and we are doing things wrong. By calling Lines 842 to 857 in eb3e83b
The only culprit I can point out is |
Is there an existing issue for this?
Problem description
The navigation cube and all associated controls up there in the top right corner of the render view do not respond to clicks.
Full version info
Subproject(s) affected?
None
Anything else?
Intel Arc GPU, Linux 6.8.5, gnome 46.0 desktop, i915 driver. Tested with all four combinations of {X11,Wayland} & Use software OpenGL {True,False}.
Code of Conduct
The text was updated successfully, but these errors were encountered: