Does anyone else notice that when you use the "Replace" command in an assembly, that after you click the "check" the window inside of SolidWorks resizes and is not longer maximized?
Yes, I find it quite annoying.
I'm glad it's not just me, but everytime I use the "Replace" command my window flickers big and small. And to add to this, if I'm replacing a "Part" file, my search dialog is set to see "Assembly" files, and if I'm replacing an "Assembly" file, my search dialog is set to "Part" files. It's pretty aggravating also.
Yes in SW2013 SP3.
This still isn't fixed. SW16 SP4.0. Drives me crazy. Nobody has yet to figure out why or how to stop it?
SW16 SP3 here, but this behavior goes back many years as I can tell from forum searches of at least three similar threads. My advice is unadvisable, or at least unhelpful at this point. An even better solution by other is linked at bottom.
You selected Re-attach Mates, and it could not automatically replace all mates. Therefore it opened the Mated Entities pane in the feature manager, which also includes the *Second Window* of the original part as a visual reference of the entity needing replacement in the new part. You may or may not proceed with correcting broken mates, but if you interact in any way with the second window, then the original window will Restore because you have two windows open. After the process and command is complete, the second window closes, and leaves the original window restored, not maximized.
How to stop it:
Design everything so that SW automatically solves all mates in replace component.
Avoid mating to faces. Instead, create reference geometry in every part and name it identically across all similar parts. Then, it replaces one Outlet Seat Plane with 2nd part's Outlet Seat Plane, Y-Axis with Y-Axis, Through Axis with Through Axis, Top Plane with Top Plane, Inlet Face Plane with Inlet Face Plane, Relief Axis with Relief Axis, and so on. To accomplish this, remake every part in your design library so that it is oriented same as every other possible similar part, contains exactly same named reference geometry to completely define it in any and every use, and then stop mating to non-reference geometry. This 'solution' is often unfeasible, but not impossible.
Side note: be aware that when selecting a face and clicking reference Plane, the default relation is distance, not coincident.
You can *prevent* this by creating these reference geometries in every part when adding it to the design library, and then only mating to them in your assemblies. For most users, this is a non-starter issue, as no one learns how to make good design library parts until they learn how they fail in practical use. No one. The lessons show you: see, you can add this part to your design library and use it forever; do eet nao. It doesn't tell you how to conform them all to a useful standard. One benefit of using these geometries for mates is that, unlike faces, they can be selected from the design tree, which is particularly helpful when a face is partially obscured, but a plane shows in the tree. I try to place them all within a REFS folder at the bottom of the tree for each part, so they can be collapsed and don't make every tree automatically longer, although that isn't necessary.
Here's how it's so very unhelpful. In all practical reality, it's too late to redefine every part in your design library as well as every mate ever defined using those parts.
When I get part models from vendors (when they're even available, that is), I have only learned through similar failures to at least orient them similarly compared to other similar types: all valves in this orientation, all tees in this orientation, all flanges in this orientation, etc. Also pay attention to where the origin is, as sometimes they provide it with the part far removed from it. Move it to the origin and orient it while you're at it, with the Move/Copy Bodies command. I prefer constraints to translate/rotate, but sometimes I'll use both in succession if it's easier. Adding conformed references is just as important to a useful library part as completing its custom properties, in my opinion.
Gerald Davis has another great idea regarding this issue, in this 2009 thread. His idea can be implemented incrementally as needed, between parts which you now know need similarities defined, although mine cannot because it relies more on providing entities to mate to for which mates have already been defined. He deserves credit for a better solution because it's retroactively applicable.
Now, after all that, is re-maximizing the window all that bad? I think it's the simplest solution.
yes - SW2016 sp4
I didn't pay much attention since I thought I did some thing
Thx for sharing - is it a bug
Retrieving data ...