Beiträge von FoxyRabbit

  • Skin Entwicklung

    Zitat von alpha

    i don't think that i have to go back that far..


    Good, then you should have what you need to do the magic. Just customize it for your needs.


    My example link pointed to a OE2.0 version of the running text renderer. Just for information...

  • Skin Entwicklung

    If a renderer or converter is correct programmed the info you pull out will automatically change when there is changes in the system. Lets say you want to get the name of current program, det name will change imediatly when the next program starts.


    If you have some exact examples of what you are trying to do in your skin, it would be better to explain.


    We need "screen name" and the exact line of the "thing" you want to show/change on screen.

  • Skin Entwicklung

    Yes...


    The xml file consists of screens, every screen has its own name and they are defined in python codes. either in plugins or in OS code (also python code). What you can show on screen (osd) is what is programmed in that python code. If you want to show something custom (not defined in python code), you have to program it in the python code or use converters/renderers that can be used with the spesific screen regardless of code. The xml (skin) file is there for you to use custom graphics, placements, font styles and font sizes and more.


    Lets say you want to change something in "Infobar" screen. Search up name="InfoBar" in skin.xml of the skin you want to edit. Everything in between <screen and the next </screen> is what this specific screen will give you on TV screen. You can change whatever you want.


    Converters and renderers are used to pull out desired text from the system. There are many standard converters and renderers and there is plenty 3rd party ones. What you want to show on screen determines what converter and/or renderer you will use.


    When you decide to build skins, it is very nice to understand some python code. This code will tell you what you can show on screen and if there is something new added to a python screen since last time you edited your screen.


    For my example screen "InfoBar" the python code is in /usr/lib/enigma2/python/Screns/InfoBar.py. Take a look and you will find things defined in skin.xml.


    Every name="<screen_name>" in skin.xml refere to one screen on TV. One for main menu, one for Infobar and so on... How many screen you will find in a skin xml is different. It has to do with how serious the skin maker have been. Most python code have screens defined within python code. If skin.xml dont have it defined, the python screen will show on screen. If not defined in your python screen code and in your skin.xml, code will fail with GSOD.


    Yes, to be a skin maker is a monster job. Especially if you want your skin to cover all screens and plugins out there...


    No easy overview of total screens and their names, you have to know your OS code and where to find it on your system.

  • Audio Signal auf HDMI Anschluß abschalten

    Does your TV have a HDMI ARC output?


    The way you should do this is to use an HDMI cable from TV's ARC output to soundbar. Then setup TV to use ARC sound output. Your TV will send all sound signals to soundbar and keep your TV speakers silent. You might also set source as ARC manually on soundbar, but it should do it auto.

  • DM920 Unicable SatCR setup

    Hi, you should choose type unicable, Unicable configuration mode set to Unicable LNB. There you will find manufaturer Dura-Sat(DUR-line), and then choose type UK124. As you say, all tunerblocks should have different SATCRX for different frequencies spesific to that LNB module. One cable with satcr splitter to each tuner module.


    I'm from norway and have your hardware setup, works fine.

  • DM920 WITHOUT IP

    Is this out of the box issue?
    Has there been some image other than original image on this tuner?
    Has the tuner worked for some time?
    What happens when you just start it with power button on the back of tuner?
    Or, are you just trying to flash new image?


    There are many things we still dont know about your problem...

  • InfoBarGenerics.py - wrong text

    Discovered some wrong text in infobargenerics that was missed regarding the "new" menu system in DreamOS.



  • Update Check Plugin?

    bump!


    ... and there is some bad english that should be corrected.

    Python: UpdateCheck.py
    else:
				self._session.toastManager.showToast(_("Your Dreambox software is update to date!"))
				Log.i("There are no updates available.")


    Better english is "Your Dreambox software is up to date!"


    Here is my solution to get "Check on every boot" to work regardless of choice for "Automatically check for new updates".

    Python: UpdateCheck.py
    def check(self):
		if config.plugins.updatechecker.interval.value != UPDATE_CHECK_NEVER or config.plugins.updatechecker.checkonboot.value:
			iSoftwareTools.startSoftwareTools(self._onSoftwareToolsReady)

  • Update Check Plugin?

    Zitat von Reichi

    ch hab das ganze in den SoftwareManager integriert und nutze auch dessen Funktionen (auch wenn der wirklich garnicht toll ist).
    Im prinzip gings mir um einen EINFACHEN auto-update-check.


    Wenn Updates verfügbar sind wird nachgefragt, ja/nein.
    Ende ;).

    And I agree! Simple is best for autoupdate for sure.


    I may be only me, but when i activate for "Check on every boot" AND set "Automatically check for new updates" to "never" I do not get any update check. At least it does not show up on screen.


    Either "Check on every boot" should be deactivated auto when the other is set to never, or check on every boot should work when interval is set to never. In my personal opinion, the first choice is the only choice that is interesting for me. Or I think it could be for others too.


    And maybe text should be "Automatically check for updates interval", so there is no doubt there is the interval its about. When you set this to "Never" the text looses its meaning.


    Thanks