Support and General Use > Theming and Appearance Customization
Scrolling in Conditional Viewports?
pwhodges:
That's alternating eight images as a volume indication, which change when paused to give a rotating pause symbol (it's taken from the pre-viewport version of icatcher/unicatcher). I will try losing it as a test.
Note what I said before about the conditional being the only change - if I change the "b" viewport to non-conditional and remove it from the condition that selects it, but make no other change, then the scrolling works in that viewport (and if the hold switch is selected in this version, the other viewport tries to display on top of it - which the re-writes of the scrolling viewport mess up amusingly!).
In other words, the non-scrolling is specific to conditional viewports.
Paul
EDIT:
I removed the lines starting %t0.1 and %t0.5 with no change in the scrolling behaviour. - Paul
LATER EDIT:
Incidentally, this use of viewports was intended to get over a different failure. I had previously tried:
--- Code: ---%?mh<%t0|%s%ac%fn>;%?mh<%s%ac%?in<%in - |>%?it<%it|(no track name)>|%t0>
--- End code ---
to display different lines according to the switch position - however, even though an earlier test successfully changes a "hold" icon whenever the switch is changed, this line only reflects the changing switch position for a couple of seconds after the start of a song - after that the line stays the same regardless. But it does scroll...
MrMEC:
I've also seen that scrolling causes problems in conditional viewports.
Take the following example - this code works fine and the info scrolls correctly:
--- Code: ---%Vl|x|60|90|202|60|1|FFFFFF|000000|
%ac%s%?ia<%ia|%?d2<%d2|>>
%ac%s%?it<%it|%fn>
%ac%s%?id<%id|%?d1<%d1|>>%?iy< (%iy)|>
--- End code ---
But take this code and place it in a conditional (to show next track info when hold is on), and the text still scrolls, BUT the next track info does not display when the hold switch is on:
--- Code: ---%?mh<%ac%s%?Fn<* Next *|>|%ac%s%?ia<%ia|%?d2<%d2|>>>
%?mh<%ac%s%?Ia<%Ia|%t0>|%ac%s%?it<%it|%fn>>
%?mh<%ac%s%?It<%It|%Fn>|%ac%s%?id<%id|%?d1<%d1|>>%?iy< (%iy)|>>
--- End code ---
Take the scroll tags out, and the info changes on hold, but of course it doesn't scroll:
--- Code: ---%?mh<%ac%?Fn<* Next *|>|%ac%?ia<%ia|%?d2<%d2|>>>
%?mh<%ac%?Ia<%Ia|%t0>|%ac%?it<%it|%fn>>
%?mh<%ac%?It<%It|%Fn>|%ac%?id<%id|%?d1<%d1|>>%?iy< (%iy)|>>
--- End code ---
So because of this I'm forced to either remove the scrolling or the conditional.
knight4led:
Why not have the hold switch check outside the viewport? I mean define two seperate viewports and display them depending on if the hold switch is on or not? It seems that the problem is with scrolling things contained in conditionals inside of conditional viewports. Seems silly to check conditionals inside of an already conditional viewport.
afruff23:
--- Quote from: knight4led on August 16, 2008, 01:06:40 AM ---Why not have the hold switch check outside the viewport? I mean define two seperate viewports and display them depending on if the hold switch is on or not? It seems that the problem is with scrolling things contained in conditionals inside of conditional viewports. Seems silly to check conditionals inside of an already conditional viewport.
--- End quote ---
Yep, that's what I do. Works a lot better (shorter and cleaner code). If you want to see a sample, check out my "Next" theme for the gigabeat.
pwhodges:
That's what I was trying to do - use the hold switch test to choose which viewport to display. However, I am still following the usual convention of testing to see if a tag is available before displaying it, and this test is on the line in the viewport, of course - I guess I could remove that sanity check and see if it works without...
Paul
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version