The same QAction is often reachable through multiple GUI clients; those are true duplicates and are now collapsed by pointer identity. Distinct actions that merely share a visible label (common across plugins) are kept but disambiguated by appending the owning component's display name, and every entry is assigned a unique, stable id so activating a row always triggers the intended action rather than whichever one won a hash key. |
||
|---|---|---|
| .. | ||
| PLAN.md | ||