I'll do something about those skin-errors in due course. Most likely I'll add an option to enigma and the skin to suppress them. The extra load is negligible.it generates a huge amount of skin-error reports on openeing every single screen. Isn't this an extra load for E2? Anyway: it makes E2 feedback difficult to read.
If I missed one (like this one), please report. So far, this seems to be the only one missing.But even this generic template doesn't show all labels: e.g. the green button in the about-screen has none.
It's an attempt. There is another rationale at work though:2- You told me you're now working on a way that only those colour-buttons that actually apply to a specific screen will show up. Is that also going to work for the extra buttons several screens need (such as the buttons 'menu', 'info' and 'text')? I already noticed a 'ConditionalShowHide' for the textbutton: is that a first step in that direction?
Nearly every screen contains numerous active buttons. Most of these buttons are undocumented. The reason that we supply a legend for the four coloured ones usually stems from the fact that the coloured buttons are generic and are the designated "special-action" buttons. All the other buttons have (hidden) extra meanings which hopefully can be inferred from the actual text on the button (the coloured buttons lack that, obviously). So this raises the question: why single out some of the other buttons and provide an indicator they can be pressed *without* showing a legend what it means? I.e. it would be logical to either not document *any* other buttons besides the coloured ones, or one should document *all* other buttons, preferably with legends... And guess what, the latter option is already provided for by means of the help button.
So, in short, the only logical conclusion would seem to be that having those extra TEXT, INFO, MENU buttons on screens is of questionable value and merely clutters the screen needlessly in most cases.
There already is a generic way. The generic title of a screen is displayed in the upper right. If a screen does it differently and doesn't show up the right way, the screen/plugin needs to be fixed, not the skin. Most screens get it right.3- Maybe it will also be possible to create a generic way to display the title? As it is now some screens need a hard 'title="XXXXX", while others generate (translatable) titles with the widget 'source="Title" render="Label" '
Yes, the rule is, if a screen is seen often enough, it should be skinned. If a screen is extremely rare, skinning it in a generic skin is a waste of resources.4- I take it that all commonly used functionality will get skinned screens? atm several (such as Device Manager and positioner setup) are not skinned.
I don't see all the common screens on my device though. Sometimes I do not know how to open it, sometimes I lack the plugin for it. Either notify me of screens that are missing, or provide patches (the latter is preferred of course).
> 5- The length (heigth) of the widgets list/config etc is not correct: the length should be a multiple of the item height to be displayed properly. As I understand it fontsize will be configurable: will that take into account the itemheight and height of the widget ( I hope I expressed myself clear enough).
Yes, some list/config widgets have a separate Itemheight parameter which should be dependent on font sizes. The widgets need to be fixed to allow for this. It's on the todo list, but if someone fixes it for me, they're more than welcome ;-).
> 6- General remarks: the distribution over the available space doesn't seem to be optimal (yet).
> See e.g. the channel-list: the list is very small (might be widened a bit to the left), and the description area (under the PiG) is too wide: it almost touches the channels.
It's a tradeoff, of course. With regards to the channel list vs. description area... In most screens I started out with a screen partitioned in four equal tiles. If I were to make the channel list wider (yes, there is room), then the description area indeed gets smaller; it would allow less text to fit in there, is that good or bad? You're saying that the description area almost touches the channel list; does that mean that you'd like a larger gap there for better readability? Keep in mind that fonts could be a bit smaller in general, so a wider channel list might make the channel list needlessly wide, because the text rarely will touch the right side of the screen anymore.
> Also the top bar (with the title etc) is very small (low in height), while at the same time the colour-buttons are still far away from the bottom.
With regard to the top bar and the menu button bar, they're symmetrical in size. Meaning: if on your screen it looks asymmetrical, then most likely your TV-display is not centered vertically; is that possible?
Edited by BuGless, 13 February 2013 - 09:29.