Forgive me if I am dense, but I saw that the bug was resolve and a fix was checked in, but I don't see how the problem is solved.
The following are the results of my testing of r27994 (I had to wait for a simulator build).
Again, my wps code is:
%?ic<%s%al%t(6)Composer:|%t(0)>;%?iA<%s%al%t(6)Alb Artist:|%t(0)>;%?ia<%s%al%t(6)Trk Artist:|%t(0)>
%?ic<%s%al%t(6)%ic|%t(0)>;%?iA<%s%al%t(6)%iA|%t(0)>;%?ia<%s%al%t(6)%ia|%t(0)>
I have a track that has an %iA, but no %ia or %ic
As a result of the first line of the wps, I get a short display of "Alb Artist:" with a longer display of a blank line. I would think that there should not be any blank display.
The second line continues to display the contents of the %iA tag - and begins the scroll process about each two seconds. If the tags are blank is the prior tag value not being cleared out?
Additionally, if I changed some (or all) of the %t(6)s on the first line to %t(9)s (changed from 6 seconds to 9 seconds) the synchronization between the first and the second line does not change. Furthermore, each conditional subline seems to be occurring after about 2 seconds, and not the time specified in the %t tag.
Just as another informational point, after the fix, the following sbs line caused a fault in both the player and the simulator
%?bc<%t(0.1)%xd(Ba)|%t(0)>;%?bc<%t(0.1)%xd(Bb)|%t(0)>;%?bc<%t(0.1)%xd(Bc)|%t(0)>;%?bc<%t(0.1)%xd(Bd)|>
In truth, this was a very stupid line, and I was able to change the line, get the same effect, simplify the code and avoid the fault by using the following as a substitute
%?bc<%t(0.1)%xd(Ba);%t(0.1)%xd(Bb);%t(0.1)%xd(Bc);%t(0.1)%xd(Bd)|>
The only reason that I mention this is that you may want to avoid situations where theme code produces a device fault.
I would be glad to do some more testing, but at the current time, my build environment is broken and I have no idea how to fix it (I have another thread on this).
Thanks for all the assistance.
I think It does not appear that the sub-lines that