2022 replies to this topic

[littlesat]

That is not what I meant…. I mean the bouquet name in the title…. It stops in the middle while it can go upto the time…

[DimitarCC]

I am not sure i get it....Can you provide some screenshots?

[littlesat]

Not easy where I am right now…. 

[WanWizard]

I will check that...but i think that is IMDB plugin issue....since it hides it.

I see. It seems to do that because of the fact in the PLi skin, it has a PiG on the left.

 

This is not great, it leaves a massive gaping hole on the left now...

Attached Files

•  1_0_19_22C5_80D_2_11A0000_0_0_0_20240201115026.jpg   161.11KB   3 downloads
•  1_0_19_22C5_80D_2_11A0000_0_0_0_20240201115036.jpg   114.84KB   3 downloads

[WanWizard]

Well that screens share one template so changing the font is for all screens.

 

And that can't be dealt with?

 

This is not very handly, on most of the screens, the monospace font looks odd and out of place.

[DimitarCC]

 

I will check that...but i think that is IMDB plugin issue....since it hides it.

I see. It seems to do that because of the fact in the PLi skin, it has a PiG on the left.

 

This is not great, it leaves a massive gaping hole on the left now...

 

 

Definitely not... But we should blame the imdb plugin maker for that Why poster should be hidden? I dont get it.

[DimitarCC]

 

Well that screens share one template so changing the font is for all screens.

 

And that can't be dealt with?

 

This is not very handly, on most of the screens, the monospace font looks odd and out of place.

 

 

Can be....But that means one more template just for 2 screens (in PLi) in ViX for example screens are different and there is not required at all

[WanWizard]

I don't have enough development skills or knowledge to comment on either .  Maybe someone else?

[littlesat]

This is not very handly, on most of the screens, the monospace font looks odd and out of place.

 

->

 

I think we better can add a different screen for the screen where you need a monospace font for... bur this also means we need to make a change in the code so it first tries the monospace variant and then the legacy. The skin 'stuff' can put screens in a list and take the first that fits...

 

So I suggest create a special screen for the monospace and name it e.g. the same name with _monospace in the screen name and then arrange in python in the skins list that this specific screen is preferred (to stay compatible with all other skins).

 

(what is different in Vix?..... I think change the font hardcoded is also obvious)

Edited by littlesat, 1 February 2024 - 15:08.

[Huevos]

This is not very handly, on most of the screens, the monospace font looks odd and out of place.

 

->

 

I think we better can add a different screen for the screen where you need a monospace font for... bur this also means we need to make a change in the code so it first tries the monospace variant and then the legacy. The skin 'stuff' can put screens in a list and take the first that fits...

 

So I suggest create a special screen for the monospace and name it e.g. the same name with _monospace in the screen name and then arrange in python in the skins list that this specific screen is preferred (to stay compatible with all other skins).

 

(what is different in Vix?..... I think change the font hardcoded is also obvious)

Change in the code for what? The fixed width font is listed in the top of the skin and then required by the widget. If the font definition is missing the regular font is selected automatically.

[littlesat]

Change in the code for what?

->

To tell the skin for which screen it should take normal font and for which screen monospace font...

[athoik]

@DimitarCC, Very nice work! Kudos!

 

I would like to bring into your attention that changes to eSlider might cause issues to scanning progress bar.

As a friend informed me, the progress bar when scanning channels, with latest version seem like, no progress, stacked on 100%.

 

I need to confirm if that happens with your skin or it happens with old skins.

 

Anyway, keep up the nice work.

 

 

Did the friend recently update. As far I can see the progress bars should be fine now.

 

 

Will check it, maybe it was an older version of e2. Building the latest develop branch and will get proper feedback.

@DimitarCC it seem that problem was on SatDreamGR skin.

 

https://github.com/s...85d281807ddba36

 

borderColor="blue" and backgroundColor="blue" was the problem.

 

Working before, maybe after https://github.com/O...803a3c73a4d57ab stopped?

 

No idea if the problem was blue on blue, or indeed some of the changes had a side effect.

 

If you can understand what was the problem, please be my guest.

[DimitarCC]

So in my opinion the problem was 

backgroundColor="blue" foregroundColor="blue"

With the old c++ code backgroundColor was not taken at all and threated as transparent/default. So it was not important what you will define for background color.

 

With the latest c++ changes however that matters. And when both are blue it just cant be understood what the real progress is.

 

foregroundColor specify the progress color, backgroundColor specify the remaining part (till 100%) of the progress.

 

So changing background color actually fixed the issue and progressbar now working fine.

[athoik]

Nice, thanks for the explanation!

[Huevos]

Change in the code for what?

->

To tell the skin for which screen it should take normal font and for which screen monospace font...

The font is specified in the skin widget. Why would you need to force something in the python code?

[Frenske]

@DimitarCC

I just tested QuadPIP for another user and noticed that in the default skin the text in QuadPIP is hard to read from a distance of about 3.5 meters. I really don't know whether this is a side-effect of your changes in your E2-darkOS skin but I can't rule out this too. I have added two screenshots. One with your skin and one with the default skin.

 

      IMG_4048.jpeg   255.7KB   3 downloads

The first is with the default skin.               And the second one is with the E2-darkOS skin so the difference is minor.

 

The text near the red button is the most difficult to read on the TV.

 

Possibly this should be changed in the plugin.

 

Hmm, the layout of the message is f*c*edup by some unknown reason.

Attached Files

•  IMG_4047.jpeg   219.93KB   3 downloads

[DimitarCC]

@DimitarCC

I just tested QuadPIP for another user and noticed that in the default skin the text in QuadPIP is hard to read from a distance of about 3.5 meters. I really don't know whether this is a side-effect of your changes in your E2-darkOS skin but I can't rule out this too. I have added two screenshots. One with your skin and one with the default skin.

 

IMG_4047.jpeg      IMG_4048.jpeg

The first is with the default skin.               And the second one is with the E2-darkOS skin so the difference is minor.

 

The text near the red button is the most difficult to read on the TV.

 

Possibly this should be changed in the plugin.

 

Hmm, the layout of the message is f*c*edup by some unknown reason.

 

The problem is in QuadPiP definition.....

<widget name="key_red" position="15,60" zPosition="1" size="140,40" font="Regular;20" halign="center" valign="center" backgroundColor="#9f1313" foregroundColor="#ffffff" transparent="1" />
<widget name="key_green" position="185,60" zPosition="1" size="140,40" font="Regular;20" halign="center" valign="center" backgroundColor="#1f771f" foregroundColor="#ffffff" transparent="1" />
<widget name="key_yellow" position="355,60" zPosition="1" size="140,40" font="Regular;20" halign="center" valign="center" backgroundColor="#a08500" foregroundColor="#ffffff" transparent="1" />
<widget name="key_blue" position="525,60" zPosition="1" size="140,40" font="Regular;20" halign="center" valign="center" backgroundColor="#18188b" foregroundColor="#ffffff" transparent="1" />

As you can see on all texts is set transparent="1". That is very bad since that enable transparency with alphatest and NOT "blend". So you can see through the text.  There is no point specify backgroundColor="#9f1313" and transparent="1".

That is the actual problem.

That can be fixed if there is skin definition for that screens in the active skin. Or the default skin of QuadPiP screens have to be fixed in the plugin.

[littlesat]

In the channelselection in move mode the background is orrange, while the text is red... this makes it somehow unreadable.

 MoveMode.jpg   142.7KB   3 downloads
And this is what I meant with the title in the channelselection screen... I suggest we can free the room up to the clock..

 chanelselection.jpg   54.17KB   3 downloads

Edited by littlesat, 2 February 2024 - 11:34.

[DimitarCC]

In the channelselection in move mode the background is orrange, while the text is red... this makes it somehow unreadable.

MoveMode.jpg
And this is what I meant with the title in the channelselection screen... I suggest we can free the room up to the clock..

chanelselection.jpg

 

About orange color it doesnt look like that on my side. Still i think there is difference in contrast in the way it appears on my side and yours.

However i am not sure what color can be used since the text color is red so red cant be used for the selection.

 

Regarding the title i will see can that be done easily since that title have to be dynamic because is in one and the same for all screen sizes

[WanWizard]

But the screenshot is a binary dump of the framebuffer, and in the screenshot the red on orange is unreadable.

 

So if it is different in your preception, it is (the setup of) your TV that is the problem?