![Photo](https://secure.gravatar.com/avatar/871c591a198380d02642032f8861fe87?s=100&d=https%3A%2F%2Fforums.openpli.org%2Fpublic%2Fstyle_images%2Fmaster%2Fprofile%2Fdefault_large.png)
[WIP] PLi-DarkOS Skin
Re: [WIP] PLi-DarkOS Skin #1801
Posted 20 April 2024 - 16:33
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Re: [WIP] PLi-DarkOS Skin #1802
Posted 20 April 2024 - 19:12
Won't be the first time...
However, that knowledge doesn't fix the issue, we can't have it crash when we move to OpenPLi 10.
Where exactlly is the number of pages in a screen and the position of those paging dots calculated? As it might be related, in Kirkstone these dots are all left-aligned and on top of each other (so only one is visible).
I currently have no idea where to start debugging.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: [WIP] PLi-DarkOS Skin #1803
Posted 21 April 2024 - 10:41
There are several functions that collect the data and do the maths. You can put a print there so to log the output on every step.
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Re: [WIP] PLi-DarkOS Skin #1804
Posted 21 April 2024 - 11:36
Re: [WIP] PLi-DarkOS Skin #1805
Posted 22 April 2024 - 15:18
Thanks.
This means we need to branch develop to kirkstone for enigma2, as these changes are incompatible with Python 3.9 in develop.
edit:
Done. So from now on Python 3.10+ specific fixes can go into the Kirkstone branch. Please don't forget to rebase every now and then .
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: [WIP] PLi-DarkOS Skin #1806
Posted 22 April 2024 - 15:39
Thanks.
This means we need to branch develop to kirkstone for enigma2, as these changes are incompatible with Python 3.9 in develop.
edit:
Done. So from now on Python 3.10+ specific fixes can go into the Kirkstone branch. Please don't forget to rebase every now and then
.
Off topic for this thread but you might want to look at this:
https://github.com/O...0ff4a830f9eb979
Re: [WIP] PLi-DarkOS Skin #1807
Posted 22 April 2024 - 15:58
Branch had to happen anyway
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: [WIP] PLi-DarkOS Skin #1808
Posted 3 May 2024 - 13:47
@DimitarCC just a pointer, I am missing the menu button in de bar below of AutoBackup screen. It works, it's only not displayed in the bar below.
Attached Files
Hardware: Vu+ Uno 4K SE - Vu+ Duo 4K - Fuba 78 cm - Tripleblock LNB Quad 19.2/23.5/28.2 - DS918+
Software : OpenPLi - OSCam - Settings van Hans - Autotimer - EPGImport
---------------------------------------------------------------------------------------------------------------------------------------
Remember: Upvote with the button for any user/post you find to be helpful, informative, or deserving of recognition!
---------------------------------------------------------------------------------------------------------------------------------------
Many answers to your question can be found in our new and improved wiki
Re: [WIP] PLi-DarkOS Skin #1809
Re: [WIP] PLi-DarkOS Skin #1810
Posted 6 May 2024 - 15:27
Can you please add this screen. Might need a lot of fine tuning as there might be a lot of wishes...... but it demonstrates at least the functionality and proves the idea works...
<!-- InfoBarAdds --> <screen name="InfoBarAdds" title="InfoBarAdd" position="38,38" size="1145,160" backgroundColor="transparent" flags="wfNoBorder"> <eLabel position="0,0" size="1145,160" zPosition="-11" backgroundColor="background5" cornerRadius="12"/> <eLabel position="2,2" size="1141,156" zPosition="-10" backgroundColor="background" cornerRadius="10"/> <widget source="session.CurrentService" render="Label" position="10,10" size="1125,35" backgroundColor="background" zPosition="1" foregroundColor="foreground" font="Regular;26" valign="center" halign="center"> <convert type="PliExtraInfo">ServiceInfo</convert> </widget> <widget source="session.CurrentService" render="Label" position="10,45" size="1125,35" backgroundColor="background" font="Regular; 26" zPosition="21" halign="center"> <convert type="CryptoInfo">FullInfo</convert> </widget> <widget source="session.CurrentService" render="Label" position="10,80" size="1125,35" backgroundColor="background" font="Regular; 26" zPosition="21" halign="center"> <convert type="ServiceName">StreamUrl</convert> </widget> <widget source="session.CurrentService" render="Label" position="10,115" size="325,40" backgroundColor="background" zPosition="1" foregroundColor="foreground" font="CAID;36" valign="center" halign="left"> <convert type="PliExtraInfo">CryptoBar</convert> </widget> <widget source="session.FrontendInfo" render="Label" position="980,115" size="150,30" backgroundColor="background" zPosition="1" foregroundColor="foreground" font="CAID;36" valign="center" halign="right"> <convert type="FrontendInfo">USE_TUNERS_STRING</convert> </widget> <widget source="session.FrontendStatus" render="FixedLabel" text="SNR" position="470,115" size="50,30" valign="center" backgroundColor="background" zPosition="2" font="Regular;26"> <convert type="FrontendInfo">SNR</convert> <convert type="ConditionalShowHide" /> </widget> <widget source="session.FrontendStatus" render="Label" position="550,115" size="130,30" valign="center" zPosition="2" backgroundColor="background" halign="right" font="Regular;26"> <convert type="FrontendInfo">SNR</convert> <convert type="ConditionalShowHide" /> </widget> </screen>
Edited by littlesat, 6 May 2024 - 15:33.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: [WIP] PLi-DarkOS Skin #1811
Re: [WIP] PLi-DarkOS Skin #1812
Posted 7 May 2024 - 10:15
.... I hope soon to find time to add something to a weather plugin that instantly can add a screen in the same way.... without renderers etc...
I also know there might be more wishes... Now I only show SNR.... I think this is sufficient (we also had this only right from the infobar in our standard skin)
I also like you can instantly enable/disable it without going to a menu...
And we also get now conditional setup when specific screens in skins do exist...
Edited by littlesat, 7 May 2024 - 10:17.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: [WIP] PLi-DarkOS Skin #1813
Posted 9 May 2024 - 20:16
Just flashed a new kirkstone image, build 2 hours ago. And guess what is back, after it was fixed in the previous version (1/5 build):
TypeError: 'float' object cannot be interpreted as an integer The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry if len(sequence) == 0: SystemError: <built-in function len> returned a result with an exception set TypeError: 'float' object cannot be interpreted as an integer The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/enigma2/python/Components/Addons/ColorButtonsSequence.py", line 52, in buildEntry if len(sequence) == 0: SystemError: <built-in function len> returned a result with an exception set Traceback (most recent call last): File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 806, in updateEventInfo cur = self.getCurrentSelection() TypeError: 'float' object cannot be interpreted as an integer [ePyObject] (CallObject(<bound method SelectionEventInfo.updateEventInfo of <class 'Screens.ChannelSelection.ChannelSelection'>>,()) failed
Other symptomes are the same too, like the dot on multi-page screens all being left-aligned.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: [WIP] PLi-DarkOS Skin #1814
Re: [WIP] PLi-DarkOS Skin #1815
Re: [WIP] PLi-DarkOS Skin #1816
Re: [WIP] PLi-DarkOS Skin #1817
Posted 10 May 2024 - 06:38
Some fixes for MainMenu addon here https://github.com/O...igma2/pull/3973
Vu+DUO4KSE, DM920UHD, Vu+Uno4KSE, SF8008Mini, 2xPulse4K, Vu+Solo2, Dreambox DM500HD, Triax 78 (7E,9E,13E,19.2E,23.5E) & 2xTriax 78 (39E)
Re: [WIP] PLi-DarkOS Skin #1818
Re: [WIP] PLi-DarkOS Skin #1819
Posted 10 May 2024 - 10:56
I have no idea what can cause this.....Since you said was fixed what made it come back?
I have absolutely no idea.
Huevos mentioned the Python 3.10 issues, and I've implemented those workarounds here: https://github.com/O...39d786a15709080
which fixed it. I rebased with develop yesterday, so this is the only difference between kirkstone and evelop, but now it's back?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: [WIP] PLi-DarkOS Skin #1820
Posted 10 May 2024 - 13:25
I've rebuild, double checked that E2 is build from the correct branch and commit hash (it is, f95df02), but the problem persists...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users