Skinning concept

[2stein]

registering with:

        PluginDescriptor(
            name=_("TMDB Infos"),
            description=_("TMDB Infos"),
            where=[
                PluginDescriptor.WHERE_EVENTINFO,
            ],
            fnc=showEventInfos

doesnt seem to be enough... when i press the red key i get the message that the plugin is not installed. :-(

 

[2stein]

never mind... i did a monkey patch that works.

 

[2stein]

is this a skin or plugin bug?

 

[DimitarCC]

Most likely plugin fault since it have 2 description widgets with same text....

 

[Huevos]

It doesn't happen in S1080.

 

[DimitarCC]

in DarkOS it have 2 widgets that are used for same thing in the plugin. I will remove one of them....

 

[2stein]

let's move on to lcd skins.
my problem is that on my dm900 all lcd skin screens are cut off at the right hand side and therefore missing a few pixels (5 or so).
as the screenshot shows the full screen, i suspect that a frame might cover the right hand side of the display a bit mechanically. a production problem so to speak.
have you guys seen something similar on your dm9xx boxes?

 

[DimitarCC]

DM900 have some pixels difference in lcd width than standard 400x240 so its actually 380x240. That makes standard lcd skins no fit...

 

[2stein]

so, your dm920 does not have that problem?
is there an lcd skin that fits or do i have to create one myself?

 

[DimitarCC]

920 have same issue. I use my own lcd skin. So you probably have to made one yourself. All lcd skins from feed doesnt display well on dreambox due to that difference.

 

[2stein]

if i recall correctly, the dreamos lcd skin did not use the full 400x240 size for content... and i was wondering why... now i know

 

[DimitarCC]

Yeah..But there is only 400x240 lcd skins out there so they all not fit

 

[2stein]

i checked a dreamos lcd skin which suggests that the display has a usable width of 395. also the origin of the skin elements is not 0,0 but 5,5 which could mean that the effective usable size is 390 by 230.
btw. doesnt gigablue quad 4k pro have the same display? maybe we could borrow from them...

 

[DimitarCC]

gigablue quad 4k pro have full featured 400x240 lcd. So not same as dreambox...

 

[2stein]

well, i read that somebody replaced a defective dreambox lcd with a gigablue one and it worked. not sure it was a gigablue pro or a non-pro one. but still could be different because you wouldnt see the difference on a dreambox .

 

[2stein]

looks like they used 395 for max width:

 <widget source="session.Event_Now" render="Label" 
position="300,145" size="95,30" valign="top" halign="right" font="LCD_display; 20" foregroundColor="#F78181" >

 

[twol]

so the display skins are here: (we have our own branch) display390 is the dm900, display 400 is the dm920.
https://github.com/oe-alliance/enigma2-display-skins/tree/openvix

you could manually try changing in the lcd skins to say 380 (either download the lcd skins from the link) or install from plugins and change (they are installed here.../usr/share/enigma2/display)

 

[2stein]

well, DimitarCC said that the standard lcd skin on his dm920 has the same bug as my dm900. so both don't work... and i would suspect that they dont work on gigablue either.
so, i would then create a 395 version... derived from the 400 version, where the x pos of widgets that end at 400 will be decremented by 5 pixels (which hopefully doesnt create conflicts with other widgets).
alternatively i could reduce the x size by 5.
i have a few script to modify skins... maybe i could change one to do this automagically.

 

[twol]

well, DimitarCC said that the standard lcd skin on his dm920 has the same bug as my dm900. so both don't work... and i would suspect that they dont work on gigablue either.
so, i would then create a 395 version... derived from the 400 version, where the x pos of widgets that end at 400 will be decremented by 5 pixels (which hopefully doesnt create conflicts with other widgets).
alternatively i could reduce the x size by 5.
i have a few script to modify skins... maybe i could change one to do this automagically.

I would try it copy to /share and see how it looks

 

[2stein]

btw... what does size="100,*" mean? fill up the remaining y space?