Post Number: 106
|Posted on Tuesday, September 11, 2012 - 05:50 am: ||
I managed to take an embedded component and make it a new component by not paying attention when copying and pasting from one file to another. In other words, it became a nested component of itself. When I then saw I had two identical components one of which couldn't be purged, I became mightily confused for a while.
Do we actually need nested components? If 'yes', then it would be great to have a pop-up when we create a new component telling us that our new component contains components...
Just a thought.
Post Number: 385
|Posted on Tuesday, September 11, 2012 - 06:37 am: ||
yes, nested components are needed badly ;)
agreed, a sort of warning would be useful, it's an operation which does not happen that often and the consequences of doing this by error could be annoying.
Post Number: 108
|Posted on Tuesday, September 11, 2012 - 07:29 am: ||
Annoying? Luckily the electricity went out so I lost my mornings work and went back to an earlier version, otherwise I'd never have figured it out.
Post Number: 17538
|Posted on Tuesday, September 11, 2012 - 11:25 am: ||
Nested Components are quite useful, but if it would be helpful to have an (optional) warning when creating a component that includes an existing one, it could be possible to do this. We will see if this can be added for the future...