Beiträge von FoxyRabbit

    pixmapWidth and pixmapHeight should always be set correct in skin.xml This makes the total componentsize the size of the actual pixmap seen. And the values that you see in skin.xml is correct for what you see (you dont make invisible rectangels).


    If you do that you also need the pixmapY option to finetune the Y position for your needs. Else its set to python Y=0 (top).


    And if we want to use small graphic files (x,y), its even more important with the pixmapY attribute.


    I am really bad in german, so bare with me if I dont follow excactly! :face_with_tongue:

    Just double your pix x value and keep pix y the same. pixmap then starts to move right. centered within your new x value. So yes, you manipulate it at you wish, but not both ways.


    An indent of only 5 within a selectionPixmap looks really terrible in my opinion. The point here is that we have to leave that question up to the skin makers out there, and not for what have been the "wrong" standard for decades. And why bother with makin attributes for components within skin.xml at all if its not done properly. I can understand that it was missed, but leave it out with overlay is a bit odd. And especially when it is done in other components. Like beginMargin= (ServiceList), and so on.

    @zombi


    If you keep pixmapWidth and pixmapHeight values out of picture ratio values it will center the pixmap wihtin what of those two that are the bigger number. The lesser number will be the pixmap size. Lets say I use 20 for width and 30 height, wich is incorrect by the way. The size of pixmap will be shrinked to 20 width (less) and centered vertically wihtin the height 30, from the point y0. Since 30 is the itemheight this will look OK. but if you set pixmapHeight to 20 it will center pixmap vertically centered from y0 down to y20. You can test this yourself. If you use correct ratio values by the way, your pixmap will stick to x5 and y0 wich is code values.


    Yes, its a form of manipulation trick, but it should not be that way. If I want my pixmap to start at x position 20px, then it should be possible to set that value as an attribute in skin component.


    Anyway, I got it sorted out, just wanted others to have those same options when they work with skins.

    In python (see below) ident (x direction) for pixmap is set to 5, and pixmap y position is set to 0. If you downsize pixmap (icon) to less than text size the pixmap will stick to position y0. There is no centering neither in x or y direction. And we dont need that either.


    From standard code: res.append((eListboxPythonMultiContent.TYPE_PIXMAP_ALPHABLEND, 5, 0, pxw, pxh, png)) # x=5 y=0


    Standard code is:



    ...and it could be this, what solves the problem properly:


    You could even go further and auto calculate a textMargin from pixmapWidth to where text starts, but the code above will be good enough for a skin maker to solve every issue.

    Sorry, missed a word in first post! (indent)


    I just want to request an indent option for pixmap also. And I want a possibillity to adjust pixmap Y if I want to shrink pixmap, wich else will go to top.


    In the screenshot below I have used pixmapX="20" pixmapY="5". Downsized pixmap to 40px x 20px.


    In PP image we have added this option long time ago. The reason for I am requesting this here in this forum is that it should have been added as an option from the start. I just think someone forgot to do it when the components project was running.

    Bump!


    Here is my contribution to a solution for this request. Just in case if its the work burden that makes the difference here. I really think this wish request makes all skins look much better when you can show greyed buttons when colored buttons are disabled.


    Example of skin code with this solution (shows grey button if red button is disabled):


    XML
    <ePixmap pixmap="active_buttons/grey.png" position="80,165" size="24,24" zPosition="0" alphatest="blend" />
    <widget source="button_red" render="Pixmap" pixmap="active_buttons/red.png" zPosition="3" position="80,165" size="24,24" alphatest="blend">
    			<convert type="ConditionalShowHide" />
    		</widget>


    MovieSelection.py and TimerEdit.py attached (solution,zip).


    And as I wrote above, the new python changes will not crash any existing skins. The only thing we do here is adding new Boolean widget source (self["button_red"]), and set it False or True. Making it possible for everybody to use condiniolshowhide on colored buttons if they want to.

    Hi,


    Is it possible to wish for x and y attributes to adjust for pixmap indent in ChoiceList component? Everything else can be adjustet, but not pixmap. Thanks!


    Code
    <component type="ChoiceList" itemHeight="30" textX="70" textY="0" pixmapX="5" pixmapY="0" textWidth="625" textHeight="30" pixmapWidth="40" pixmapHeight="20" fillerCount="200" />


    Something like this...

    Hi,


    Just made (build) a new Peter Pan image for dm920, and got boot loop after restoring old settings (backup). Error log says something about webinterface certificate...


    Made a look in plugin.py for webinterface and saw that it uses /etc/enigma2/cert.pem and key.pem. I then tried to delete those files (rename) and the boot loop dissapeared. But webinterface does not work anymore.


    Flashed dm920 again and the problem is not there. WebInterface works fine.


    Could it be that there is conflict with older backuped cert.pem and key.pem with latest changes in webinterface?

    Hi folks!


    Very nice with the new option to use attributes for components in skin! Keep up the good work!


    The EPGSearchList component is using EPGList component, but it will not use EPGList attributes defined in skin. Is it possible to make it do that, or make a separate one for this list? A separate would be prefered if someone wish to make this list different from EPGList component.

    Hi folks!


    I have problem building image for dm920 (first time). I have no problem building images for det the rest of OE 2.5 tuners. Tried to google and search this forum for something similar, but cant find anything helping me.



    I have no clue of what is going on here... and especially when other images build without problems. :frowning_face:

    Hi folks! :smiling_face:


    Someone else that get gsod when entering cookies in menu section? Something about timestamp out of range...



    I think this was no problem for just a few days ago, but suddenly we (developers of pp image) are several people getting this error.

    Perfect! But I want to discuss something else with you.


    If you get the list with "Storage devices" like:


    Hard disk
    Network Mount
    Internal Flash


    Hard disk we can not copy, move or rename, but Network Mount and Internal Flash you can start the action, but I have not testet if it really does it, I dont have the guts. My question is, is it possible (easy) to block for this action to happen for storage devices?