Keyboard Input Issue

[Gammelstulle]

Bug Report

Description

Fusion360 starts successfully within Wine on Debian 12 (KDE Wayland) using your custom script. While the software is mostly usable with some acceptable crashes, many keyboard inputs, including number inputs, do not function as expected. sometimes they working but inconsistently,.

Steps to Reproduce

1. Install Fusion360 using the provided script.
2. Start Fusion360.
3. Attempt to input numbers using the keyboard (e.g., for entering dimensions or other values).
4. Observe that most number keys fail to register input.

Expected behavior

All keyboard inputs, including number inputs, should work consistently when interacting with the software.

Actual behavior

• Keyboard inputs do not register in the software.
• Inputs behave inconsistently; sometimes the keys work, but most of the time they do not. I not shure if it is time related, right now they worked after I left fusion open for 10 min but not working anymore as soon as i switch from build in scatch mode

Environment:

• OS: Debian 12 (KDE Wayland)

[sebadob]

I do have the same issue with KDE Plasma + Wayland on Fedora 40 + wine-9.17 (staging).

I played around with "window rules" (don't know how the english KDE call them) and focus / activation accept, and so on, but it does not really fix the issue. Sometimes it works when I open a window the 2nd time, or collapse and expand the browser and try again, but very inconsistently and annoying. The text input is then marked, and most often I am able to hit the delete key and delete it, but I can't type in anything new. It only work with typing in another editor and then copy &

If someone has another idea how to tackle this I would gladly try it out.

[sebadob]

What works most of the time for me now, apart from the situation where a popup opens the very first time after the application itself has been started, is the following setting in KDE (sorry it's german, but it should be clear from the symbols):

Exakte Übersteinstimmung means exact match.

Aktivierung zulassen is translated with allow activation (probably), but I don't know how the exact naming is for english KDE.

Erzwingen is probably force in english.

[Ameb]

What works most of the time for me now, apart from the situation where a popup opens the very first time after the application itself has been started, is the following setting in KDE (sorry it's german, but it should be clear from the symbols):

Exakte Übersteinstimmung means exact match.

Aktivierung zulassen is translated with allow activation (probably), but I don't know how the exact naming is for english KDE.

Erzwingen is probably force in english.

Thank you! It helped me. Here is an english screenshot.

1. Go to (KDE) System Settings > Apps & Windows > Windows Management > Window Rules
2. Add New Rule
3. You can use the "Detect Window Properties" to identify the window class, or add fusion360.exe manually.
4. The setting that does the trick is Accept focus to Force

[Ameb]

Your message is mostly clear, but there are a few minor grammar and clarity improvements that could be made. Here's a revised version:

As @sebadob mentioned, there are still some places where keyboard input doesn't work. For example, when adjusting the tamper angle for an extrusion, the keyboard input is unresponsive. The issue affects mostly floating windows, but I found a workaround: by docking the floating window to the side and then reopening the feature (you can press ESC to close the floating window now docked but still bugged) by right-clicking on the timeline and selecting "Edit Feature."

Additionally, the floating windows are cut off for me:

However, if I dock the window and reopen it, I'm able to see all the properties: