littlesat

It looks more that cable provider does not follow the standards...

 

When you put a box in standby in the background cablescan will scan again in the background after a few secs... so when you do now want that, you need to disable cablescan...  Disabling should be possible

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

It was not only me… also pieterg that time prefered to avoid them. Every thing that can be tweaked needs continuously support and makes the stuff complicated and promotes spaghetti code. All the config stuff in the channel selection is a classic example of it.
But at the end for those who want to tweak… at enigma2’it is possible…

In the skin the menu has a limit width and there are items in Dutch language that do not fit. Maybe the translation could be adapted…

Merged.... as far I understood in development image... So the initiator needs to test it in the development image.

Wierd two slightly different iso… a revision with different letters. It can indeed be considered to add the variation.

Thanks…. Also a second infobar is missing and more but it will be done

I agree this is a key one to see what is still free… and indeed find a way to see more recording would be nice. The same for the recording list.

I'm afraid this breaks the fallback timers....Sounds like OWIF needs extra functionality here that also collects the disabled timers.... but the fallback timer is a 'Cool' feature that CoolEPG does not have.......

One issue I have with that is that currently it is for your skin... and adding python code for a special skin is something we should avoid. But the difficult thing here is that it also make other skins more easy in a way that it does not interfere with something as these renderers are stand alone... and it is intend to be used by other skins. So I think we should agree...

Mij lukt het in ieder geval niet om vanuit safari op een ipad een stream te kiezen vanuit de openwebif zodat de telefoon of tablet VLC opent... Daarom gebruik ik meestal de app van GigaBlue of VU+

Better next time ask here and when there are good reasons to upgrade we can do it..We PIN it as sometimes a higher number in oscam could also contain unexpected bugs. Getting it from 'elsewher'e could have risks that it is not working as you did experience.

Maybe we can re-pin

https://github.com/O...92f0f6ebfb03c7b

 

This is what I think bot the idea to go. It looks for my like stripping an image after it is flashed.

 

Image in Slot 0 can still be a real image that can be overwritten when the subdirs are backed up... To add Multiboot in the wizard can be done in a much easier way. Having Screens in standard enigma for VU is also not a real good structured idea... but when you want to do it, you just do it... At least this is something in PLi's 'PEP' we tried to avoid. I was thinking about a mechanism where the slot directories when they are on flash are backed up on the USB or so and moved back to the slot 0 once it is flashed. so to do it in a kind of 'stealthy' way.

 

-or-

 

Together we decide to make a small 'mechanism' that slot 0 will be a real 'recovery' slot.... Then I prefer a small binary that can be executed like ofgwrite with remote control input where you are able to select a slot, download and flash an image via ofgwrite....

 

I do not like that this is getting a person-to-person round instead of cooperative working somehow together.

Please note that this is also something that depends on cross-image stuff....

It is also a bit pitty that some start to code something without getting any agreement.

What is improved mandatory in this version compared what we have now in our feeds?
I’m afraid all what might happen is the binary you find is simply not a good one for openpli or even for your box etc…

Did you get your oscam from our feeds?