Skip to content

Duplicate toolbars and buttons appearing in the incorrect toolbar #67

@brinkdinges

Description

@brinkdinges

This is an issue that has plagued me/us for years. I have already spent multiple days looking for the issue but I haven't found it yet.

I just received this image, where all our Lightning buttons appear in the DBWorks toolbar.

Image

Interestingly, there are no separators in this image but our Lightning toolbar has separators. Every separator starts a new 'tab box', but in the DBWorks toolbar, all our buttons are in a single box. Strange.

Background info:

  • This doesn't happen consistently at all. Not with every user, not with every DBWorks install.
  • It happens independently for each solidworks version you have installed. The registry also treats every version independently, so that makes sense.
  • We also see lingering and duplicate toolbars. Here are mine:
Image
  • I've also seen Drew buttons appear in the wrong place before:
Image
  • Toolbar info is stored in the Registry, in the key "Computer\HKEY_CURRENT_USER\SOFTWARE\SolidWorks\SOLIDWORKS 2025\User Interface\CommandManager[AssyContext | PartContext | DrwContext]\TabX\GbX
  • I see a Lightning toolbar in my registry where the ModuleName property is set to the Drew GUID. So something does get mixed up already. Does the first started add-in own the toolbar? That's something I could test.

Places we should look

  • CommandManager.GetCommandTab gets a tab by its name and model type. Could we receive the incorrect tab from solidworks here? We could log the actual tab name and see if there is a mismatch between the requested tab name.
  • Can we write our own tab from scratch to relearn the basics?
  • Why does Lightning have a part and drawing toolbar when I has no buttons for those model types?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions