Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[ViX_Misc] EPG files test, phase 2: Button mods

Attached are latest set of files.

Fixes the crash that was reported earlier.
Allows usage of Ch+/CH- for paging. Default is 24hour jumps
The number selection that AndyBlac added to Enhanced EPG 7 years ago has been extended to apply to Grid EPG. Option is currently called "Number buttons mode", default is off. It works without issue on the bouquet you are in.

EDIT:
Also with the OK button change referred to below


Some skin changes are required to fully support these. Draft files attached and go in /usr/share/enigma2/

Change log here
https://github.com/SimonCapewell/enigma2/commits/epg-custom-buttons
 
Last edited:
Up and running ok here.

Can I make a suggestion about the ok button in grid epg. I'm used to it giving program info, rather than zapping. Any chance of that option?
For me, the info key is awkward whereas the navigation buttons are all together.
Long press could still zap.

Daft question....

Pressing back moves the selection back to the current time, then the service the EPG opened on
On grid and multi EPGs a third press moves the selection to the first service

What's the back button?
 
Last edited:
.... found the back button, but I don't think all remotes have one.
 
Not all remotes are the same, so it is an impossible task to make something that will work for everyone. Those without a button won't benefit from additions and will function the same as now. Just like how Vu receivers lose out on info/epg differences. I don't have a Help or back button on my remote. The info button is in near middle though.

Rewind/FFWd buttons do nothing in EPG, most remotes have them. One of the main issues was that people don't know what the buttons do. To me, adding more button functions just adds to complexity. There has to be a balance/compromise.
 
To me, adding more button functions just adds to complexity. There has to be a balance/compromise.
Adding another option to ok would make no difference to the complexity - it's already in the menu and, like all the alternatives, you use them if you want to.
There are already hundreds of permutation and combinations.
 
I was commenting about the back button. Only consideration I see with the OK button is how it will interact with the preview mode function.
 
I was commenting about the back button. Only consideration I see with the OK button is how it will interact with the preview mode function.

OK :)

I wouldn't use the back button anyway. I don't use preview mode either, but clearly it would need to be catered for.
 
I can't think of a reason for not allowing info on OK, it does make a rather convenient pairing with the event view, which closes when you press OK. So, we'll have zap, zap+exit or show more info. It's just a matter of choosing a sensible subset of available actions that fit with the general theme of the button. I'll add it unless anyone can think of a solid objection. Preview mode would still be catered for on whichever button you put a zap action on.

In a few places, OpenVix doubles up button functions where there's a dedicated button for it (Green and Timer is the one that immediately springs to mind). When you've got a labelled button, you tend to use it rather than the mysterious Green, even though you know it opens timers. The rationale for adding Back (some remotes it might be recall) is that when you've got the numbers set for jumping to a channel, it's hard to get back to the current channel or time, so it's a kind of hybrid of 5 and 0, toggling between the two.

I do rather wish was consistent was the buttons for paging. In most places it's left and right, in config it's ch+/ch- and in the Grid EPG it's 2 and 8. You could perhaps use FFWD and RWD, but who would reach for that when left and right is already under the thumb? Abu is correct about striking a balance.

You can grab the updated file from here if you want to try it out

Code:
https://raw.githubusercontent.com/SimonCapewell/enigma2/epg-custom-buttons/lib/python/Screens/EpgSelectionBase.py
 
... nice one, thanks for that, working fine !!

What a difference, for me, at least. :)
 
Yes, it's amazing what a difference it makes having buttons set up a bit more ergonomically. More or less impossible to do by default thanks to the multitude of remotes, it's always going to be a compromise for someone.
 
Attached are latest set of files.

Fixes the crash that was reported earlier.
Allows usage of Ch+/CH- for paging. Default is 24hour jumps
The number selection that AndyBlac added to Enhanced EPG 7 years ago has been extended to apply to Grid EPG. Option is currently called "Number buttons mode", default is off. It works without issue on the bouquet you are in.

Some skin changes are required to fully support these. Draft files attached and go in /usr/share/enigma2/

Change log here
https://github.com/SimonCapewell/enigma2/commits/epg-custom-buttons
Thank you for this. Great so far, no issues :)

I use the Confluence skin which common skin is vixbmc_1080_common.

What do I need to change to introduce the number button mode so it works on skin I use?
 
Thank you for this. Great so far, no issues :)

I use the Confluence skin which common skin is vixbmc_1080_common.

What do I need to change to introduce the number button mode so it works on skin I use?
Like maybe, if possible, using skin_user.xml file in /etc/enigma2 :)
 
I've made a start on skin updates, which you can see here

Code:
https://github.com/OpenViX/skins/pull/63/files
 
Attached are latest set of files.

Fixes the crash that was reported earlier.
Allows usage of Ch+/CH- for paging. Default is 24hour jumps
The number selection that AndyBlac added to Enhanced EPG 7 years ago has been extended to apply to Grid EPG. Option is currently called "Number buttons mode", default is off. It works without issue on the bouquet you are in.

Some skin changes are required to fully support these. Draft files attached and go in /usr/share/enigma2/

Change log here
https://github.com/SimonCapewell/enigma2/commits/epg-custom-buttons

Seems to work nicely added into 5.3.034.
Unexplained weirdness I had with 5.3.034 before is gone.
Thanks.
 
IMO just adding it to the emergency skin will ensure it shows for everyone. It can then be tweaked for other skins.
 
Can you point me in the right direction? Doesn't seem to be an emergency.xml or emergency/skin.xml
 
IMO just adding it to the emergency skin will ensure it shows for everyone. It can then be tweaked for other skins.
Can it be added to emergency/default skin? If it's requires specific settings of where to place things (ie x and y co-ordinates), can that be done as a universal answer for short term?
 
WTH?
Why does "Behaviour when a movie reaches the end" keep getting changed to "Return to previous service"?
Could that be due to these new tests or is it a problem with 5.3.034?
 
Attached are latest set of files.

Fixes the crash that was reported earlier.
Allows usage of Ch+/CH- for paging. Default is 24hour jumps
The number selection that AndyBlac added to Enhanced EPG 7 years ago has been extended to apply to Grid EPG. Option is currently called "Number buttons mode", default is off. It works without issue on the bouquet you are in.

EDIT:
Also with the OK button change referred to below


Some skin changes are required to fully support these. Draft files attached and go in /usr/share/enigma2/

Change log here
https://github.com/SimonCapewell/enigma2/commits/epg-custom-buttons

With the number zap I've noticed this only works for typing numbers in the current bouquet. If I'm in entertainment and try 301 for sky Premiere it doesn't seem to move to that channel.

If I'm in entertainment I can type 135 for E4 HD and that works
 

OpenViX Feeds Status

Back
Top