Reloading Components
-
Has the option to reload components been put into the bit dust bin?
-
Right click/reload.
-
I tried that but there is no Reload option.
-
You have multiple selections there, it won't give you the reload option with a mix of components.
-
There are all grouped as a single component.
-
Yes, but you have it open for editing, so it's looking inside and finding several different things to choose from.
Right click on the component when it is closed and I'm pretty sure you'll get the reload option. -
Sorry to write that the option still does not appear. If it does still exist should it not at least be visible but greyed out, as the Explode command is?
-
You are still not right clicking on a closed component.
-
Then I don't understand what you mean by closed. The component is not in editing mode. All I did was to select all faces and edges.
-
If you are able to select all edges and faces like that, then it is either open for editing, or it isn't a component.
Since the option in the context menu for make component is available, it suggest that it isn't a component and therefore how can it be reloaded. -
@se7ven said:
All I did was to select all faces and edges.
Right there you confirm you aren't selecting a component. You are selecting faces and edges. That's not a component.
If you had selected a component it would look like this:
-
-
Hmmm, now I am truly perplexed. I am uploading the file. Perhaps either one of you can further explain to me what is happening.
-
What's happening is the only components you have in the whole darn model s[ace are the letters in the word, "GOOGLE" Everything else is loose, ungrouped/uncomponented geometry. That shouldn't be so hard to figure out.
There are no components in your selection to reload so of course Reload won't show in the Context menu.
As with a problem you were having before, you've started out trying to learn advanced things without having bothered to learn the basics. It's come back to bite you again.
-
Dave is a true master here, so I'll bow out and let him take over.
-
Very well. I see that something must have gone amiss as I was following an exercise. Will have to retrace my steps to see where I went wrong.
As a side question, does Xref Manager do the same thing as Reload?
-
You are trying to learn the basics here
Please forget Xref Manager for now... it does reload external SKP files into the current Model, listing any that have changed since they were last reloaded etc...
BUT using Reload from the context-menu reloads external SKP [Components] too [just no check to see if it has changed and therefore needs to be reloaded]
IF you have a SKP that is used as a Component within another Model, and you know that the SKP has changed then Selecting an Instance of that Component within the Model and using Reload will update it to match...So for example you do housing developments and have 6 commonly used house types.
You make 6 separate components as individual SKP files, these are stored in a 'Library' of your house-types.
You a SKP Model for a Site A.
You load and place the houses onto the Site A as desired.
You repeat this for another Site [B] as well.
Later on you decide to change something about the style of some of your standard house types... so you edit their individual SKP files and save...
At this point the equivalent house components in your Sites' Models are 'out of date'.
But perhaps you want to leave those on Site A in the old-style - maybe they are getting built like that already !
But you'd like to use the newest version of the houses on Site B... Simply open the Site B Model and select one of the houses you'd like updating, and right-click context menu 'Reload' - the Instances of that house are now updated to be the newer one.
If you save the changes Site B now uses the newer houses...
Of course if you have [ill-advisedly] Exploded an Instance in the Site Model it is now loose geometry and cannot be reloaded !
Also if you edit a house component in the Site Model it is now going down a separate path from its original SKP in your Library... Although if you want to revert to the original Library you can Reload that back in, overwriting any Site specific changes...
OR if the changes are such that'd you'd like to include them in your 'standard' one, then you can do a context-menu 'Save_as' the changed version - either saving as anew version or overwriting the original Library version - thereby allowing you to use these SKPs in other Site Models as desired...
Advertisement