Skin Support - Post questions for all my skins in here.

I designed those screens blind, ages ago.

I have doubled up the button code though.

I have a template of buttons as well as the buttons again individually.

I can center them with the textoffset in "config"

Right, just reading back through this thread. (fun read)

Willo3092 mentioned the multiboot screen issue. i.e the double buttons. here in Jan 2023

Thread

Skin Support - Post questions for all my skins in here.

Instead of having a support thread for each skin, I am only now going to have 1 skin support thread. Other threads will soon be deleted.

Use this thread to post any question, bugs, feedback for any of my skins.

I will need to know.
Satellite Box
Image
Which exact skin and whether the 720 or 1080 version.

KiddaC

Dec 23rd 2018

Why has the choicelist screens vertically alignment now buggered up. Because openatv have broken things again adding offset or center alignment to some elements that have historically always been offset by the skin parameters.
in skin.xml in slyk q skin which I just updated. I removed the top offset to accomodate openatvs amends. Not realising this would break layout on all other images. (grr).

This is the losing battle we are now fighting. Nobody is on the same page. Nobody even cares about years worth of code.



I am just going to undo those parameters and but them back to what they used to be. Openatv layouts can then be wrong (which will now be pretty much bottom aligned.) As its them that broke things.

I don't know, i can't keep up with all these changes.

lists that should be list but are choicelists

Configs that should be configs but maybe not configs.

Choicelists that are configs.

Quickselects which are openatvs version of choicelists.

Who fucking knows.

List -> a list of things
Choicelist -> and list that can be selected with a button
Config -> a selection of config choices, yes/no, inputs etc etc.
Quickselect - not even a thing. Its a choicelist. Stop feeding lazy people that want buttons for selecting lists elements in a list. It is literally quicker to scroll up and down a list than look down at your remote to find a red button or a number button.

Parameters originally used so skinners could set offsets and sizes globally.

This is why looking back through this thread, I pretty much gave up on skin work as soon as all this python 3 chaos started.

I will work it all out eventually. But its a nightmare, and causing me and others a lot of unnecessary stress.

and your comment about the offset. What will fix one, will probably break the other. There would have been a reason they were like that in the first place. As shown on willows original multiboot screenshot. The layout was correct.

I actually don't understand why openvix are actually using name="config" in their multiboot screen.
Never used it, but to me its either a list element or a choicelist element.

and looking on github. It is defined as a choicelist.

self["config"] = ChoiceList(list=[ChoiceEntryComponent("", ((_("Retrieving image slots - Please wait...")), "Queued"))])

SO they are probably actually wrong there. As its probably the name config buggering things up
There is no paramaters for "config", so we use textoffset. But as this is also actually defined as a choicelist (which there are params), then they are clashing. I can fix this screen just putting the params back and removing the offset. As this is a vix only screen.

But then I got to try and work out where openatv have buggered up with the parameters. It is a bit of a mess.

I am just talking to myself at the moment. Talking to the rubber duck. So not after any replies. :)

So looking at choiceList.py on openatv github. Jbleyel put the RT_VALIGN_CENTER in when experimenting (nov 30 2021). Then reverted his commit and removed it (Dec 1 2021). 3 months later IanSav put it back in again (Mar 28 2022). *sigh*. This element has a parameter offset, so putting in anything other than top aligned or left aligned is going to break skinning choiceList.py

This has gone unnoticed from me for a year due to me having no desire to update to openatv 7.* due to all the crazyness going on. It worked perfectly on openatv 6.4.

Their error that one. Not mine.

Right, I have been a good boy and reported it

https://github.com/openatv/enigma2/issues/2877

OK openatv have agreed to add in a new skin parameter value as a work around to these choicelists being displayed differently on different images.
This will require an image update from yourselves. And me to put in a new line in all of my skins. I am currently going through my skins anyway. So that isn't a problem for me.
This seems to be a openatv 7.2 issue. I think 6.4 and 7.3 are ok.
Openvix no need to do anything.

[ChoiceList.py] Make vertical alignment configurable by IanSav · Pull Request #2878 · openatv/enigma2

Add a new skin parameter called "ChoicelistVerticalAlignment", that takes a value from "*top", "*center", "*middle" or "*bottom", to specify the vertical…

github.com

And if you want an old choicelist.py file that just works without any of the above hacks, here is an amended file for openatv.

Copy over to /usr/lib/enigma2/python/Components/

and reboot your gui.

abu baniaz I am doing an update for this skin very shortly.
But you now need this new file

/usr/share/enigma2/slyk-q-1080/

The new full repo for slyk q is now here. I am creating separate new repos
https://github.com/kiddac/Slyk_Q_1080

Copy all them files across and if its still broken, then raise it with the openatv team. You have read the conversation on git.

They broke things not me.