OpenSkin Designer [Modifikation by Humaxx]

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Im Anhang zum vorherigen Beitrag ist der gesamte Skin
      Es handelt sich um einen Skin für das AccuWeather-Plugin, der nur 3 Screenshots enthält
      Ich denke, dass die korrekte Darstellung der Haut mit dem Hautfaktor *f zusammenhängt
      Die Skin-Datei von Dorik1972 könnte im Anhang hilfreich sein
      Dateien

      • skin.zip

        (16,65 kB, 8 mal heruntergeladen, zuletzt: )

    • biko_73 schrieb:

      Im Anhang zum vorherigen Beitrag ist der gesamte Skin
      It contains only the .xml file. I need the complete skin, with all files (all directorys, all graphics...)
      - How much for the Ape? -

    • No, thats not what i mean. I need the complete skin with all files, but anyway i have added your 3 screen in my skin und have replaced your size "*f" and then it works.
      What mean *f in your skin.

      But i still dont know whats your problem.?
      Dateien

      • Unbenannt.png

        (97,48 kB, 30 mal heruntergeladen, zuletzt: )
      - How much for the Ape? -

    • Edit hgdo: unnötiges Direktzitat entfernt.

      Ja, wenn der f-Parameterfaktor gelöscht wird, kehrt der Skin zur herkömmlichen Methode zurück

      Dies ist die neue Methode, die von den Teams zum Entwerfen von Bildschirmen mit automatischer Skalierung entwickelt wurde.

      Es verwendet eine Quelle für das Bild, den Hintergrund oder das Symbol, basierend auf einer Quelle im SVG-Format, und konvertiert diese Quelle automatisch in Kompatibilität mit verschiedenen Auflösungen SD, HD, FHD, OHD auf der Haut.

      Bei dieser Methode passt ein Skin für alle Bildauflösungen und es ist nicht für jede Auflösung ein separater Skin erforderlich
      Neue Methode zur Verwendung einer Skin-Auflösung für alle Bilder nach f-Parameterfaktor

      Sie können den Skin sehen, den ich in Beitrag Nr. 821 angehängt habe, um zu erfahren, was ich sage

      Dieser Beitrag wurde bereits 5 mal editiert, zuletzt von biko_73 ()

    • @biko_73

      ich denke @Humaxx ist in der Lage deine englischen Posts zu lesen.
      Wahrscheinlich ist es einfacher als das was dein Übersetzungsprgramm ausgibt.

      ...und z.B. UHD unterstützt keine VU+ Receiver und für die f-Parameter benötigt es doch sicherlich Converter oder Renderer
      _______________________________________________________
      LG Nase
      Receiver
      Duo 4Kse DVB-S2x (45308X FBC) / DVB-T2 (BCM3466) ; Samsung HM321H intern ; Synology 218+ ; Inverto Unicable II IDLU-UWT110-CUO1O-32P Multischalter 5/32
      Uno 4K SE DVB-S2 (45208 FBC) ; TOSHIBA MQ01ABD0 extern ; Synology 218+ ; Inverto Unicable II IDLU-UWT110-CUO1O-32P Multischalter 5/32
      Uno 4K DVB-S2 (45208 FBC) ; Synology 218 ; Inverto Unicable II IDLU-UWT110-CUO1O-32P Multischalter 5/32 ; Inverto Pro Wideband IDLP-WDB01-OOPRO-OPP
      Zero 4K DVB-S2x (SI2166) / HMP-Combo DVB C/T2 Hybrid ; Synology 218+ ; Selfsat H30D2 / Maximum UHF 200


      Der Fortschritt lebt vom Austausch des Wissens. (Albert Einstein)
      Wende dein Gesicht der Sonne zu, dann fallen die Schatten hinter dich. (aus Uganda)

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von NaseDC ()

    • Thanks, it more easy-- i think it not allow to write other than German

      yes ...
      - UHD does not support VU+ receivers until now but support (sd, hd, fhd) which will be from one skin not different skin for each resolution

      there is package for svg for example it will display

      Quellcode

      1. opkg install rsvg

      check ... for example

      Quellcode

      1. self["logo"] = Pixmap()
      2. self["logo"].instance.setScale(1)
      3. self["logo"].instance.setPixmapFromFile('/path/to/image/file.svg)
      4. self.show()
      - for the f-parameters it certainly needs a converter or renderer -- Now Tappat do it on YouTube plugin file __init__.py as

      Quellcode

      1. try:
      2. # Check functions for full svg and scaling support
      3. from enigma import loadSVG
      4. from skin import applySkinFactor
      5. screenwidth = 'svg'
      6. except ImportError:
      7. from enigma import getDesktop
      8. screenwidth = getDesktop(0).size().width()
      9. if not screenwidth:
      10. screenwidth = 720
      description of how to set it in skins

      Quellcode

      1. # Usage: center : Center the object on parent based on parent size and object size.
      2. # e : Take the parent size/width.
      3. # c : Take the center point of parent size/width.
      4. # % : Take given percentage of parent size/width.
      5. # w : Multiply by current font width. (Only to be used in elements where the font attribute is available, i.e. not "None")
      6. # h : Multiply by current font height. (Only to be used in elements where the font attribute is available, i.e. not "None")
      7. # f : Replace with getSkinFactor().
      as my friend Dorik1972 say

      The whole difference is how the "size" is set in xml skin itself ... but this is solved by some compromise "universalization" of the xml skin or, if "by BAGAtomU" and "feldipersovo" , then by redefining this method in the class so that it works with all variants of xml-ok skins ...

      There is a plugin E2m3u2b, rewritten by "harmful type", so there in the folder modules is a certain file - skinpatcher.py ... it redefine the method in the class ... and make it do what needed in the same way on any image

      in fact,the get Skin Factor method on OpenPli and OpenATV done already ....

      Open

      Quellcode

      1. def getSkinFactor(screen=GUI_SKIN_ID):
      2. skinfactor = getDesktop(screen).size().height() / 720.0
      3. # if skinfactor not in [0.8, 1, 1.5, 3, 6]:
      4. # print("[Skin] Warning: Unexpected result for getSkinFactor '%0.4f'!" % skinfactor)
      5. return skinfactor
      OpenPLI

      Quellcode

      1. def getSkinFactor():
      2. skinfactor = getDesktop(GUI_SKIN_ID).size().height() / 720.0
      3. # if skinfactor not in [0.8, 1, 1.5, 3, 6]:
      4. # print("[Skin] Warning: Unexpected result for getSkinFactor '%0.4f'!" % skinfactor)
      5. return skinfactor
      all what i request hope to have that method on important program OpenSkin Designer as all image teams go to use this on future

      Dieser Beitrag wurde bereits 5 mal editiert, zuletzt von biko_73 ()

    • I think i can the osd make to ignore "*f". Is this a solution which is ok?
      Will it always "*f" can it also be another letter "*d" for example?


      -- Edit

      OK, i think i got it!?
      I have added the "skinfactor" for size and position.

      Test it (#1) and give feedback
      - How much for the Ape? -

      Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von Humaxx ()

    • all appreciation ...
      Unfortunately, the skin loses the f-factor when changing the position or size or font

      before

      Quellcode

      1. <widget name="city" position="14*f,8*f" size="666*f,30*f" font="Regular;24*f" foregroundColor="#FFF554" transparent="1" halign="center" valign="center" zPosition="0"/>
      after

      Quellcode

      1. <widget name="city" position="15,8" size="666,31" font="Regular;25" foregroundColor="#fff554" transparent="1" halign="center" valign="center" zPosition="0" />

    • Ahh, i see.
      I will have a look into that. That will take some time...

      -- EDIT--

      This factor process presents some problems for the OSD. First of all, I have to find a way how the OSD does not lose the factor information after moving it via mouse / keyboard. I guess I could manage that, but there can / will be small inaccuracies of 1 pixel in the calculation. Also the undo function then becomes (at least partially) unusable.

      I will again think about a solution.

      -- EDIT 2--

      I will upload (probably tomorrow) a test version in #1.
      This will be an ABSOLUTELY experimental test.

      I can not see through to the end the scope of the changes made, so there may be unusual errors / behavior that are not noticeable at first glance. Therefore a backup of the skin.xml should be kept!

      One can now move (factor) elements with the arrow keys or with the mouse, whereby the factor specification should now be preserved.

      Known issues:
      - There can be inaccuracies when moving with the arrow keys: Without the ctrl-key, it is normally moved by 5 pixels, with the ctrl-key by 1 pixel. Because of the factor, the element is also moved sometimes 6 or 0 pixels.
      - When moving with the mouse, the performance (with factor elements) is very poor.
      - The undo and redo function will not work if a factor element has been moved.
      - The size of a factor element cannot be changed by mouse yet: This will probably be possible, but with the same restrictions as for moving.
      - At the moment moving via mouse works only if pos X AND pos Y both are factored.
      - How much for the Ape? -

      Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von Humaxx () aus folgendem Grund: Ergänzung

    • So leider kein Fortschritt seit gestern. Ich lade die Version zum testen mal hoch. Beachtet #830
      - How much for the Ape? -

    • @biko_73
      I think I was able to solve the problem. In the end it was easier than I thought (if you know what you are doing...).
      Nevertheless, the OSD now makes a change in a place that was not planned, so there might be a problem somewhere and so I'm just releasing another experimental version for now. The performance is now much better, and it doesn't matter anymore if the position X AND Y are factorized or only one of them. Moving and resizing with mouse works now.

      Known problems:
      - Moving by keyboard: there can still be inaccuracies of 1 pixel. As an example: I move a label by keyboard by 5 pixels. But in fact it is moved only 4 or 6 pixels. Moving by 1 pixel does not always work.

      - Undo does not work: If a factor element is moved or changed in the designer. The undo memory is reset.

      Please test extensively and keep an eye out for unforeseen events
      - How much for the Ape? -

    • Good progress .... Thank you for your continuous attempts to improve and reform
      Now, in general, skin can deal with f* factor without ignore it
      Only the change values is difficult, as it does not accept the change with the mouse or the keyboard and only accepts the direct change in the value on xml code ....
      In some cases, and some conservation.... the previous values are restored before the change and after save
      Great we on the track ...

    • Hi again. I don't understand. For me the changes i made via Mouse or keyboard in the designer are stored. Or What do you mean? Where do you want to change the value?
      - How much for the Ape? -

    • Thanks again for your time

      attached test_1 you can transfer to OpenSkinDesigner_experimental version and try what i am faced
      i can't change by Mouse or keyboard and it not stored, only manual from code which can stored

      What i mean, i don't want to change by value it will be long and not easy
      all credit to you by making changing very easy by Mouse & keyboard on all versions before and we not want to miss that
      Dateien

      • Test_1.zip

        (174,11 kB, 8 mal heruntergeladen, zuletzt: )

    • OK, i dont know why the performance with your skin is this bad.
      In generally osd experimental works with your skin, but only if you "hit" the element absolutly correct.
      If you miss the element by 1 pixel the main screen is selected and it crashes.
      I will have a look into that, but i am not sure if i can fix that
      - How much for the Ape? -

    • @linux22
      I have tested your skin. You have made some errors:

      1) Comments (<!-- ) musst end with -->

      XML-Quellcode

      1. <!-- Skin: Default-OE-A skin,


      like this:

      XML-Quellcode

      1. <!-- Skin: Default-OE-A skin, -->
      2) You haven't set a resolution, here is an example


      Quellcode

      1. <output id="0">
      2. <resolution xres="1280" yres="720" bpp="32" />
      3. </output>

      3) Also you missed to set a windowstyle, something like that:


      XML-Quellcode

      1. <windowstyle type="skinned" id="0">
      2. <title offset="25,11" font="Regular;24" />
      3. <color name="Background" color="background" />
      4. </windowstyle>
      After you solved these problems the OSD should be able to open your skin. But i guess there will be error when try to show some screens, because "scalable options" in your skin
      - How much for the Ape? -

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von Humaxx ()