Here is a screenshot of what my workspace looks like.
Here is a screenshot of what my workspace looks like.
Hi Roger,
Are you still having this problem? It looks like not only are those shortcut toolbars improperly showing on the screen, but the Flyout FeatureManager tree is also showing when it shouldn't be (that should only show when in a command that uses the PropertyManager). If you are still having the problem, try exiting out of SOLIDWORKS and restarting. If, after that, you are still having the problem, try rebooting the machine. If you are still having the problem after that, please post back and I'll try to troubleshoot further.
Thanks,
Jim
Jim,
Thanks, but I tried all of that plus uninstalling and reinstalling SW2106.
I am working with the reseller to solve the issue with no luck so far, so any information would be helpful.
Thanks
Hi Roger,
Here is something to try:
1) Make sure SOLIDWORKS is not running.
2) Go to Start, and in the search field type in regedit and run regedit.exe.
3) Navigate to HKEY_CURRENT_USER, Software, SOLIDWORKS, SOLIDWORKS 2016 in the tree on the left.
4) Right mouse select on "User Interface" in the tree under SOLIDWORKS 2016 and choose Rename and rename it to "User Interface OLD".
5) Right mouse select on "User Interface OLD" in the tree and choose Export and save the file as UserInterfaceOld.reg in some folder.
Now restart SOLIDWORKS and see if gone. You will lose your interface customization, but hopefully the problem should be gone. Post back and let me know the results and also attach the "UserInterfaceOld.reg" file so we can take a look at it. To attach files, you have to select "Use Advanced Editor" in the upper right corner and then Attach is in the lower right corner after you do that.
Thanks,
Jim
Thanks Jim. This is ultimately what we did.
Working with Nick at CADDEDGE, he was able to help me clean out a lot of deadwood from previous installs and got everythign straightened out.
Appreciate the help.
Thanks
Roger
Hi Roger,
Do you happen to have your old registry? I'd really like to investigate the problem to see if we can figure out what was wrong or how it happened so we can try to prevent if from happening to you or others in the future.
Thanks,
Jim
Jim,
Sorry I wish I had thought of that but we cleaned house afterwards.
OK, Thanks Roger. I'm glad you got the problem solved. In the future, if this or something like it occurs, it would be helpful for us to have a copy of the "offending" registry so we can investigate.
Thanks,
Jim
I have just had the same issue with 2017 and had followed basically the same steps as Roger did including reinstalling SW with no success. Changing the registry did the trick. I have attached my old user interface file for you.
Thank you for your assistance.
Hi Jim,
Thanks for the registry. From this, we can understand the symptom of the problem, but unfortunately, not the cause. The good news is we think we can put some code in SOLIDWORKS to detect the symptom and fix the problem in the registry when SOLIDWORKS is started up, and therefore hiding the Shortcut Bars. So, this has been logged as SPR# 1003740 so we can put in the code to fix the symptom.
Because the symptom is that these toolbars are set to be visible in the registry (when they never should be...they should always be set to hidden), I'm guessing that the cause is perhaps SOLIDWORKS crashing when using a Shortcut Bar, when customizing a Shortcut Bar, or perhaps crashing in a session after Customizing the Shortcut Bars. I'm guessing this since that is the only time these toolbars would be set to visible and perhaps a crash causes the visibility not to be set back to invisible when the information is stored in the registry.
Again, we hope to solve the symptom with this SPR so if you want to get notified when the fix is made, please ask your reseller to log your name against the SPR. And, if you perhaps come across a reproducible case of something happening in a session and the toolbars being stuck on the screen after that, please post it here so we can then fix the cause and not just the symptom.
Thanks,
Jim
Hi Guys,
We put a fix into SOLIDWORKS 2017 SP03 that should eliminate this bad behavior, even though we don't know the exact cause of it.
Thanks,
Jim
Hello Jim,
I have only recently started using the S key, and have this same problem, on sw 2015 though.
I've tried all of your suggestions.
Restart program
Restart machine
Regedit...and then restart. I renamed the entry for sw 2015 though.
I still have the shortcuts appearing, but only when I'm in a part file, when I'm in an assembly file, it behaves as expected.
Any suggestions?
thanks Nathan
Hi Nathan,
I'm afraid I'm not sure what to suggest. If you have reset the registry, it should clear out the problem if it is the same problem that we have identified. If this does not work, I would suggest contacting your reseller to help troubleshoot.
Thanks,
Jim
Jim Wilkinson wrote:
Hi Jim,
Thanks for the registry. From this, we can understand the symptom of the problem, but unfortunately, not the cause. The good news is we think we can put some code in SOLIDWORKS to detect the symptom and fix the problem in the registry when SOLIDWORKS is started up, and therefore hiding the Shortcut Bars. So, this has been logged as SPR# 1003740 so we can put in the code to fix the symptom.
Because the symptom is that these toolbars are set to be visible in the registry (when they never should be...they should always be set to hidden), I'm guessing that the cause is perhaps SOLIDWORKS crashing when using a Shortcut Bar, when customizing a Shortcut Bar, or perhaps crashing in a session after Customizing the Shortcut Bars. I'm guessing this since that is the only time these toolbars would be set to visible and perhaps a crash causes the visibility not to be set back to invisible when the information is stored in the registry.
Again, we hope to solve the symptom with this SPR so if you want to get notified when the fix is made, please ask your reseller to log your name against the SPR. And, if you perhaps come across a reproducible case of something happening in a session and the toolbars being stuck on the screen after that, please post it here so we can then fix the cause and not just the symptom.
Thanks,
Jim
Hi Jim, I am wondering if this is related to the issue that I see once in a while, in which the "S" toolbars reset their sizing.
Example:
The way I want it:
The way it comes after a crash (sometimes):
Only happens after a crash, and I can go in a fix it immediately and it stays until the next crash.
I am just wondering if these might be related in any way.
Hi Dan,
Related only in that with the crash, the registry may be getting incomplete data recorded for the definition of the toolbar. The toolbar sizing may not be being written to the registry when it crashes and then it may go back to the default layout. Unfortunately, we likely don't have control over when this data gets written to the registry since we use built in Microsoft functionality for a lot of the toolbar code/functionality.
Thanks,
Jim
Hi Jim,
Thanks for the registry. From this, we can understand the symptom of the problem, but unfortunately, not the cause. The good news is we think we can put some code in SOLIDWORKS to detect the symptom and fix the problem in the registry when SOLIDWORKS is started up, and therefore hiding the Shortcut Bars. So, this has been logged as SPR# 1003740 so we can put in the code to fix the symptom.
Because the symptom is that these toolbars are set to be visible in the registry (when they never should be...they should always be set to hidden), I'm guessing that the cause is perhaps SOLIDWORKS crashing when using a Shortcut Bar, when customizing a Shortcut Bar, or perhaps crashing in a session after Customizing the Shortcut Bars. I'm guessing this since that is the only time these toolbars would be set to visible and perhaps a crash causes the visibility not to be set back to invisible when the information is stored in the registry.
Again, we hope to solve the symptom with this SPR so if you want to get notified when the fix is made, please ask your reseller to log your name against the SPR. And, if you perhaps come across a reproducible case of something happening in a session and the toolbars being stuck on the screen after that, please post it here so we can then fix the cause and not just the symptom.
Thanks,
Jim