Posts by KiddaC

    By IPTV account, I presume you mean playing an iptv playlist you have.


    If its an xstream codes playlists with a url that includes get.php in it

    you can use my xstreamity plugin

    X-Streamity - Xtream Codes IPTV Player (new thread)


    If its just a standard playlist you can use my bouquet maker
    Jedi Maker Xtream (IPTV Bouquet Creator) - Main thread

    If your box is not able to use the chronium plugin which comes with youtube (not to sure if your box can),, there is a seperate youtube plugin here
    RE: YouTube Plugin by taapat

    They change the name from TextOffset to TextPadding

    Also as you can see they change the name for secondfont


    00:05:32.5725 [Skin] Warning: Attribute 'secondfont' has been deprecated, use 'valueFont' instead!

    00:05:32.5729 [Skin] Warning: Attribute 'textOffset' has been deprecated, use 'textPadding' instead!

    There are fallbacks for textoffset and secondfont in their code.
    Nothing needs changing in my skins for that. Otherwise they would break on other images


    I have just spent most of my evening reading through all the commits on skin.py
    So I am getting up to speed.

    I have no problem with new naming conventions as long as there are legacy fallbacks.
    And only when all the big players are using the same code, thats when they should remove the legacy stuff.

    Ok I have removed the inline offset, removed the second font. Change the description to name="description"

    Does this display any differently abu baniaz


    Code
    <screen name="MultiBootManager" position="0,0" size="1920,1080" flags="wfNoBorder" backgroundColor="transparent">
    <panel name="template1"/>
    <ePixmap pixmap="q-backgrounds/setup-bg.png" alphatest="blend" position="540,384" size="1002,623" zPosition="1"/>
    <widget name="slotlist" position="540,385" size="1002,624" font="Regular;33" foregroundColor="white" backgroundColor="mid" backgroundColorSelected="select-darkblue-bg" selectionPixmap="q-selectbars/q-menu-2.png" itemHeight="78" enableWrapAround="1" scrollbarMode="showNever" transparent="1" zPosition="2"/>
    <panel name="New-Buttons-T1"/>
    <widget name="description" position="540,140" size="1002,195" font="Regular;33" foregroundColor="white" backgroundColor="topmid" transparent="1"/>
    <ePixmap pixmap="buttons/key_help.png" position="1845,1030" size="38,38" alphatest="blend"/>
    </screen>

    yes, their hack on their hack requires it


    Quote

    Add a new skin parameter called "ChoicelistVerticalAlignment", that takes a value from "*top", "*center", "*middle" or "*bottom", to specify the vertical alignment of all ChoiceList base widgets. (NOTE: The "*" is required to tell the parameter processor that the data is actually a string value and to not try and process this value through the numeric parsers.)


    This parameter is a temporary hack to allow skins from other distributions to work, unchanged, on openATV. The other images should really fix the alignment issue in their code. The issue in the other images is that the default alignment is "top" and skinners have been forced to manually calculate offsets of the text to cause the text to be centered vertically in the line. In openATV we fixed this issue so that no such offset is required. Manually calculating and maintaining centering offsets is a waste of time and code when Enigma2 is fully capable of centering text itself. Most Enigma2 displays assume and expect text to be centered in the space allocated. The opeATV change makes this automatic and consistent for all widgets.

    this is what happens when they faff.


    ?thumbnail=1


    Your screenshot is neither using the values from skin parameters in skin.xml


    <parameter name="ChoicelistVerticalAlignment" value="*top" />

    <parameter name="ChoicelistName" value="68,20,919,78"/>


    or the inline textOffset


    <screen name="MultiBootManager" position="0,0" size="1920,1080" flags="wfNoBorder" backgroundColor="transparent">

    <panel name="template1"/>

    <ePixmap pixmap="q-backgrounds/setup-bg.png" alphatest="blend" position="540,384" size="1002,623" zPosition="1"/>

    <widget name="slotlist" textOffset="15,0"


    As a mancunian would say. Proper fucked. Just make it a bloody list instead of all this crazy choicelist mayhem.


    I am back openatv. Have you missed me.

    aro1 try this version. But in playlist settings try switching between Stream Source URL: Standard or Direct Source


    XStreamity V4.02
    New files on post 1.


    Only a tiny update.


    Amended location box callback, to prevent an openatv double open issue if changing playlist.txt location option. (hopefully not broke other images)

    Tried to eliminate black screen freezes when zapping, by removing the stream log, and loading the picon after the stream. It seems to play alot better now.
    Added in seagens UHD skin files.

    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

    I said I will no longer be supporting python 2.7. Not deleting python 2.7 code.

    Which means I will be coding on python 3 images. Whereas before I coded on python 2.7. Then made it work on python 3.

    All the hybrid code is still there. But if something is better and faster to do it with python 3 code and no easy way to convert to python 2.7, then and only then do we have a problem. I will not have any python 2.7 images to test with.