Jump to content


Photo

[WIP] PLi-DarkOS Skin


  • Please log in to reply
2057 replies to this topic

Re: [WIP] PLi-DarkOS Skin #621 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 08:30

Can you try to put the two next to eachother.
Due to in oe-a the code was merged it is more difficult to see there what’s happening in the gmepg…. This is a small disadvantage from this merge, but it was done to show gmepg in the infobar that time (which looks as x-mass tree).

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #622 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 08:33

I only see it in ‘big’ style…. Can’t make a screenshot now
What do you mean with the space?
When there is no path it is fine.

Edited by littlesat, 2 December 2023 - 08:34.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #623 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 08:45

I mean if the ScreenPath is " " and not "" (string with a space in it instead of empty string) it will still think is there. But i guess that is not the case....

 

However i see a difference in logic for ScreenPath in PLi.....

 

In PLi:

if showPath and (config.usage.showScreenPath.value == "large" or self.noScreenPathSource) and title:
	screenPath = ""
	screenTitle = "%s > %s" % (self.screenPath, title) if self.screenPath else title
elif showPath and config.usage.showScreenPath.value == "small":
	screenPath = "%s >" % self.screenPath if self.screenPath else ""
	screenTitle = title
else:
	screenPath = ""
	screenTitle = title

In OpenViX:

if showPath and config.usage.showScreenPath.value == "large" and title:
	screenPath = ""
	screenTitle = "%s > %s" % (self.screenPath, title) if self.screenPath else title
elif showPath and config.usage.showScreenPath.value == "small":
	screenPath = "%s >" % self.screenPath if self.screenPath else ""
	screenTitle = title
else:
	screenPath = ""
	screenTitle = title

It seems in PLi if there is self.noScreenPathSource it switches to large mode.... That is different on ViX for example since that part of code is not there.

Thats why you see it large only.

 

Why it is switched to large version when self.noScreenPathSource == True?


Edited by DimitarCC, 2 December 2023 - 08:46.

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 #624 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 08:50

Can you try to put the two next to eachother.
Due to in oe-a the code was merged it is more difficult to see there what’s happening in the gmepg…. This is a small disadvantage from this merge, but it was done to show gmepg in the infobar that time (which looks as x-mass tree).

 

I cant make a screenshot from PLi at the moment....

 

But here is @WanWizard screenshot...The differences are obvious ;)

 

Attached File  graphmultiepg.jpg   144.76KB   0 downloads

 

Attached File  pligmepg.jpg   138.86KB   0 downloads

 

 

Pli GMEPG doesnt have the separation border lines (in graphics mode) and colors sometimes look washed out.

Also PLi GMEPG doesnt have a setting to manually switch between text and graphics mode...It automatically switch to graphics mode if there are images in skin folder epg subfolder.


Edited by DimitarCC, 2 December 2023 - 08:58.

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 #625 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 08:56

Regarding the path… that was changed recently as work a round for this skin. Sounds like this can be reverted :)

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #626 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 08:58

Regarding the path… that was changed recently as work a round for this skin. Sounds like this can be reverted :)

 

Yes it have to be reverted and then it should work as expected.


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 #627 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 08:59

In pli we hate to add configs to tweak stuff for skins. In our standard skin there are pngs behind it so border stuff is not needed. Maybe to make it compatible add them as well these graphs.

Edited by littlesat, 2 December 2023 - 08:59.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #628 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 09:01

In pli we hate to add configs to tweak stuff for skins. In our standard skin there are pngs behind it so border stuff is not needed. Maybe to make it compatible add them as well these graphs.

 

Yes because i can not add borders to the images since it will duplicate the border in OE-A. Maybe the only way to be compatible is to add the borders in PLi?


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 #629 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 09:03

But also in openpli I see borders…. But with low contrast and extreme small. I hope you can help to add them…sorry I do not have that much time you have…

Edited by littlesat, 2 December 2023 - 09:05.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #630 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 09:05

That is maybe because there is small gap between the images in two rows....And under the lines are seen.Maybe if the gap is bigger and lines color brighter it will work...


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 #631 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 09:06

 I hope you can help to add them…sorry I do not have that much time you have…

 

I will do my best for that. But i also dont have so much time either...I do that in gaps from my real work and in weekends when possible. ;)


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 #632 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 09:21

It is at least clear why we have a difference…

Edited by littlesat, 2 December 2023 - 09:24.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #633 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 10:27

So here a pull proposal...But have to be tested how exactly behaves...So if someone is possible to test please report.

 

https://github.com/O...igma2/pull/3855


Edited by DimitarCC, 2 December 2023 - 10:28.

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 #634 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 11:30

I merged it so everyone can test it after a rebuild omg what a huge thing…. Maybe that is why I never implemented it as we did it by the picture

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #635 Frenske

  • Forum Moderator
    PLi® Core member
  • 27,507 posts

+397
Excellent

Posted 2 December 2023 - 11:57

@DimitarCC

Is it possible to create a minor gap of about 1 mm between the shown items in the GMEPG?


Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: [WIP] PLi-DarkOS Skin #636 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 12:02

Generally is possible but can you post a screenshot and mark where you want a gap?


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 #637 Frenske

  • Forum Moderator
    PLi® Core member
  • 27,507 posts

+397
Excellent

Posted 2 December 2023 - 12:10

Here you are. Between all shown items there is a minor gap to show the end and the beginning of the item. 
 

Attached File  IMG_0492.jpeg   191.59KB   0 downloads


Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: [WIP] PLi-DarkOS Skin #638 littlesat

  • PLi® Core member
  • 57,434 posts

+708
Excellent

Posted 2 December 2023 - 12:11

I thought this was exactly created here…

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: [WIP] PLi-DarkOS Skin #639 DimitarCC

  • PLi® Contributor
  • 1,584 posts

+71
Good

Posted 2 December 2023 - 12:23

Yes with the last pull it should add a borders around it so it will be visible where it starts and where it ends. Did you tried the last merge?


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 #640 elsato

  • Senior Member
  • 636 posts

+27
Good

Posted 2 December 2023 - 12:26

Hi,

 

Adding a channel to a bouquet gives me this error with e2darkos skin (git129). With the default PLi skin there is no error message.

 

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
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 714, 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)
 



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users