When I had a similar approach to do, I used Basic Conveyor. The first conveyor with the continuous flow was just animation. I created my own events using messages to animate the flow which was just drawing a cube in the OnDraw-Trigger, similar as you do in your model. I needed to also put some code for breakdowns in the object, which I did again with messages to have events for the animation.
In your model because of using the item for the animation of the cube breakdowns are taken care off. The downside on your idea is in my eyes, that the first item leaves the animation jumps to the next item. In my model the flow starts in the beginning of the simulation and if the conveyor is filled up the animation just shows a full conveyor, beside if breakdowns happen on the previous conveyor.
Later on in my model the continuous flow became a discrete flow, where I used a Basic Conveyor again and created items depending on the state of the previous continuous flow conveyor.
In general I guess your idea goes in the same direction. It depends what else happens in your model to do the right animation and events. I like your idea of using an item for the drawing of the cube and if the cube should stay, you could just put another cube in the OnDraw which is shown when the first item left the conveyor.
__________________
tom the (A)tom: "We have solved our problems ... now we have to fight the solutions."
|
