Conditionals with timings

[AsusFreak]

JdGordon,
I saw you released r27956 to solve this problem (?). I tried it with my AF_Black theme and still have the same problem. I used the following line to get something like an Onscreen Menu disappearing after 2 seconds:

Code: [Select]

%?St(touchscreen mode)<%?Tl(2)<%Vd(j)|%Vd(k)>|%Vd(k)>

It does disappear but the refresh of the rest does not work and I pointed out that because of the timing in the conditional I never get back to the redrawing Viewport - only by re-pressing the screen the conditional works right again because it starts at a defined status.

I tested this with an old release r27530 and everything's working fine.

@ew:
Please name the bug number here, then I will add my part.

[JdGordon]

read the thread, that commit didnt actually fix this issue, and that line has no timeout tags in which means means it is a ocmpletly different issue

[ew]

FS#11588 filed (http://www.rockbox.org/tracker/task/11588) for this item.

Thanks,

EW

[AsusFreak]

read the thread, that commit didnt actually fix this issue, and that line has no timeout tags in which means means it is a ocmpletly different issue

Completely different? Conditional with a timeout. It might be a different tag but for me as user (with less coding skills than you) I understood it as a possible identical issue. If I'm wrong I'm sorry.

If you put a number straight after %Tl it will be used as a timeout in seconds (e.g %Tl2.5 will give a 2.5s timeout) between the touchscreen press being released and the tag going false. If no number is specified it will use a 1 second timeout. Can also be used as a conditional, and can be used with conditional viewports for some really neat effects.

[JdGordon]

different tag, completly different issue

[AsusFreak]

Ok, than I AM sorry.

[ew]

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

[ew]

Been out of touch for a little while, but I am able to confirm that as of build 28235, the issue seems to be fixed.  Perhaps it was fixed in 28226, or some other build, nonetheless it seems to be working now.

Thank you!