Album Art in status bar?

[Avalon]

I have no problem with the WPS viewport definitions and user information area on the WPS.

I was trying to set multiple Vi viewport sizes for the RockBox SBS information;  menus, FM standard info and Recording standard info.

On the menu and list SBS screens, I would like as much space as possible for the menus and lists.

On the FM screen, the standard information is small, so I would like to reduce the Vi size for the FM screen to allow for more information display via the theme.

On the Recording screen, the standard information fills the screen.  I would like to reduce the size by a couple of text lines to display more of the recording settings via the theme.

So, by using the Vi and VI instructions conditionally based on which screen was active (%?cs), I was attempting to adjust the viewport used for RockBox standard info display to allow more room for theme based info.
- Menus and lists: as large as possible
- FM: much smaller to fit the standard info
- Recording: a couple of lines smaller to allow display of some setting information

The theme info would then change in content and size dependent on screen as well.  That I have done before.

The problem I have is that I have to define multiple viewports for the same screen locations (different screens).  It seems that I can do this with normal viewports but the Vi/VI combination doesn't operate as expected.  In the last example I gave, the simulator does not indicate any errors, but does not display Vi/VI as defined for the FM and Recording screens.  Only 1 Vi/VI viewport for RockBox standard info display appears to be used for all SBS screens.

If this worked as I had expected, it would be a nice feature.  It would offer theme developers the ability to change theme content dependent on screen using existing conditionals.

If there is a way to control the Rockbox standard menu/list viewport size and location independently for each screen, I would appreciate a description.

Thanks again.

[JdGordon]

What you are doing is correct and should work. Maybe there is a problem with %cs... ill try and look into it tonight maybe

[Avalon]

Thank you very much for the effort.

I will look forward to your findings.

Cheers!

[JdGordon]

for some unknown reason you need to add a blank line between the Vi lines

This is hopefully fixed now... please let me know if they still refuse to load without an empty line between them. (havnt looked into %cs yet though)

[Avalon]

When you say that it is fixed, does that mean in the daily release and in the latest simulator release?

[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:

%?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)>

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.