topic Re: Keyboard shortcut for Undo doesn't work when command line has focus in Fusion Electronics Forum

Keyboard shortcut for Undo doesn't work when command line has focus

jaholmes6502 — Sat, 12 Sep 2026 20:17:10 GMT

This might not seem like a big deal most of the time, however if you've got legacy command line focus switched on, it's really frustrating. I'm running Fusion 2705.1.15 on macOS Tahoe 26.5.2. In Eagle, if I entered a command and didn't like the result, I could press Command+Z and the command would be undone. In Fusion, Command+Z doesn't do anything if the command line has focus. Weirdly, all the other keyboard shortcuts seem to work fine, so it's like this was done intentionally. And yes, I know that "undo" is a command, however like probably everybody else, I've been trained for decades that Control+Z or Command+Z is how you undo something, and I can't imagine why it shouldn't work here. Can this be fixed please?

Re: Keyboard shortcut for Undo doesn't work when command line has focus

C.Nicks — Mon, 14 Sep 2026 22:54:34 GMT

I've been having issues with this as well. Strange thing is the REDO keyboard shortcut still works.

This is a pretty serious regression as I almost exclusively have the command line focused.

Re: Keyboard shortcut for Undo doesn't work when command line has focus

obulesub — Tue, 29 Sep 2026 14:35:51 GMT

Hi @jaholmes6502 ,

It looks like another community member has observed the same behavior, but a solution hasn't been identified yet. If you're still experiencing this issue, please let us know whether you've found any additional information or workarounds since your original post, as that may help move the discussion forward.

Re: Keyboard shortcut for Undo doesn't work when command line has focus

nnovotney — Tue, 29 Sep 2026 16:05:25 GMT

If you're still experiencing this issue, please let us know whether you've found any additional information or workarounds

Autodesk programmers can't figure out what the issue is? embarassing

Re: Keyboard shortcut for Undo doesn't work when command line has focus

C.Nicks — Wed, 30 Sep 2026 00:58:47 GMT

@nnovotney They most likely have a bug report and ticket, but these are not things they share here or publically.
Just because they lack that level of transparency does not mean they don't know.

I must say you tend to comment on a lot of topics here with an attitude that does not add to the conversation. I would say I'm equally if not more frustrated with how they've managed Eagle as I have at least 25,000 hours of experience in it and they've completely broken my workflows.
That being said they will be less engaged with the community if all we give them is complaints. Managing large software projects like Fusion is a massive undertaking, and they've managed to get a huge amount of features all (mostly) working well together. Coordinating efforts between so many stakeholders and automating an exponential set of quality checks is also a massive undertaking.

To me they have decent enough programmers and quality control. Where I have issue is the product managers and user experience designers that do not seem to have any Eagle experience or have forgotten where it all came from and why it worked so well. So many features have been half baked and poorly implemented and they do not seem to take any user feedback into account.
I think there needs to be a more transparent approach to involve the users they impact. Things like a public roadmap, a features voting platform, and maybe even publicly visible bug ticket list would go a long way to mending the divide between users and developers.

Let's try to focus on explaining changes we want to see and explaining why along with helping our fellow users find solutions or workarounds.

Re: Keyboard shortcut for Undo doesn't work when command line has focus

nnovotney — Wed, 30 Sep 2026 06:50:54 GMT

@C.NicksI 100% agree with your thoughts, and yes perhaps some comments have been overly harsh. However it seems there is way too much of "thanks for letting us know, we'll ask the developers to take a look, is there anything else we can do for you?" Why are the developers not taking a detailed look in the first place, already??? It's as though they get something working just enough to look like it does xyz, but never check it beyond that for any after effects. Many of the failings are straightforward and easily observed with just a few minutes of trying something out (so I'm not referring to complex obscure or difficult to create errors). Many times it is as though things are simply not logically programmed to cover simple situations. For example, moving a net with a connection dot...hey, ok the dot is moving with it--programming done! But did any programmer bother to think, what if there is another dot along the way that it needs to drag through; guess not, since it fails (now fixed). Why does the document layer keep turning on by itself (this has been reported at least twice, months apart).

and maybe even publicly visible bug ticket list--why shouldn't users be kept in the know about unresolved issues they will face (and any known current workarounds)?? WAY too much "thanks for bringing it up" (again, as rediscovered by another user), "we'll let someone know." That would also make Fusion team appear less asleep at the proverbial QA wheel. No list also makes it very hard to inform what has been fixed.

Re: Keyboard shortcut for Undo doesn't work when command line has focus

C.Nicks — Wed, 30 Sep 2026 18:46:49 GMT

Yes I agree there are a lot of canned responses. Some of them are followup bots and others are responses meant to be polite. They don't really go to solving our problems, but they are trying to be polite and receptive.

Keep in mind primary developers, product/project managers, and QA teams in large companies are typically separated with different processes, manager levels, and directives. Also these days so much of it is driven by AI. With those tools they do/check only what is outlined in the directions and/or requirements. Developers are also most likely pushed to work on the highest impact tasks at a time with little refinement phases. I'm only guessing here as I work for Motorola and there are so many levels of complexity it's a wonder anything works in this world.

My suggestion to you would be to sign up for the Fusion insiders program. That way you could help give feedback on new changes and features while the door is still open to fixing them. It seems once the features ship it's extremely hard to get any suggestions implemented.