Support and General Use > Theming and Appearance Customization
new theme (kinda): retroTape
vash:
--- Quote from: audio-i on July 01, 2010, 12:03:03 AM ---
--- Quote from: vash on June 30, 2010, 10:10:18 AM ---I'd really appreciate, if u write same stuff for replacing counter with a clock, so I could change it in my wps. Big tnx.
--- End quote ---
That's actually a very easy change ;), you'd just have to change the current track time tag for the clock time tags in the retroTape.wps file, find the comment "Song Time" there. For more information about the tags you might want to use see http://www.rockbox.org/wiki/CustomWPS
--- End quote ---
I tried once to do that change before posting, but that gave me nothing :[ I suppose I shoud've been using some other font or so. Ok. Will try again and if'll become in any troubles with that issue let u know.
Song time is problematic for viewing content in hh:mm:ss format (cued albs, radio podcast, huge audio books etc) - there is no enough space for additional 2 hour digitis.
Tnx anyway!
ps UPDATE --> Taking 2 minutes to do all that stuff. Working like a charm!
Here's the code, in case someone need it
--- Quote ---# Song Time replaced with time
%V|268|13|36|13|2|FFFFFF|000000|
%ar%ck:%cM
--- End quote ---
Pretty much like that stuff -->
%cI hour (01..12) - (that's a c and an uppercase i)
%cl hour (1..12) - (and this is a c and a lowercase L)
:D
audio-i:
I was hoping to find a workaround for the bug that makes the wheels movement look really bad since some time ago on recent builds (bug is FS#11629, %t not working well when used as argument inside %?mp), so instead of using %t according to the playing status in %?mp, in a viewport for each wheel, I defined 4 viewports for each wheel (1 for each playing status except stop), each containing the correspondent image displaying order and timing, and made %?mp display the according viewport.
Code for 320x240 was
--- Code: ---# Left Wheel
%xl(W,wheel.bmp,0,0,3)
%V(65,64,28,28,-)
%?mp<|%t(0.2)%xd(Wa)|%t(0.1)%xd(Wc)|%t(0.1)%xd(Wa)|%t(0.1)%xd(Wc)>;
%?mp<|%t(0.2)%xd(Wb)|%t(0.1)%xd(Wc)|%t(0.1)%xd(Wb)|%t(0.1)%xd(Wb)>;
%?mp<|%t(0.2)%xd(Wc)|%t(0.1)%xd(Wc)|%t(0.1)%xd(Wc)|%t(0.1)%xd(Wa)>
--- End code ---
changed it to
--- Code: ---# Left Wheel
%xl(W,wheel.bmp,0,0,3)
%?mp<|%Vd(p)|%Vd(pause)|%Vd(f)|%Vd(r)>
%Vl(p,65,64,28,28,-)
%t(0.2)%xd(Wa);%t(0.2)%xd(Wb);%t(0.2)%xd(Wc)
%Vl(pause,65,64,28,28,-)
%xd(Wb)
%Vl(f,65,64,28,28,-)
%t(0.1)%xd(Wa);%t(0.1)%xd(Wb);%t(0.1)%xd(Wc)
%Vl(r,65,64,28,28,-)
%t(0.1)%xd(Wc);%t(0.1)%xd(Wb);%t(0.1)%xd(Wa)
--- End code ---
Strange thing is, it did work fine for the left wheel, but it didn't work for the right wheel, which is shown static, unless REW is pressed, and from then on it stays in the REW viewport %Vd(r) regardless of the playing status. As if it couldn't handle two %?mp that have to display images using %t in the same wps.
Any ideas?
EDIT
It seems the wps parser was being a little bit temperamental, but after changing a couple things, it seems to like the workaround for now, so both wheels seem to be working. Below is the 320x240 version for those interested, please let me know if any problems come up.
(retrotape-sbs.txt has to be renamed to retroTape.sbs)
JdGordon:
%t issues are hopefully all fixed now... let me know if there is any more wierdness
audio-i:
--- Quote from: JdGordon on October 10, 2010, 02:49:23 AM ---%t issues are hopefully all fixed now... let me know if there is any more wierdness
--- End quote ---
Seems to be working great! ;)
Interesting the info you provided about the FPS in SBS and WPS (http://svn.rockbox.org/viewvc.cgi?view=rev;revision=28226). If I'm getting it right, in a WPS with peakmeters enabled (by the way, which would be the FPS without peakmeters?), the screen updates every 0.04 seconds, but as far as I know the %t() tag allows only a minimum of 0.1 sec, and 0.1 sec steps... in this theme, if FFW and REW would "look faster", with say %t(0.04) instead of %t(0.1), it would be great... just in case this can be considered in the future.
JdGordon:
without peakmeters I think its 5 or 10 FPS. I've thought about adding either some clever logic to work out the required update speed, or add a tag to specify the speed, but (obviously) that hasnt happened yet
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version