Here is a bug for ya if I activate one component then turn the light bulbs of for the rest of the components, then move the time line do what's needed then move the timeline back every other component disappears, If I do a couple of undo's it comes back doing the same action again same thing.
File Attached just open it and move the timeline like the screencast shows
Solved! Go to Solution.
Solved by jeff_strater. Go to Solution.
Yep, that's a bug all right. Thanks for the video and the file. Makes it easy to reproduce, and therefore should make it easier to fix.
Jeff
Oh, now I understand what is going on... And, technically, it is not a bug, but it is confusing (clearly it had me fooled, and I've seen this before). I should not reply to forum posts before coffee.
This is a bit more complex than I first realized. It has to do with the fact that the timeline is filtered when a component is active. Your full timeline looks like this:
However, when you activate the "bottom" component, your timeline is filtered down to this:
All the features that create the other components are hidden. They are still there, but just not shown. You can disable this using the "hide inactive features" command in the timeline:
But, in filtered mode, we only show features for the active component. Then, when you drag the end of design marker to before "R-Pattern 1", you are dragging past a whole bunch of features for the other components. So far so good. Now, when you drag it back to the right, you are really just dragging the marker to just after "R-Pattern 2", not to the very end. At this point in your video, if you turn on inactive features, it actually looks like this:
and that is why the other component are not shown in the browser: They are still rolled out. If you either show inactive features, or activate the root component, and roll to the end, everything is just fine.
This is a discussion we've had several times: What does moving the end of design marker mean when a component is active? For now, we've decided that you can only move it to features that are currently visible in the timeline. We have discussed what should happen if you hit the "move to end" button. Should that, also, be restricted to visible features, or should it move to "the real end" of the design? For now, that is also only for visible features.
Jeff
Clear as mud Thanks @jeff_strater
Yep that was it I will blame it on a long week (bad), That be why I have done it only twice s that way.