I generate sequences procedurally and then I chain them or encapsulate them (put one into another), sometimes I generate a sequence that is empty or has just small interval inside itself.
What I have encountered is that if I have sequence that is very short and I put it into some other sequence, it couses the other (outer) sequence to stuck at the moment it should execute the inner sequence.
var inner = DOTween.Sequence().AppendInterval(0.1f);
var outer = DOTween.Sequence() ... (other tweens) .Append(inner);
Note: I'm not anyhow developing this code, I'm just interested in it being reliable.
I would personally add some warning or something about puting an empty sequence into a sequence, because as someone has stated in the #40 it took me quite a time to debug and find out what is the problam (I has an empty array from which I was constructing the sequence)
The solution I have applied is that I'm checking if the lists I'm constructing sequences from is empty and if it is, I return null instead of empty sequence (or sequence with short interval).
@Malhavok But overall I'm using DOTween on almost all my projects and this is the first time I have runned into an issue so I would say it's pretty reliable and I would recommend using it.
Ahoy!
I just added a note marked as important on the docs, to say that empty Sequences are no good.
About the rest, I'll have to investigate (next week). Sorry for the issue!
Any news on this ?
This is party stopper for us.
Yea It would be nice to have appends / prepends and so on to ignore empty sequences or the execution of the tween to ignore them because I'm able to work around it but I have code full of ifs that checks whenever something was added to the sequence and appending it only if was which makes my code much more messy.
Most helpful comment
Note: I'm not anyhow developing this code, I'm just interested in it being reliable.