2041 replies to this topic

[littlesat]

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).

[littlesat]

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.

[DimitarCC]

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.

[DimitarCC]

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

 

 graphmultiepg.jpg   144.76KB   0 downloads

 

 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.

[littlesat]

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

[DimitarCC]

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.

[littlesat]

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.

[DimitarCC]

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?

[littlesat]

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.

[DimitarCC]

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...

[DimitarCC]

 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.

[littlesat]

It is at least clear why we have a difference…

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

[DimitarCC]

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.

[littlesat]

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

[Frenske]

@DimitarCC

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

[DimitarCC]

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

[Frenske]

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

 IMG_0492.jpeg   191.59KB   0 downloads

[littlesat]

I thought this was exactly created here…

[DimitarCC]

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?

[display name]

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)