keep dragging the bar back to the top and if you close out the program without it crashing it may recall the setting. my best guess.
I tried dragging the bar to the top, saving and closing.
When I re-open SW the bar appears at the very bottom of the CommandManager (not at the top where I had dragged it to pre-closing).
Tried a few times, same thing. Thanks though!
While in your feature manager view, drag the bar to the bottom before using Copy With Mates.
When I start SW the bar is already at the bottom. I tried dragging it up, then dragging it back to the bottom, before starting "Copy with Mates". Unfortunately the CommandManager was still split.
I have attached a video showing what I mean. Thanks for your reply!
sldrx.wmv 765.4 KB
copy with mates does not split my feature tree. it puts the copy with mates property manager in the property manager tab like it is supposed to. I did not find a setting for this, except maybe one of these two (which I can't try out). also, I am not able to manually split the feature manager.
The way it should work is if the splitter is at the top or bottom, the PropertyManager should take over the entire vertical space, completely hiding the FeatureManager tree. If the splitter is in the middle, there are two possible behaviors:
- If "Auto-size PropertyManager when panels are split" is ON, the PropertyManager will show in the bottom pane and move the splitter while the command is running to show the contents of the PropertyManager.
- If "Auto-size PropertyManager when panels are split" is OFF, the PropertyManager will show in the bottom pane and not move the splitter at all.
So it looks like you are getting behavior #1 even if your splitter is at the top or bottom which is not correct behavior.
Does this only happen on this assembly? If you open a new assembly file (with no components in it) and then run the Copy with Mates command, does the same thing happen? If so, where is the splitter bar on the new assembly?
If not, try one more thing; on the assembly that is giving you trouble, double click the splitter bar. This should automatically put it all the way at the top. Then try Copy with Mates. Does the same problem occur? If so, does the same problem occur with other commands like Insert Components or Mates?
Report back on what you find.
Thanks for taking the time to reply.
Currently, "Auto-size PropertyManager when panels are split" is on.
I tried a new assembly as you indicated. The splitter bar appears at the bottom. When I click "Copy with Mates" from ribbon, the dialog appears correctly in the top pane of the CommandManager.
When I went back to my working assembly (splitter also at bottom), I tried "Copy with Mates" from the ribbon and it works correctly as well! This is very interesting.
I didn't think to include this in my original post, but I usually invoke "Copy with Mates" by RMB on either the part itself, or on a part in the tree. It's only when I invoke "Copy with Mates" by RMB that the issue I'm seeing occurs.
If I double-click the splitter bar (or move it to the top), "Copy with mates" by RMB works correctly.
Next I tried turning "Auto-size PropertyManager when panels are split" OFF.
With the splitter bar at the bottom, I tried "Copy with Mates" by RMB again. The screen changes such that "Copy with Mates" is active, but the dialog is not visible because it appears on the lower pane, which is hidden/isn't auto-sized now.
"Insert Component" and "Mate" from the ribbon work correctly. "Mate" by RMB a part works the same as "Copy with Mates" by RMB above.
I went back and tried to see if I got the same results since I really don't use copy with mates...im old school enough and just insert components and try and use the smart mates set up in parts to put in my components. It is annoying to have to drag the bar all the time....send in a tech support ticket to your var. maybe they can tell you where the setting is and or report the bug if you really found one.
We were very disappointed with our VAR over the last year, and are not going to be renewing our support contract with them.
Do bug reports need to go through a VAR, or is there a way to report directly?