Support and General Use > Theming and Appearance Customization

Album Art in status bar?

<< < (5/5)

AlexP:
It means in the latest current build.  We don't release simulators as a project, and I don't know how often people that do update them.

Avalon:
I gave the following a try using r28212-101005:

#User Information viewports
%?cs<%VI(g)|%VI(g)|%VI(h)|%VI(i)|%VI(g)>
#
# USER INFORMATION PANELS
#
%Vi(g,1,17,219,110,1)

%Vi(h,1,30,219,97,1)

%Vi(i,1,17,130,80,1)

next line

This does not create any errors, but %Vi(g,1,17,219,110,1) appears to be used for all screens including the FM and RECORDING screens. 

It does partially work....when you hold down the select button while in the RECORDING screen, the displayed list screen uses %Vi(h,1,30,219,97,1).  Likewise, when you hold down the select button while in the FM screen, the displayed list screen uses %Vi(i,1,17,130,80,1).

I tried deleting the blank lines between the Vi lines and the Fuze crashed with a white screen on reboot (off/on).  The only way I could restart was to boot into SANSA OS, undo the changes and reboot into RB.

Just out of curiosity, I tried the above on the simulator for the same release date.  I got the same results, except the simulator just fails and blinks off when the blank lines are used.  Since the simulator works for this, it should be easy to check any changes.

I hope that this helps.

ew:
If somebody figures out how to do this, it would be appreciated if the solution could be posted to the forum.  I also tried a series of if statements as in:


--- Quote ---%?if(%cs,=,1)<%VI(regport)>
%?if(%cs,=,2)<%VI(regport)>
%?if(%cs,=,3)<%VI(regport)>
%?if(%cs,=,4)<%VI(regport)>
%?if(%cs,=,5)<%VI(plport)>
--- End quote ---

That did not work either (all screens wound up using the first viewport).

Thanks,

Avalon:
I am glad that someone has confirmed my findings.

I have retested the code provided in my last post with simulator build
r28296-101016 and found a curious result in the RECORDING screen.

When first accessing the RECORDING screen, the first VI definition, %Vi(g,1,17,219,110,1), is used for the viewport.

When I hold down the select and get the menu, it does use the 2nd VI definition, %Vi(h,1,30,219,97,1).

When I then go back to the RECORDING screen the 2nd VI definition, %Vi(h,1,30,219,97,1), is now used for this screen as well.

It looks like the main RECORDING screen does not check the VI definition on initial display but does when toggling between list menus.  The FM screen always displays a full screen width frequency bar independent of VI definition but does use the VI definition (less then full screen width) for message display such as "No settings found. Autoscan?".

It looks like the code is there but is in an incorrect sequence or using an incorrect conditional.  The use of conditional VI definitions was probably not anticipated when the code was written for the RECORDING and FM screens.

I hope that this helps.  If this can be corrected, it will provide much more flexibility for displaying additional information on the default RECORDING and FM screens.

Navigation

[0] Message Index

[*] Previous page