30.06.2010 Version 2.7
SecondInfoBar for all skiners and all images
SecondInfoBar] for all skins and all images
Many colleagues override skin for Second Infobar OK button repeatedly InfoBarGenerics.py.
I've done it, but I must say:
Very bad idea!
One should not change in Enigma2-Python Core.
Dafon very many bad surprises
I sat down and tried a SecondInfoBar OK button as pure plug
to write WITHOUT having to change InfoBarGenerics.py.
And it works
WARNING!
Now, if everyone does his own skin with its skin plugin for SecondInfoBar,
we will get conflicts when multiple skins are installed with SeconInfoBar!
That would be good if we agree, and always use the same plugin
In principle the use is easy!
You install the plugin and starts the new GUI.
For second time, press OK I get the message that your skin
the SecondInfoBar untrstützt not. (picture 1) Sure, we still have no screen.
In principle, this is THE SeconInfoBar only is currently empty.
Again, this is easy!
Paste into skin.xml a new screen:
Code:
<screen flags="wfNoBorder" name="SecondInfoBar" position="center,350" size="720,200" title="Second Infobar">
<eLabel text="Your skin do not support SecondInfoBar !!!" position="0,0" size="720,200" font="Regular;22" halign="center" valign="center"/>
</screen>
You can now screen all possible in these converters, renderers, or
Sources include
(Dafon's enough anyway)
I have tried it in CVS-based image and it goes well
1xOK InfoBar screen (Figure-2) and 2xOK SeconInfoBar screen (Figure 3)
If all images are run, with some like LT or something like Nabilo
not need
For CVS, Merlin, Excalibur, OoZooN ICVS, Gemini, etc. but
interesting.
And something here is very good!
If you do not want Infobar Second, one must only remove the plug
Since we do not run SecondInfoBar of skin.xml and disturbs
update: 30.06.2010 Version 2.7:
In working mode "show EPG List" is recognized od MerlinEPG installed
and if so this started, if not the standartEPGliste started.
SecondInfoBar for all skiners and all images
SecondInfoBar] for all skins and all images
Many colleagues override skin for Second Infobar OK button repeatedly InfoBarGenerics.py.
I've done it, but I must say:
Very bad idea!
One should not change in Enigma2-Python Core.
Dafon very many bad surprises
I sat down and tried a SecondInfoBar OK button as pure plug
to write WITHOUT having to change InfoBarGenerics.py.
And it works
WARNING!
Now, if everyone does his own skin with its skin plugin for SecondInfoBar,
we will get conflicts when multiple skins are installed with SeconInfoBar!
That would be good if we agree, and always use the same plugin
In principle the use is easy!
You install the plugin and starts the new GUI.
For second time, press OK I get the message that your skin
the SecondInfoBar untrstützt not. (picture 1) Sure, we still have no screen.
In principle, this is THE SeconInfoBar only is currently empty.
Again, this is easy!
Paste into skin.xml a new screen:
Code:
<screen flags="wfNoBorder" name="SecondInfoBar" position="center,350" size="720,200" title="Second Infobar">
<eLabel text="Your skin do not support SecondInfoBar !!!" position="0,0" size="720,200" font="Regular;22" halign="center" valign="center"/>
</screen>
You can now screen all possible in these converters, renderers, or
Sources include
(Dafon's enough anyway)
I have tried it in CVS-based image and it goes well
1xOK InfoBar screen (Figure-2) and 2xOK SeconInfoBar screen (Figure 3)
If all images are run, with some like LT or something like Nabilo
not need
For CVS, Merlin, Excalibur, OoZooN ICVS, Gemini, etc. but
interesting.
And something here is very good!
If you do not want Infobar Second, one must only remove the plug
Since we do not run SecondInfoBar of skin.xml and disturbs
update: 30.06.2010 Version 2.7:
In working mode "show EPG List" is recognized od MerlinEPG installed
and if so this started, if not the standartEPGliste started.