View Full Version : Skin Simple 1080 button bar
Just want opinions... coloured text or button graphics. Coloured text stops button graphics showing when they should not, and not having graphics leaves more room for text.
6137361374
6137561376
6137761378
6137961380
Coloured text for me :thumbsup:
The coloured text screen shots show the problems with the contrast against a coloured background. White text on black (or a dark colour) is always readable, red text against a black background is difficult.
However, no-one is imposing the use of a skin when other are available so its down to personal taste. My eyes are not as good as they were when I was young so text menus with better contrast and more basic rounded/upright fonts suit me better.
I did once have a STB where the designer thought light grey text on a light blue background was a good idea. It’s also a mistake Barclaycard once made with some of their printed literature – white text on a light(ish) blue background. The light blue being the colour of their corporate logo.
Button graphics for me every time, coloured text is very difficult to read.
I'd go for graphics where you've got higher transparency. You need the white text to cut through the changing background.
I prefer the buttons. Coloured text can be difficult to read on certain backgrounds as @adm says.
BrokenUnusableAccount
02-02-21, 00:35
Just want opinions... coloured text or button graphics. Coloured text stops button graphics showing when they should not, and not having graphics leaves more room for text.
I think I prefer buttons.
I don't know much about how skins work but if you can't make a button disappear if the text for it is blank (blank because it has no function) could you instead make the text be a dash indicating it has no function?
I think I prefer buttons.
I don't know much about how skins work but if you can't make a button disappear if the text for it is blank (blank because it has no function) could you instead make the text be a dash indicating it has no function?The buttons showing is nothing to do with this skin. It is because a mountain of work would have to be done to bring the unmaintained skins up to date. An no skins don't add text.
I prefer the buttons. Coloured text can be difficult to read on certain backgrounds as @adm says.Background is black, except the second infobar which currently is the wrong shade. If you flick from first infobar to second infobar you will see second infobar is far too light and that is the problem.
Previously this did not notice as there was never a button bar in that screen.
This is what it looks like with SIB transparency fixed...
61382
TBH, I don't think the grabs do it justice. On the TV it looks good.
BrokenUnusableAccount
02-02-21, 03:18
The buttons showing is nothing to do with this skin.
That doesn't change the argument.
You were the one who said you didn't like the buttons showing when there was no function/no text for them.
It would make more sense to have the button and a dash indicating no function than to just have no button and no text for some of the buttons.
Background is black, except the second infobar which currently is the wrong shade. If you flick from first infobar to second infobar you will see second infobar is far too light and that is the problem.
But it's just the right transparency to still see the TV program. I like to bring up the big full screen second infobar and still be able to see the TV programme properly.
You were the one who said you didn't like the buttons showing when there was no function/no text for them.
It would make more sense to have the button and a dash indicating no function than to just have no button and no text for some of the buttons.Having a dash just adds another thing that should not be there. And it is nothing to do with the skin.
I'd argue that having labels indicating that the button does nothing just adds cognitive load to the user. Taken to its logical conclusion, we should also show menu, info icetc. with a red X through them when they do nothing.
If you press one of the unassigned buttons, you'll automatically get the button unassigned X popup. That should be sufficient.
BrokenUnusableAccount
02-02-21, 14:02
Having a dash just adds another thing that should not be there. And it is nothing to do with the skin.
Stop telling me over and over that it's nothing to do with the skin.
The fact that I initially thought it was to do with the skin should not disqualify me from answering your question about which arrangement (coloured buttons or coloured text) I prefer.
Why shouldn't they be there?
Isn't the complete row of coloured buttons that matches the row of real coloured buttons on the remote the way one makes it clear that they correspond with the buttons on the remote?
If not why do you bother putting them in the same order as on the remote?
Why shouldn't they be there?
Isn't the complete row of coloured buttons that matches the row of real coloured buttons on the remote the way one makes it clear that they correspond with the buttons on the remote?
If not why do you bother putting them in the same order as on the remote?Inactive buttons should not be there. Being there is due to code in enigma that had no foresight to templating. If we fix the python code (couple of weeks work) we would then need to fix 10 unmaintained skins (about a month's work each) to have a fully automatic button bar. Alternatively we could just delete all those skins, after all no one cares for them, but I don't think that would go down too well, which is why I suggested this change. Some skins, e.g. RED HD, are beyond hope because the buttons are in different positions in every screen.
61388
61390
Other popular skins (Confluence and Magic) have been using coloured text for a long time.
61391
61392
BrokenUnusableAccount
02-02-21, 23:28
Inactive buttons should not be there.
This is just your opinion.
This is just your opinion.So you would like meaningless crufts dotted all over the skin?
BrokenUnusableAccount
03-02-21, 16:41
So you would like meaningless crufts dotted all over the skin?
Now you're just trying to provoke me so you can ban me.
Now you're just trying to provoke meAm I pushing the right buttons? Maybe the coloured ones?
The button bar spacing in 5.4.006 has gone peculiar in at least 2 screens, others appear ok.....
61445 61446
Setup/Information/About is another screen.
The button bar spacing in 5.4.006 has gone peculiar in at least 2 screens, others appear ok.....
61445 61446
Setup/Information/About is another screen.Can you try with the latest version from github because I can't reproduce that.
I've grabbed the files skin.xml, skin_plugins.xml, skin_templates.xml and vix_skin.xml from
https://github.com/OpenViX/skins/tree/master/src/skins/1080/Simple_Ten_Eighty
and it still happens. Any files I've missed, or maybe I've grabbed the wrong files?
(Couch flashed 5.4.006 with a settings restore this morning.)
Maybe someone else can confirm if they're seeing the same?
root@vuultimo4k:/usr/share/enigma2/Simple_Ten_Eighty# ls -l skin* vix*
-rw-r--r-- 1 root root 152110 Feb 10 16:55 skin.xml
-rw-r--r-- 1 root root 152110 Feb 8 21:11 skin.xml.orig
-rw-r--r-- 1 root root 155124 Feb 10 16:55 skin_plugins.xml
-rw-r--r-- 1 root root 155124 Feb 8 21:11 skin_plugins.xml.orig
-rw-r--r-- 1 root root 27577 Feb 10 16:55 skin_templates.xml
-rw-r--r-- 1 root root 27576 Feb 8 21:11 skin_templates.xml.orig
-rw-r--r-- 1 root root 41078 Feb 10 16:55 vix_skin.xml
-rw-r--r-- 1 root root 41078 Feb 8 21:11 vix_skin.xml.orig
root@vuultimo4k:/usr/share/enigma2/Simple_Ten_Eighty#
BrokenUnusableAccount
10-02-21, 18:32
Maybe someone else can confirm if they're seeing the same?
Yes, same here.
BrokenUnusableAccount
10-02-21, 18:33
Am I pushing the right buttons? Maybe the coloured ones?
You were, but I'm over it now. If I don't like it when it's done I will have a go at making my own skin.
Could this cause it .... ?
https://github.com/OpenViX/skins/commit/27c9b0d8f5c7bb7d12bfdb8316a5fbd9b1c83eec
Could this cause it .... ?
https://github.com/OpenViX/skins/commit/27c9b0d8f5c7bb7d12bfdb8316a5fbd9b1c83eecThat is reverted.
That is reverted.
Cheers, now working ok.
And the reason for the problem... inconsistency...
halign="left" is the default setting so can be omitted. But it turns out Components.Button does not follow that default.
If anyone is not happy with the update to the button bar and want to drop back to the previous version they can use the attached file.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.