thoughts on the colour and backdrop settings

[JdGordon]

since custom statusbar and ui viewport settings went in, the settings controlling the list colours and main backdrop image don't really make sense anymore....
This can be made very obvious when you load a ui viewport which sets the colours.. try changing the colours in the setting and its totally useless. Ditto with the backdrop image (in theory you could load a backdrop in the sbs and a different one with the wps and it should just work.. but it doesnt because %X will load both into the same buffer...)

So, what would be nice is to remove those settings which are meaningless and start forcing use of the ui viewport setting and sbs to do the backdrops....

comment?

[Llorean]

Agreed.

[audio-i]

The change makes all the sense.

So, what would be nice is to remove those settings which are meaningless and start forcing use of the ui viewport setting and sbs to do the backdrops....

But would this mean there would be a backwards incompatibility?

[JdGordon]

backwards incompatability is something we dont care about....

[JdGordon]

also... does this sound correct?

If a WPS doesnt disable the sbs, then its very unlikely it will load its own backdrop and should use the backdrop from the menus?

[[Saint]]

.

If a WPS doesnt disable the sbs, then its very unlikely it will load its own backdrop and should use the backdrop from the menus?

I think regardless as to whether or not an .sbs is loaded, if a background image is loaded for the menu, but not by the WPS, it makes sense for the WPS to use the menu's backdrop by default instead of leaving it blank.

Makes sense to me at least.

Also,

Will this have any effect on using a .cfg to specify colours/backdrop via the:

forground colour:
background colour:
backdrop:

Settings?

What about the current %X WPS Tag? Will that no longer work?

Won't this break any themes/WPS made prior to this change?
I don't use an .sbs nor do I have a UI Viewport setting specified so....just curious.

Perhaps I've missunderstood.



[St.]

[Llorean]

I think the opposite - the WPS should never "inherit" the backdrop from the menus. Instead just require the author to always explicitly define both so that there's never any accidental weirdness when changing themes or whatnot.

Otherwise there's really no way for a WPS author to actually say "no backdrop for the WPS, but I want one for the menus" right?

[[Saint]]

Good call, I hadn't thought of that.

[fml2]

since custom statusbar and ui viewport settings went in, the settings controlling the list colours and main backdrop image don't really make sense anymore....
This can be made very obvious when you load a ui viewport which sets the colours.. [...]

I must admit I haven't looked into the custom status bar (csb) and ui viewport features since I don't use them. But from here arises my question: do the old (i.e. now existing) settings still make sense in this situation? Or is some default csb and ui viewport used in that case so that the settings are meaningless even then?

I use a very minimalistic text only WPS without backdrop.

[JdGordon]

[St.] has it exactly backwards... I'm saying that if the WPS doesnt disable the sbs, then there is a tiny chance that will will load a backdrop, i.e it would expect to be using the themes backdrop and not its own. if no backdrop is loaded in the WPS then there is no change, it will display a flat colour.

fml: (the custom statusbar acronym is sbs ) yes thats what I'm asking, and what I was arguing probably 2 months ago. using a sbs should be sufficient to set the menus backdrop, colours and ui viewport. The 3 settings in [St.]'s post as well as "ui viewport" all are redundant

[fml2]

fml: (the custom statusbar acronym is sbs ) yes thats what I'm asking, and what I was arguing probably 2 months ago. using a sbs [...]

My qestion was rather what happens if I don't use any sbs and/or a custom viewport explicitly. I just want to use the inbuilt status bar (however it looks like -- I assume it has all important information in it) and the default viewport (which, I think and hope, is the whole screen).

[JdGordon]

yes, thats the only downside to this.