2041 replies to this topic

[littlesat]

Multytranscoding can do more than one transcoding which is 2? Or 3?

Edited by littlesat, 23 December 2023 - 21:33.

[WanWizard]

Why would that require a different plugin ( or even a plugin at all ) ?
 

The docs are useless:

multitranscoding:

	BoxInfo.getItem("multitranscoding")

		This variable defines if a receiver supports multi transcoding feature.

	Example: True

[Pr2]

Why is the marked section twice in the About?

 

There is indeed something weird here.

 

If you are in the about screen the two bullet means that they will scroll down.

But if you are in a contextual menu (pressing menu to get the different possible action) it page down and not scroll.

 

To reproduce: go into the channel list select a channel and press the menu button, you will see 2 bullets and the right arrow will page down and not scroll down.

Go into the About screen and press the right arrow it will scroll down.

 

So I think that the behaviour should be more coherent either scroll when the second page is not full or use a true paging system, but mixing both can be confusing.

[littlesat]

Yes we know and it always worked like this. It is enigma2!

[Huevos]

 

Why is the marked section twice in the About?

 

There is indeed something weird here.

 

If you are in the about screen the two bullet means that they will scroll down.

But if you are in a contextual menu (pressing menu to get the different possible action) it page down and not scroll.

 

To reproduce: go into the channel list select a channel and press the menu button, you will see 2 bullets and the right arrow will page down and not scroll down.

Go into the About screen and press the right arrow it will scroll down.

 

So I think that the behaviour should be more coherent either scroll when the second page is not full or use a true paging system, but mixing both can be confusing.

 

You are not comparing like for like. One is a list, the other is a block of text (ScrollLabel). But anyway why are you interested in this now? It is the way it has always been.

Edited by Huevos, 24 December 2023 - 22:48.

[Pr2]

I always use the default OpenPLi skin so I never had the need to scroll in the about screen since everything was displayed on the same screen.

So I never point out the different behaviour before.

I mainly use the About screen when I want to see the IP address assign to the box.

[littlesat]

Good point fist it most time fits and now most time you need to scroll. But we can look at it.

[Huevos]

Instead of having all that info in one screen maybe you could split it like in other images.

Attached Files

•  1.jpg   80.19KB   3 downloads
•  2.jpg   62.81KB   3 downloads
•  3.jpg   46.08KB   5 downloads
•  5.jpg   50.67KB   4 downloads

Edited by Huevos, 25 December 2023 - 01:40.

[littlesat]

Originally it waa intended to get one overview with the most imported stuff and we had most times it on one page. Split it has also disadvantages. A longer information menu I suppose. Other images show also more and more and more information. All color buttons are already occupied there. But reorganize stuff there might be a good idea. But you never can made it good I’m afraid. To split it is an easy task. But maybe someone else has a better idea.

Edited by littlesat, 25 December 2023 - 08:04.

[littlesat]

@dimitarCC can you please consider to change the icons that blink to 4000,1000?

[DimitarCC]

Well that is almost steady behavior...So i dont know. Personally i dont like it much.... 

[littlesat]

Can you please try for at least a couple of weeks and then evaluate it?

 

....It is indeed more steady... but it still blinks, but less aggressive. And no need to do configs etc...

 

I know I made a micro issue about this and subjective. But the skin gives you a non aggressive impression... Then the flashing each second on/off icon looks aggressive... We used this kind of flashing stuff e.g. in displays.

 

The info is recording... that it also does with non flashing... but the flashing should not making you nervous when you choose a skin that looks non aggressive...

 

When you never try to change and get stuck to what you were used to then you never experience what might be better...  I understand and most of the enigma2 users are used to the flashing things... but be aware at the end when you are used to non flashing things you will think differently about it.

 

E.g. in the channellist for example they also do not flash...

 

One other thin. The cursor in the GMEPG needs a more different color... maybe also change the color of the font or so to get more attention to it. With lower contrast situations especially you do not easily see the 'cursor'.

Edited by littlesat, 27 December 2023 - 15:08.

[DimitarCC]

Yes OK. Seems OE-A images doesnt understand 

<convert type="ConditionalShowHide">Blink,4000,1000</convert>

So on that images it blinks like default....But PLi understand it...

 

OK i will add that to the skin.

 

But i dont get the issue with the GMEPG....

 

What is not visible? On my TV there is big contrast between non selected and selected item....

[littlesat]

It is visible but the contrast between the green current, the black and the gray background is low. So you do not clearly see what event is selected. I understand it is likely the same gray (I did not check it yet) as in channel selection and other lists. Maybe giving it a lighter color, change the font color of the event and/or add a colored border makes it more visible. Unless this at least the coloring could be better here
Also current event and current playing service has the same green color we had green for current playing arrive and blue for current playing event and a lighter blue with yellow font for the selected cursor event. Having two different colors for the green stuf might also already help

Edited by littlesat, 27 December 2023 - 15:40.

[Ev0]

 

Some HiSi doesnt suffer from that issues or at least not so visible. Like qviart dual 4K as reported

 

What is "that issue"? As the movie I posted was exactly from a Qviart Dual 4K.

 

Sorry for late reply, I haven't been following the posts.

The issue you posted was fixed back in August after a lot of pestering Qviart to fix it.

IIRC this driver update fixes it.

https://github.com/o...6794fb109874143

 

EDIT: It was actually the update before that one, that fixed the skin issue.

Edited by Ev0, 29 December 2023 - 23:51.

[Huevos]

And now PLi BoxInfo is no longer compatible with OE-A images.

 

https://github.com/O...03125ca3cb580af

 

If you are going to make changes like this we might as well give up trying to be compatible.

 

And also the use of "eval" is a terrible idea. How can you be sure of what is in enigma.info? Well the answer is you can't because you are not in control of the source.

Edited by Huevos, 30 December 2023 - 10:33.

[littlesat]

The eval is a nice idea as it avoid the exceptions you did create. The same mechanism I already used in hotkey. It looks eval, but it allowed to use python syntax here and reduced the code while it extend it to more stuff and also standardize it. But it also sounds like a tradition that when it is not coming from you it is most times wrong.
Why did you add writing to SystemInfo stuff there? That is totally not clear to me as the idea was to get rit of systeminfo, so why do you add it there with a risk overwriting an already existing systeminfo key there? That was why I removed it. And it does not break anything regards compatibility unless something is still trying to obtain something via SystemInfo. Via infobox getItem you still get it.
And note my code cannot be hacked by hacking into BoxInfo.boxInfo… and the checksum is checked….
Please explain and open discussion. The eval for example is simply there as it defined a standard instead of making exception on exception on exception so you got exploding code.
Next step is fixing the booleans……

[DimitarCC]

I think the problem is that some things still read systeminfo 8n other distros and removing it may cause incompatibilities...

[littlesat]

Why is that a problem… when we try to avoid it.
To retrieve something with getItem from SystemInfo is fine for me.
But poking something back to it and actually store things twice with a risk overwriting something draws to me yellow flag. I was doubting about it but I could also not find something that used it… so I was free to remove it.

Edited by littlesat, 30 December 2023 - 12:12.

[Huevos]

Question is do you want compatibility or not. In oe-a we can write to boxinfo and immediately that data is available to all running processes by SystemInfo. Your commit breaks a behaviour that is expected and that has been in force several years.

And the eval is plain wrong because a string in enigma.info could match something in the namespace. It is lazy coding. And right now you don't seem to understand you are not in control of the contents of enigma.info.