Components vs. groups
-
I am trying to create a model environment for kids (they are between 9 and 11 years old). It should work like building with bricks (e.g. TinkerCad).
AFAIK it works as long as the kids do not modify the components. If they only place them on the workplane and scale them, everything is OK. Is there a way that they get always groups?Any ideas?
Regards, Kurt -
You would need to make groups instead of components from the beginning but then they would have to be present in the model space and not in some library. If you import a SKP file of a group, it comes in as a component. Also, if the student inadvertently deletes a group it's gone unless there's another copy of it elsewhere in the model.
It would be better to teach them about how editing one component edits all other copies in the model and the Make Unique command. Components have so many positives to recommend them over groups and a little instruction can overcome the problem you're running into.
-
In any case, you can save these components as separate files and reload them if the kids have modified them. In fact, if you build up more complex components (that contain sublevel components nested), you should do this from the beginning and collapse the sublevel components so that they can only see/import the top level ones.
See some further explanation here: http://sketchucation.com/resources/tutorials/36-intermediate/115-internal-external-components
-
@enhydra said:
I am trying to create a model environment for kids (they are between 9 and 11 years old). It should work like building with bricks (e.g. TinkerCad).
AFAIK it works as long as the kids do not modify the components. If they only place them on the workplane and scale them, everything is OK. Is there a way that they get always groups?
..You could build components, simple blocks, say length A, 2xA, 3xA and 5xA (just as an example).
These components are in the 'In Model' library.
Place each component in modeling space and assign layer 1 to them.
Group them together and assign layer 2 to them.
Now enter the group, select all components and lock them
Leave the groups environment and lock the group.
Hide both layer 1 and layer 2.The modeling space seems empty but holds all components locked two levels deep.
Even the 'Outliner' does not show the components on hidden layers.
(If they are smart, the kids will eventually find them!)Your kids can apply each component from the 'In Model' library. They can even scale them etc.
But each time the try to enter them for editing, they will get a warning. Making them curious. But unless they find them (hide them even more levels deep if you want)they cannot edit the components.
It's worth a try. -
Thanks for your replies.
@Dave R
@unknownuser said:
It would be better to teach them about how editing one component edits all other copies in the model
You are right, it's probably the way I should choose.
@unknownuser said:
In fact, if you build up more complex components
I think the pupils are fine with "simple" components. See also the SKP-File below.
@unknownuser said:
They can even scale them etc. But each time the try to enter them for editing, they will get a warning.
A very interessting approach.
I will keep that in mind and run a test.After I wrote the initial entry here I created a "brick builder workplane". The primitivs (groups)are placed on a "sidebar". Each group can be pulled from there 10 times.
Advertisement