Import mesh -> file dialog disabled window (blue overlay / can't click)

[jerwitt]

Not a bug report exactly, but experiencing an issue where any kind of 'file->open' type modal popup activity in Fusion dims the whole app area (presumably the normal behavior of disabling input to the main window to give focus to the modal... However, on my setup, that modal dialog also under the cover of the no-click dimmed zone, so I can't click anywhere on it.

I can navigate with keyboard (and accelerators work) to an extent, but can't mouse click. Anyone else see this? is there a workaround?

Additionally, the disabled area is permanently present on other desktops as well as many of the screen elements when the window is not minimized.

Disabled area with modal underneath in z-order

Disabled area present (and actively resisting clicks) on other desktops

[OrhanYigitDurmaz]

wait.. you dont, get crashes? whats the fusion and linux version?

[jerwitt]

Fusion is newest.
Linux version is Ubuntu 24.04.2 LTS
Running latest Wine10.0 (Nvidia proprietary drivers)
I had to manually find the bits and re-patch the Qt6WebEngineCore.dll because the file changed in recent upgrade (This fixes the persistent qt6 crashes when rendering the data panel)

I tried this almost a year ago, and it wasn't so good, but now it's almost usable.

I know it's a thankless job, but many thanks to all those who haven't given up.

[OrhanYigitDurmaz]

Fusion is newest. Linux version is Ubuntu 24.04.2 LTS Running latest Wine10.0 (Nvidia proprietary drivers) I had to manually find the bits and re-patch the Qt6WebEngineCore.dll because the file changed in recent upgrade (This fixes the persistent qt6 crashes when rendering the data panel)

I tried this almost a year ago, and it wasn't so good, but now it's almost usable.

I know it's a thankless job, but many thanks to all those who haven't given up.

why is that patch even needed? why?

[jerwitt]

Who knows, I think it has something to do with window boundaries.
Anyway, in that file the new location of the byte pattern is at 0x03d81a11

at 01cc 4883 change the cc -> 90 using hex editor.

(snippet of "unpatched") as of 27May25 fusion release ==> location 03d81a11

03d81a00: 150b 47c8 0285 c075 01cc 837c 2440 0474  ..G....u...|$@.t
03d81a10: 01cc 4883 c428 c3cc cccc cccc cccc cccc  ..H..(..........
03d81a20: 4889 5c24 0857 4883 ec20 488b da48 8bf9  H.\$.WH.. H..H..
03d81a30: 4585 c075 1c41 b800 4000 00ff 152f 45c8  E..u.A..@..../E.

[jerwitt]

Answering my own question here, I found a work around to original problem.

Seems there is little sliver at very top edge of window that is still clickable. If you grab that with mouse you can position the window out of the way so you can get to the dialog.

Here:

Like So: (if the dialog moves with parent window, you can prevent that with the gnome-tweaks app by disabling the "attach modal to parent" in window options)

Messy and wrong, but works

[OrhanYigitDurmaz]

Who knows, I think it has something to do with window boundaries. Anyway, in that file the new location of the byte pattern is at 0x03d81a11

at 01cc 4883 change the cc -> 90 using hex editor.

(snippet of "unpatched") as of 27May25 fusion release ==> location 03d81a11

03d81a00: 150b 47c8 0285 c075 01cc 837c 2440 0474  ..G....u...|$@.t
03d81a10: 01cc 4883 c428 c3cc cccc cccc cccc cccc  ..H..(..........
03d81a20: 4889 5c24 0857 4883 ec20 488b da48 8bf9  H.\$.WH.. H..H..
03d81a30: 4585 c075 1c41 b800 4000 00ff 152f 45c8  E..u.A..@..../E.

aannd... what does this do?

[jerwitt]

aannd... what does this do?

As near as I can tell, the original patch cause the program to just ignore whatever error it thinks it found, instead of tripping INT3 (which is often used to break for debugger)

opcode 0xcc => int3
opcode 0x90 => nop (do nothing)

[str0g]

Before action require to work with additional window switch fusion from full screen to window mode, then you can grab new sub window and work like usual.