Timeline reordering incorrect and impossible. Moves features to beginning instead of desired location.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
This is a bug that has been bothering me for a while. Sometimes we build something out of order and I have to drag timeline elements around to group them up by component. No problem....
Except when I drag something backwards and instead of landing where I put it, the features end up at the very beginning of the timeline. These features are now at the beginning of the timeline meaning there are extrudes and fillets, etc. "happening" before the sketches or even components they operate on were created. Normally it is impossible to move a feature before something it is dependent on, but in this bug the features are always teleporting ahead of the component even existing. Very clearly buggy behavior.
This is usually reproducible though I cant say what causes it directly. I tried to isolate the cause but after a few tries, it worked correctly. Small movements are usually okay but it seems that moving a feature longer distances is what causes them to be dropped in the beginning of the timeline. It has happened on several files, usually ones with a timeline >2x the screen width.
I did capture a picture of the problem. This is a result after the bugged reorder.
You can see on the timeline on the left are two fillets (indicated by the little lines on one fillet) that are operating on the component that was created after the fillets (also indicated by the lines towards the middle of the picture). I moved them to the end/right side of the picture (from far further right/later in the timeline. Not shown in picture) to be after the other features of this component but they were placed in a seemingly random spot way earlier resulting in what you see here. To be clear, this is not an instance of reusing the limited number of colors, all the yellow here is the same exact component.
This causes some significant delays when I have a complex file that has to be recomputed from the beginning several times while I try to get the correct behavior.