17 replies to this topic

[DimitarCC]

Hello,

 

I want to report some stuff that seems wrong to me.

I own a vu+ uno 4k se and i have installed the latest openpli 7.0 rc before 5 days and then i regularly update it.

First i'd like to say that since my STB have LCD screen on the front in the image is included by default lcd4linux plugin.

That plugin doesn't work at all on openpli 7.0. no matter what i set there it has no effect over the lcd screen.

Even if i uninstall it lcd screen continue to work and look in the same way.

 

Second regarding skinning of the LCD screen i noticed that is controlled by skin_display.xml that is in skins folder.

However there is no way to use a skin specific setting for that since it always takes that skin_display.xml.

If i modify it it works but on image update it get overwritten.

I checked the source and in skin.py seems there is hardcodded to get skin_display.xml from SCOPE_SKIN. That is wrong i think.

It should be made conditional if in SCOPE_CURRENT_SKIN there is such a file takes it from there, if not takes it from SCOPE_SKIN

 

Please let me know what you think about my suggestions.

Thanks.

[Pr2]

Hi,

Custom skin values must be placed into the folder:

/etc/enigma2/

So give it a try placing your custom file there.

Pr2

[DimitarCC]

Hi,

Custom skin values must be placed into the folder:

/etc/enigma2/

So give it a try placing your custom file there.

Pr2

 

Do you mean my custom skin_display.xml should be placed in /etc/enigma2/ ?

But in that case since on my box is color LCD screen and i can put skin specific images i have to recreate my skin_display.xml for every skin and to replace it in /etc/enigma2/ (since there is no menu in settings to manage multiple display skins). That is quite odd and not user friendly and hell for skin makers.

It is much more friendly if it search it in current skin folder. Then it will be a skin specific.

 

If you mean with "custom values" a custom settings for the lcd4linux plugin i dont think that is the case since i set the settings from the webif. they are applied when i set them but after enigma restart all my changes are gone. Also setting it via th eplugin menu not works at all.

Edited by DimitarCC, 17 December 2018 - 11:01.

[Pr2]

If you want to change some specific part of a skin (I am not talking of LCD4Linux) you can create a custom:  skin_user.xml the change you make in this file are overwriting the default one from the skin you use.

 

Here is a concrete exemple:

<skin>
 <!-- Volume -->
  <screen name="Volume" title="Volume" position="30,360" size="30,330" backgroundColor="transpBlack" zPosition="1" flags="wfNoBorder">
   <widget name="Volume" pixmap="PLi-FullNightHD/infobar/volumeslider.png" position="0,3" size="30,300" orientation="orBottomToTop" transparent="1" zPosition="1"/>
   <ePixmap pixmap="PLi-FullNightHD/infobar/vol_box.png" position="30,303" size="30,24" alphatest="on" zPosition="4"/>
  </screen>
 
<!-- Console -->
 <screen name="Console" title="Command execution" position="fill" flags="wfNoBorder">
  <panel name="PigTemplate"/>
  <widget name="text" position="30,540" size="1860,500" itemHeight="38" font="Fixed;28" transparent="1" foregroundColor="white" scrollbarMode="showOnDemand"/>
 </screen>
</skin>

In this exemple what i do is:

I move the Volume bar to the right.

I change the console screen to display the PiG windows when I start a shell script from Hotkey.

 

So all the rest of the skin remains untouched.

 

So this an easy way for end-user to be able to customised there favourite skin for there own need. And those file are not overwritten during online update.

 

Most user are testing skins and then select there preferred one and then they stick with it, then they start customising it if needed thanks to file mentioned above.

So there is no real reason to have a more complex approach to have end user being able to customise individually every possible skin.

 

Now if you are a skin creator then you have to place everything in your own skin folder structure and it is normal that during online update those file are overwritten when the skin is updated by the author.

 

I am don't know if it is possible to create also a:  skin_user_display.xml

Edited by Pr2, 17 December 2018 - 11:56.

[DimitarCC]

If you want to change some specific part of a skin (I am not talking of LCD4Linux) you can create a custom:  skin_user.xml the change you make in this file are overwriting the default one from the skin you use.

 

Here is a concrete exemple:

<skin>
 <!-- Volume -->
  <screen name="Volume" title="Volume" position="30,360" size="30,330" backgroundColor="transpBlack" zPosition="1" flags="wfNoBorder">
   <widget name="Volume" pixmap="PLi-FullNightHD/infobar/volumeslider.png" position="0,3" size="30,300" orientation="orBottomToTop" transparent="1" zPosition="1"/>
   <ePixmap pixmap="PLi-FullNightHD/infobar/vol_box.png" position="30,303" size="30,24" alphatest="on" zPosition="4"/>
  </screen>
 
<!-- Console -->
 <screen name="Console" title="Command execution" position="fill" flags="wfNoBorder">
  <panel name="PigTemplate"/>
  <widget name="text" position="30,540" size="1860,500" itemHeight="38" font="Fixed;28" transparent="1" foregroundColor="white" scrollbarMode="showOnDemand"/>
 </screen>
</skin>

In this exemple what i do is:

I move the Volume bar to the right.

I change the console screen to display the PiG windows when I start a shell script from Hotkey.

 

So all the rest of the skin remains untouched.

 

So this an easy way for end-user to be able to customised there favourite skin for there own need. And those file are not overwritten during online update.

 

Most user are testing skins and then select there preferred one and then they stick with it, then they start customising it if needed thanks to file mentioned above.

So there is no real reason to have a more complex approach to have end user being able to customise individually every possible skin.

 

Now if you are a skin creator then you have to place everything in your own skin folder structure and it is normal that during online update those file are overwritten when the skin is updated by the author.

 

I am don't know if it is possible to create also a:  skin_user_display.xml

I think skin_user_display.xml is no possible to be created. At least in skin.py there is no option for that.

And i am a developer and skin creator and i do not want to modify a part of the skin but to create completely new one coming together with skin_display.xml. But now this is not possible. No matter what i do i can not overwrite the LCD display skin.

The only way working for me so far is to directly change the default skin_display.xml.

Still i think for skin creators (including me) will be much better if the can overwrite the LCD look per skin and not for every different skin to create/update everytime a single user file.

The current concept is useless. At least allow user to pick LCD display skins somewhere from the settings.

[DimitarCC]

Besides since lcd4linux not work with current OpenPLI it will be better if it is not present by default in th eimage.

[DimitarCC]

For the developers here i can make a pull request or diff with proposed changes of skin.py by me so to make that decentralisation of skin_display.xml possible.

[Pr2]

For the developers here i can make a pull request or diff with proposed changes of skin.py by me so to make that decentralisation of skin_display.xml possible.

 

I think that this kind of initiative is always welcome. 

[DimitarCC]

 

For the developers here i can make a pull request or diff with proposed changes of skin.py by me so to make that decentralisation of skin_display.xml possible.

 

I think that this kind of initiative is always welcome. 

 

 

done. https://github.com/O...igma2/pull/1889

[anudanan]

I would like to update my uno4kse in the next days from openpli 6.1 to 7.0rc because sometimes I have a driver crash during zapping or sonetimes when a timer needs a tuner. I hope that is fixed in 7.0

@DimitarCC
Do you feel 7.0 is more stable them 6.1 around the drivers for uno4kse?

Edited by anudanan, 18 December 2018 - 19:16.

[DimitarCC]

I would like to update my uno4kse in the next days from openpli 6.1 to 7.0rc because sometimes I have a driver crash during zapping or sonetimes when a timer needs a tuner. I hope that is fixed in 7.0

@DimitarCC
Do you feel 7.0 is more stable them 6.1 around the drivers for uno4kse?

@anudanan I have never used 6.1 on my uno4kse

[Erik Slagter]

Besides since lcd4linux not work with current OpenPLI it will be better if it is not present by default in th eimage.

And you base that on what information?

[jackassnl]

 

 

I think skin_user_display.xml is no possible to be created. At least in skin.py there is no option for that.

And i am a developer and skin creator and i do not want to modify a part of the skin but to create completely new one coming together with skin_display.xml. But now this is not possible. No matter what i do i can not overwrite the LCD display skin.

The only way working for me so far is to directly change the default skin_display.xml.

Still i think for skin creators (including me) will be much better if the can overwrite the LCD look per skin and not for every different skin to create/update everytime a single user file.

The current concept is useless. At least allow user to pick LCD display skins somewhere from the settings.

 

I've added the custom display stuff to to my user_skin_[SKIN-NAME].xml in /etc/enigma2 and that works.

        <windowstyle id="1" type="skinned">
                <color color="#000000" name="Background"/>
                <color color="#ffffff" name="LabelForeground"/>
                <color color="#000000" name="ListboxBackground"/>
                <color color="#ffffff" name="ListboxForeground"/>
                <color color="#000000" name="ListboxSelectedBackground"/>
                <color color="#ffffff" name="ListboxSelectedForeground"/>
                <color color="#000000" name="ListboxMarkedBackground"/>
                <color color="#ffffff" name="ListboxMarkedForeground"/>
                <color color="#000000" name="ListboxMarkedAndSelectedBackground"/>
                <color color="#ffffff" name="ListboxMarkedAndSelectedForeground"/>
                <color color="#ffffff" name="WindowTitleForeground"/>
                <color color="#000000" name="WindowTitleBackground"/>
        </windowstyle>
        <fonts>
                <!-- pick a funky name for the font, so we don't conflict  -->
                <font filename="nmsbd.ttf" name="FdLcD" scale="100"/>
        </fonts>

<!-- template -->
        <screen name="SummaryClockPanel">
                <widget source="global.CurrentTime" render="Label" position="230,180" size="160,60" font="FdLcD;60" halign="right" valign="bottom" noWrap="1">
                        <convert type="ClockToText"></convert>
                </widget>
        </screen>

Edited by jackassnl, 20 December 2018 - 06:34.

[DimitarCC]

 

 

 

I think skin_user_display.xml is no possible to be created. At least in skin.py there is no option for that.

And i am a developer and skin creator and i do not want to modify a part of the skin but to create completely new one coming together with skin_display.xml. But now this is not possible. No matter what i do i can not overwrite the LCD display skin.

The only way working for me so far is to directly change the default skin_display.xml.

Still i think for skin creators (including me) will be much better if the can overwrite the LCD look per skin and not for every different skin to create/update everytime a single user file.

The current concept is useless. At least allow user to pick LCD display skins somewhere from the settings.

 

I've added the custom display stuff to to my user_skin_[SKIN-NAME].xml in /etc/enigma2 and that works.

        <windowstyle id="1" type="skinned">
                <color color="#000000" name="Background"/>
                <color color="#ffffff" name="LabelForeground"/>
                <color color="#000000" name="ListboxBackground"/>
                <color color="#ffffff" name="ListboxForeground"/>
                <color color="#000000" name="ListboxSelectedBackground"/>
                <color color="#ffffff" name="ListboxSelectedForeground"/>
                <color color="#000000" name="ListboxMarkedBackground"/>
                <color color="#ffffff" name="ListboxMarkedForeground"/>
                <color color="#000000" name="ListboxMarkedAndSelectedBackground"/>
                <color color="#ffffff" name="ListboxMarkedAndSelectedForeground"/>
                <color color="#ffffff" name="WindowTitleForeground"/>
                <color color="#000000" name="WindowTitleBackground"/>
        </windowstyle>
        <fonts>
                <!-- pick a funky name for the font, so we don't conflict  -->
                <font filename="nmsbd.ttf" name="FdLcD" scale="100"/>
        </fonts>

<!-- template -->
        <screen name="SummaryClockPanel">
                <widget source="global.CurrentTime" render="Label" position="230,180" size="160,60" font="FdLcD;60" halign="right" valign="bottom" noWrap="1">
                        <convert type="ClockToText"></convert>
                </widget>
        </screen>

 

Yep it works but still if you want different stuff for different skins you can not do that with user skin. Orr at least i didnt make it to work

[DimitarCC]

 

Besides since lcd4linux not work with current OpenPLI it will be better if it is not present by default in th eimage.

And you base that on what information?

 

I base this on my personal experience. Whatever i set in that plugin config is not saved in OpenPLI.... after restart of enigma all is lost. Also the settings menu works strange (at least on 7.0RC and uno4kse)

[Erik Slagter]

Over here it just works, based on my experience... On two receivers.

Edited by Erik Slagter, 24 December 2018 - 17:58.

[DimitarCC]

Over here it just works, based on my experience... On two receivers.

On what receivers? As i said it still not works on my uno4kse. Dont get me wrong....it do works when you play with the settings. But after enigma restart it get the current skin_display.xml settings. So it not works for me.

[Erik Slagter]

I am currently using it on Duo4k and Ultimo4k. The Duo4k has a "sumo" image (the successor of "develop"), but the Ultimo4k has a public 7.0rc image and just works. The Uno4kSE is quite similar to these, same display interface, only different resolution.

 

For this display interface to work, lcd4linux needs make a skin_display.xml in /etc/enigma2. If you define your own there, the two will collide, won't work.