Why Are Commands Treated Differently in AutoCAD’s CUI Editor? Design Choice or Legacy Debt?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I’ve been exploring AutoCAD’s CUI Editor in detail and ran into something puzzling. Commands seem to live in their own separate section, while other UI components — tabs, panels, workspaces — form a clear hierarchy.
As someone with a background in both software architecture and UX design, this feels like a leftover from earlier internal structures — possibly a form of legacy technical debt?
From a user’s perspective, it adds complexity and inconsistency to customization. From a dev perspective, I wonder if there was a compelling reason to isolate commands rather than treating them as reusable building blocks within the tree — just like panels or tabs.
Is there a deeper technical rationale here? Or has this been kept due to inertia and backward compatibility constraints?
Would love to hear from both power users and Autodesk insiders — and happy to share a deeper write-up I posted elsewhere if helpful.