Single EPG: highlight day change

[adoxa]

Would the few Single EPG users be interested in this? It uses yellow (currently hardcoded, no option) for the entry when the day changes.

[Star6key]

How about alternating the colour for the whole day's listing? (ie 1st day white, 2nd day yellow, 3rd day white... etc)

[adoxa]

I don't know, you don't think that'd be a bit much?

[adoxa]

Might be alright, after all. Here's a plugin to try it out. Still no configuration, install the plugin to use it, remove it to not (takes effect immediately, restart not required). Done properly there would be an option added to the setup menu and the colour would be set via an attribute in the skin (this yellow would be the default).

[Star6key]

Works fine... although a whole page of that particular shade of yellow on a black background is psychosis inducing.

Something like this would be more soothing. - (#F5F6CE)

[sub3R]

Might be alright, after all. Here's a plugin to try it out. Still no configuration, install the plugin to use it, remove it to not (takes effect immediately, restart not required). Done properly there would be an option added to the setup menu and the colour would be set via an attribute in the skin (this yellow would be the default).

Great work. That particular yellow colour is just right on the black background of both our TVs (2 x U4s running OverlayHD).

That was a good suggestion by Star6key to alternate the days between white & yellow.

Just changing the first time slot at midnight wouldn’t have achieved anything for me. I go through the EPG at breakfast each morning so by the time I go past the single yellow day change at midnight I would be back to white text again - I’m usually getting picked up for scrolling too far through to the following days. This option should help to eliminate that.

The colour option in setup would be good.

[sub3R]

Just thinking about when I go through the EPG at breakfast time to set timers. Is it possible to have the daily colour change time to be user selectable? For example instead of the colour changing at midnight have it so it could be user selectable to change at say 7:00am or 8:00am every day (hourly options) with midnight being the default.

I expect what sounds like a simple suggestion could be a nightmare to achieve.

[prl]

Something like this would be more soothing. - (#F5F6CE)

Not against a white background

[prl]

I expect what sounds like a simple suggestion could be a nightmare to achieve.

There's a useful U*ix function (and Python library function) called localtime() that converts a system time (floating point number in Python) into a tuple (in Python, struct in C) that contains (year, month, day_of_month, hours, mins secs, day_of_week, day_of_year).

It wouldn't be hugely complicated to get the changeover at some time after midnight. I think that you'd just take the "change colour at midnight" code and add the time offset from midnight that you want to the system time for the program you want to colour before using that time and "now" to calculate the colour.

Various different TV guides use different times for "start of day". The printed Canberra Times guide uses 06:00, SBS online uses 05:00, ABC and yourtv.com.au use 00:00 and IceTV uses 23:00 on the previous day, which, I think, point mainly to the fact that a user-configurable colour change time might be useful.

[adoxa]

I could even have two times, as I check it before bed (up to 3pm) and after lunch (up to 12:30am).

[sub3R]

Various different TV guides use different times for "start of day". The printed Canberra Times guide uses 06:00, SBS online uses 05:00, ABC and yourtv.com.au use 00:00 and IceTV uses 23:00 on the previous day, which, I think, point mainly to the fact that a user-configurable colour change time might be useful.

I hadn’t thought of the various TV guides doing that. So yes, it could have other advantages.

[sub3R]

I could even have two times, as I check it before bed (up to 3pm) and after lunch (up to 12:30am).

That's even better. So to select the one colour for each 24hr period (white > yellow > white > yellow … etc.), say from 8:00am on day 1 to 8:00am on day 2 ... etc., it would just mean selecting the same colour for both time span options, am I right?

[adoxa]

That's right. Here it is, as a patch this time (extract it where the Wiz can see it, run epg-transition/setup.sh, restart; repeat to remove). The setup has new option "Highlight transition", which expands to show the times. If the times are the same it's a daily transition, otherwise it transitions at each of the times. The colour is currently a parameter in the skin, add a user skin to change it:

/etc/enigma2/skin_user.xml

Code: Select all

<skin>
  <parameters>
    <parameter name="EPGTransitionColor" value="#F5F6CE" />
  </parameters>
</skin>

[sub3R]

That's right. Here it is, as a patch this time ...

Thanks, I’ll give it a shot sometime tomorrow.

[sub3R]

Thanks, I’ll give it a shot sometime tomorrow.

That works well for the various First & Second hour settings I tried with First & Second minutes set to 0.

I don’t know if First minute & Second minute (in EPG > MENU) do what you intended them to do, but perhaps I’m missing the intention. With First hour & Second hour both set to 09:00 I experimented with various minute settings & as soon I select a minute other than 0 I lose the 09:00 to 09:00 colour change span. I just get the odd single line colour change two to three days ahead. Changing First & Second minutes back to 0 gives me the 24hr daily colour change again.

I noticed that the default #F5F6CE yellow in skin_user.xml comes out a lot lighter than the yellow in your previous plug-in. But that is easily fixed in skin_user.xml.

I used IanSav’s ‘OverlayHD Skin Colour Chart’ I downloaded some time ago from here to experiment with colours. Opening this in the U4 gives a good idea of colours on the TV screen. At this stage I settled on Tan #D2B48C.

Do you intend making this a plug-in?

[adoxa]

[A]s soon I select a minute other than 0 I lose the 09:00 to 09:00 colour change span.

Seems to work okay for me. I did neglect to reset the seconds to 0, but that still shouldn't have done what you saw. I've changed the option to a selection, so now you only need to enter one time for daily, and can have separate times for daily and period.

I noticed that the default #F5F6CE yellow in skin_user.xml comes out a lot lighter than the yellow in your previous plug-in. But that is easily fixed in skin_user.xml.

The default didn't change (#D2D225). The user skin was intended for star6key, who didn't like that.

Do you intend making this a plug-in?

I intend to submit it for inclusion in the firmware (hence the switch from plugin to patch).

[peteru]

I intend to submit it for inclusion in the firmware

It would be nice if this (or a similar feature) was integrated with the existing primetime setting. At the moment, the primetime setting just defines an arbitrary start time. If a duration (or end time) was added to primetime, then all entries in the primetime window could have a distinct colouring, with the rest of the entries having the normal colour scheme.

The colour transition between primetime and post-primetime entries would very likely suffice as an indication of one viewing day transitioning to another.

As an example, with primetime set to 19:00 ~ 01:00, the colouring could look like this:

 04:00 - 06:00 Event A 
 06:00 - 11:30 Event B 
 11:30 - 15:30 Event C 
 15:30 - 18:30 Event D 
 18:30 - 20:30 Event E 
 20:30 - 23:00 Event F 
 23:00 - 01:30 Event G 
 01:30 - 04:00 Event H 
 04:00 - 06:00 Event I 
 06:00 - 11:30 Event J 


There's probably also no reason to have two separate definitions for primetime as there are now. All EPG views should behave consistently.

[sub3R]

Seems to work okay for me. I did neglect to reset the seconds to 0, but that still shouldn't have done what you saw.

It consistently did as I described every time I changed the minutes to anything other than 0 on both U4s. I thought it may have been because I was saving the last 75 minutes (in EPG setup) but changing that to saving the last 0 minutes didn’t fix it.

The latest version worked perfectly for me. Increasing the minutes increases the transition time past the set hours.

The default didn't change (#D2D225). The user skin was intended for star6key, who didn't like that.

Ahh ok, I thought the default colour was in the user skin but I can now see it wasn’t.

The user skin is important to have, what looked good on one U4/TV combination looked pretty ordinary on the other U4/TV combination. Its nice to be able to change the colours like that, sometimes just a minor change makes the text easier to read.

[Grumpy_Geoff]

I've changed the option to a selection, so now you only need to enter one time for daily, and can have separate times for daily and period.

What would you expect the transition to show with a 19:00 - 01:00 time window?
I get the transition starting at the earliest of the two times and it continues until the later of those times.
It's not what I expected, I'm wanting the 6 hours to be colour transitioned.

[adoxa]

The current time (more specifically, the time of the first event) is always white, so 1725-1900 should be white, 1900-0100 yellow, 0100-1900 white, ... When the current time is past 1900 then it will be white until 0100, yellow until 1900, then white, ...

[Grumpy_Geoff]

The current time (more specifically, the time of the first event) is always white, so 1725-1900 should be white, 1900-0100 yellow, 0100-1900 white, ... When the current time is past 1900 then it will be white until 0100, yellow until 1900, then white, ...

No way Jose.

Current is yellow because that event time is greater than 01:00 but less that 19:00.
Stays yellow until the 19:00 is hit, that being the latest of the two times, then goes white.
It's treating it as 01:00 - 19:00, but 19:00 - 01:00 was spec'ed.

[adoxa]

I wasn't testing the start time properly.

[Grumpy_Geoff]

Code: Select all

root@beyonwizv2:~# grep config.epgselection.transition_ /etc/enigma2/settings
config.epgselection.transition_firsthour=19
config.epgselection.transition_secondhour=22
root@beyonwizv2:~#

It's the opposite of how I expect it, which is events from 19:00 - 22:00 to be transitioned to colour.

Don't worry about it, I won't bother.

[adoxa]

You're in the 1900-2200 block, so the transition occurs after 2200, then again at 1900. Seems like you want the prime time colouring that peteru mentioned, where you want a specific time range always highlighted. This is intended more for making it easier to know when to stop when looking ahead. I could either add another selection to highlight the period, not the transition, or keep the transition and add another option for the period (the prime time option). That would be three colours: white for current, yellow for transition, green for prime time (overriding the other two).

[Grumpy_Geoff]

Hang on, it's now working as I expected (after an overnight shut down and reboot for this morning's timer). Settings are still -

Code: Select all

config.epgselection.transition_firsthour=19
config.epgselection.transition_secondhour=22

So, are you saying this behaviour will change based upon the current time-of-day (inside/outside of "first -> second" window)?
If so, I'll make do without it.
Thanks anyway.

[sub3R]

Attachments: epg-transition.zip

With the latest version you attached on Jul 30, 2021 22:10 I find the following:

The Daily option hours works fine including the minutes.

I’m not sure if the Period option is working as it should. For example:

• This morning setting the First hour to 10, the Second hour to 1 & both minutes to 0 gave me the exact same result as setting the First hour to 1, the Second hour to 10 & both minutes to 0.
• I also managed to trigger once only a similar issue I found in the second paragraph here. I should have taken more notice to what options I had set but due to the time I had to stop & later I couldn’t replicate it. I think I had Daily option set to 0, Period First & Second hour options set to either 1 & 10 or 10 & 1, Period First minute set to 1, & Period Second minute set to 0. This only gave me a single line colour change about three days in the future. Could this be due to the end/start time of a particular EPG time slot & a time change/update?

The above doesn’t worry me because the Period option is something I don't have a need for ... just reporting something that doesn't seem right to me.

... That would be three colours: white for current, yellow for transition, green for prime time (overriding the other two).

If you decided to go that way, in addition to the transition colour would you also be making the prime time colour user configurable in skin_user.xml ?

[adoxa]

• This morning setting the First hour to 10, the Second hour to 1 & both minutes to 0 gave me the exact same result as setting the First hour to 1, the Second hour to 10 & both minutes to 0.

That is how it's supposed to work. That's why it's called first & second, not begin & end, because it's a transition between one period and the other.

This only gave me a single line colour change about three days in the future. Could this be due to the end/start time of a particular EPG time slot & a time change/update?

Possibly. I haven't seen it any of my testing. I'll be using the period myself at some stage, but I've got to integrate it with my other changes.

If you decided to go that way, in addition to the transition colour would you also be making the prime time colour user configurable in skin_user.xml ?

Yep, EPGSinglePeriodColor, default is #00AA00. It goes with the new option "Highlight period" (don't like "primetime", sorry peteru). Any event that starts within the period, or starts before and ends at least 10 minutes after the period starts, will be green (or whatever). This should satisfy what GG wanted, I think. The default period is 19:30 to 23:00.

[sub3R]

That is how it's supposed to work. That's why it's called first & second, not begin & end, because it's a transition between one period and the other.

Fair enough, I can see that now.

Any event that starts within the period, or starts before and ends at least 10 minutes after the period starts, will be green (or whatever). This should satisfy what GG wanted, I think. The default period is 19:30 to 23:00.

I see you’ve made the Highlight period hours & minutes ‘begin’ & ‘end’. Seeing that I thought I may be able to use that option to highlight a late night to a mid morning period (begin 2330 to end 0930), but it didn’t come out as I expected (see below attachments). It does however work as I expected if I begin after midnight & leave the end at 0930 (begin 0030 to end 0930).

Should the Highlight period colour span from begin 2330 (11:30pm) to end 0930 (09:30am) or have I got the bull by the tail again?

So you can follow my colours; I’ve made “EPGTransitionColor" grey (#A0A0A0), & "EPGSinglePeriodColor" yellow (#D2D225) in skin_user.xml.

Code: Select all

<skin>
  <parameters>
    <parameter name="EPGTransitionColor" value="#A0A0A0" />
    <parameter name="EPGSinglePeriodColor" value="#D2D225" />
  </parameters>
</skin>

2330 to 0930 period & 1000 transition (1)

2330 to 0930 period & 1000 transition (2)

2330 to 0930 period & 1000 transition (3)

0030 to 0930 period & 1000 transition (1)

[adoxa]

Should the Highlight period colour span from begin 2330 (11:30pm) to end 0930 (09:30am) or have I got the bull by the tail again?

It should, yes, glad you're testing it properly, at least.

[adoxa]

Should the Highlight period colour span from begin 2330 (11:30pm) to end 0930 (09:30am) or have I got the bull by the tail again?

Fixed that and added direct number input (to any config number selection; no negative, no backspace, though).

[sub3R]

Fixed that and added direct number input (to any config number selection; no negative, no backspace, though).

So far with limited testing that version works fine. The direct hour & minute input is a good idea.

It is so much easier & quicker to go through the EPG in the morning now, & I don't get "you've gone too far".

For anyone trying different text colours in skin_user.xml I found Grey #A0A0A0 works well on one U4/TV combination, Silver #C0C0C0 on the other U4/TV combination, & Tan #D2B48C on both U4/TV combinations. These are a trade off between not being too harsh to read & being different enough to the previous/next transition/period colour. Without an on-screen keyboard, I gave up trying to edit in File Commander with the remote control … a USB keyboard works very well.

[Grumpy_Geoff]

Yep, EPGSinglePeriodColor, default is #00AA00. It goes with the new option "Highlight period" (don't like "primetime", sorry peteru). Any event that starts within the period, or starts before and ends at least 10 minutes after the period starts, will be green (or whatever). This should satisfy what GG wanted, I think. The default period is 19:30 to 23:00.

Yep, it does, thanks.
I left it at the defaults and it's fine.

I was a bit thick before with the transition times. I realise now it's a transition at time-1, transition at time-2 arrangement, and the current time affects the highlighting. It's not a from/to period.
Highlight period is more to my liking.

[adoxa]

Here's an update, installed as a plugin, but still a patch (it replaces existing files). It will uninstall itself before an online update and indicate itself in the About.

Past events are now considered a transition; up to an hour before the transition is considered current. Transition's "Period" is now called "Twice daily".

Added option "Hide titles" (default on); use STOP to remove titles from the EPG. Use SUBT to ignore titles (same as hide, but always off when the guide opens). Again, use STOP to ignore. When the options are off STOP will restore the titles. The titles are saved in /etc/enigma2/epg_hide and epg_ignore. They're sorted for convenience; they don't need to be if you manually edit them. Turn the option off before editing, when it's turned back on the updated file will be read. The file can be deleted to reset everything.

[sub3R]

Here's an update, installed as a plugin, but still a patch (it replaces existing files). It will uninstall itself before an online update and indicate itself in the About.

Thanks. I'll install this within the next couple of days. When you say "(it replaces existing files)", I take it you mean it replaces all existing files except skin_user.xml to change text colours, or is that installed with the plug-in?

Your existing epg-transition is working great. I don’t mean to put other improvements down, but I’d put it up there with your Automute plug-in & IanSav’s OverlayHD as an improvement.

[adoxa]

When you say "(it replaces existing files)", I take it you mean it replaces all existing files except skin_user.xml to change text colours, or is that installed with the plug-in?

It replaces the files it modifies, not all existing files. No, skin_user.xml is up to the user to create.

[sub3R]

That’s what I thought … just wanted to clarify. Thanks.

[sub3R]

It will uninstall itself before an online update and indicate itself in the About.

Confirmed that it does that with an on-line update to 19.3 20210828 & to 19.3 20210830 on our U4s. An observation which is probably intentional at this stage; I had to re-install it after an on-line update whereas I didn’t have to re-install AutoMute or OverlayHD.

Period & Transition works very nicely & works with my existing skin_user.xml for text colours. Well done, & as I mentioned before, this is a nice improvement to the EPG.

Hide Titles is something I would never use but I did try it over a couple of hours. I found it not very user friendly & the SUBT confusing (actually I’m still not sure what SUBT does).

I think the default option for Hide Titles should be disabled instead of enabled, although my disabled setting was saved after a backup, an on-line f/w update with restore settings, & a re-install of enigma2-plugin-systemplugins-epg-hide-hl_1_all.ipk. With Hide Titles enabled it would be too easy for someone not familiar with how it works to accidently press STOP & not realising it hide that EPG entry & the future ones.

Have you considered making Hide Titles a separate plug-in to Period & Transition (i.e. two separate plug-ins so that Period & Transition can be installed on its own)? But I suppose disabling Hide Titles achieves the same.

It is nice to have a plug-in version for Period & Transition so I no longer have to un-install the previous patch version before a f/w update.

[adoxa]

I had to re-install it after an on-line update whereas I didn’t have to re-install AutoMute or OverlayHD.

OverlayHD is a skin, so mostly unaffected by updates; AutoMute is a "hook", so should work with updates, unless there's a pretty major change; but this is a patch, so installing it may effectively undo an update.

Hide Titles is something I would never use but I did try it over a couple of hours. I found it not very user friendly & the SUBT confusing (actually I’m still not sure what SUBT does).

Really? You don't mind seeing all those "Home Shopping" and "Infomercial" entries, as well things like "Leading the way"? That's stuff I never want to see; SUBT is for stuff I don't want to see atm, mostly repeats. E.g. pretty much everything on Ten (at one stage Peach was under a page for the whole week, but more Charmed repeats has got it back to two).

I think the default option for Hide Titles should be disabled instead of enabled

Peteru will probably want that, too, so I'll do it for the next update (or before submission).

Have you considered making Hide Titles a separate plug-in to Period & Transition (i.e. two separate plug-ins so that Period & Transition can be installed on its own)?

I'll submit them for inclusion into the firmware (after the beta becomes production), so there won't be a plugin.

[Grumpy_Geoff]

epg-hide-hl was auto-uninstalled as part of the online update, yet it still shows as being present in "About" and the plugin is still listed as being installed.

Code: Select all

root@beyonwizv2:~# ls -al *epg*
-rw-r--r--    1 root     root        109591 Aug 30 11:27 backup-epg-hide-hl.tar.gz
root@beyonwizv2:~#
root@beyonwizv2:~# opkg info '*epg-hide-hl*'
Package: enigma2-plugin-systemplugins-epg-hide-hl
Version: 1
Depends: beyonwiz-version-info (>= 19.3-20210801)
Status: install user installed
Architecture: all
Installed-Size: 93736
Installed-Time: 1630294041

root@beyonwizv2:~# date @1630294041
Mon Aug 30 11:27:21 AWST 2021
root@beyonwizv2:~#

We have to manually uninstall it first before re-install it, right?
What then does epg-hide-hl do when re-installing after an online update? The backup file is still present, must we delete the backup or will another be taken?

[sub3R]

We have to manually uninstall it first before re-install it, right?
What then does epg-hide-hl do when re-installing after an online update? The backup file is still present, must we delete the backup or will another be taken?

No. I didn’t. When the on-line f/w update was being done it displayed that it was being removed.

After doing the on-line f/w update with restore there wasn’t any of the relevant options under EPG > MENU & my previous text colours had been removed. After re-installing enigma2-plugin-systemplugins-epg-hide-hl_1_all.ipk the previously set text colours were back & the relevant options were back under EPG > MENU.

I didn’t check About or the list of plug-ins before the enigma2-plugin-systemplugins-epg-hide-hl_1_all.ipk re-install though, only after.

[Grumpy_Geoff]

We have to manually uninstall it first before re-install it, right?
What then does epg-hide-hl do when re-installing after an online update? The backup file is still present, must we delete the backup or will another be taken?

No. I didn’t. When the on-line f/w update was being done it displayed that it was being removed.

It's not active, that I know.

But, I think I know what our different experience is from. I used the OWIF/Settings/Packages method to try it out (whereas you used the GUI), obviously that OWIF method didn't uninstall the plugin.

Ahh, I thought this may be what the uninstall would try to do -

Code: Select all

root@beyonwizv2:~# mv backup-epg-hide-hl.tar.gz backup-epg-hide-hl.tar.gz.old
root@beyonwizv2:~#
root@beyonwizv2:~# opkg remove enigma2-plugin-systemplugins-epg-hide-hl
Removing enigma2-plugin-systemplugins-epg-hide-hl (1) from root...
Extracting backup...
tar (child): /home/root/backup-epg-hide-hl.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
rm: can't remove '/home/root/backup-epg-hide-hl.tar.gz': No such file or directory
You can force removal of packages with failed prerm scripts with the option:
        --force-remove
No packages removed.
Collected errors:
 * pkg_run_script: package "enigma2-plugin-systemplugins-epg-hide-hl" prerm script returned status 1.
 * opkg_remove_pkg: not removing package "enigma2-plugin-systemplugins-epg-hide-hl", prerm script failed
root@beyonwizv2:~#

I then forced the re-install -

Code: Select all

root@beyonwizv2:/hdd/Runnables# opkg install --force-reinstall enigma2-plugin-systemplugins-epg-hide-hl_1_all.ipk
Reinstalling enigma2-plugin-systemplugins-epg-hide-hl (1) on root.
Installing enigma2-plugin-systemplugins-epg-hide-hl (1) on root.
Extracting backup...
tar (child): /home/root/backup-epg-hide-hl.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
rm: can't remove '/home/root/backup-epg-hide-hl.tar.gz': No such file or directory
prerm script for package "enigma2-plugin-systemplugins-epg-hide-hl" failed
Configuring enigma2-plugin-systemplugins-epg-hide-hl.
Creating backup...
Extracting files...
Collected errors:
 * pkg_run_script: package "enigma2-plugin-systemplugins-epg-hide-hl" prerm script returned status 1.
root@beyonwizv2:/hdd/Runnables#

A new backup was taken -

Code: Select all

root@beyonwizv2:/hdd/Runnables# ls -altr ~/backup-*
-rw-r--r--    1 root     root        109591 Aug 30 11:27 /home/root/backup-epg-hide-hl.tar.gz.old
-rw-r--r--    1 root     root        109583 Aug 31 13:09 /home/root/backup-epg-hide-hl.tar.gz
root@beyonwizv2:/hdd/Runnables#
[code]

[sub3R]

Really? You don't mind seeing all those "Home Shopping" and "Infomercial" entries, as well things like "Leading the way"? That's stuff I never want to see; SUBT is for stuff I don't want to see atm, mostly repeats. E.g. pretty much everything on Ten (at one stage Peach was under a page for the whole week, but more Charmed repeats has got it back to two).

Ok, I have to agree with you there. I can see that getting rid of the “home shopping” ones would speed up going through the EPG. My better also half thinks so, so I might give this a go on one U4 & see how it goes.

After playing around with SUBT in Hide Titles, I’ve finally worked out how it works. For the average user it really needs a detailed help option detailing how to use it.

While testing I got caught out trying to remember which service I removed one of the titles from. Looking in /etc/enigma2/epg_hide didn’t help. I think /etc/enigma2/epg_hide & /etc/enigma2/epg_ignore needs more information such as the service & possibly the start time the now hidden/ignored item was listed in the EPG (though a future EPG date could possibly show it at a different start time).

IMO to be more user friendly one shouldn’t have to look in those files with something like File Commander, that information should be available from the GUI. That's probably a lot of work & I don’t know how that could be displayed. Ideally, by toggling a button or option from the GUI to show a list of the hidden/ignored items so that one or more can be restored from there without having to go through the list in the EPG.

[sub3R]

But, I think I know what our different experience is from. I used the OWIF/Settings/Packages method to try it out (whereas you used the GUI), obviously that OWIF method didn't uninstall the plugin.

Good find. Looking at some user experiences with OWIF, mine included, it leaves a bit to be desired.

[adoxa]

Sorry, I should have mentioned that uninstall would only automatically happen from the GUI ("Update and ask to reboot"). I should be able to hook upgrade from OWIF, too, but you're on your own from the command line.

After playing around with SUBT in Hide Titles, I’ve finally worked out how it works. For the average user it really needs a detailed help option detailing how to use it.

Press SUBT to turn it on, press STOP to remove what you don't want to see. How much more detail is there?

IMO to be more user friendly one shouldn’t have to look in those files with something like File Commander, that information should be available from the GUI. That's probably a lot of work & I don’t know how that could be displayed. Ideally, by toggling a button or option from the GUI to show a list of the hidden/ignored items so that one or more can be restored from there without having to go through the list in the EPG.

That's why I didn't make it public. Hm, how about long-STOP to bring up a menu of what's hidden, then you could press OK to restore it. Sort it by most recent first, with an option to sort by title (or vice-versa).

[Grumpy_Geoff]

Sorry, I should have mentioned that uninstall would only automatically happen from the GUI ("Update and ask to reboot"). I should be able to hook upgrade from OWIF, too, but you're on your own from the command line.

If you want, but don't bust your gut over it as I was just trying out the option peteru mentioned.
If I'm using OWIF to update, I just use the virtual remote to drive the GUI process, including backing up; whereas the OWIF package method doesn't have the backup option.
Manually uninstalling doesn't appear to be an issue as it wants to restore the files ("Extracting backup...").

[sub3R]

Hm, how about long-STOP to bring up a menu of what's hidden, then you could press OK to restore it. Sort it by most recent first, with an option to sort by title (or vice-versa).

That sound pretty good. Are you able to add the service & possibly the start time of each EPG entry to that menu list, or is that too much trouble?

Press SUBT to turn it on, press STOP to remove what you don't want to see. How much more detail is there?

Is that the short version?

Currently the description for Hide titles reads: “Exclude selected titles from the EPG".

That is what it does but it doesn’t explain what pressing SUBTITLE or STOP (when enabled or disabled) does so a user who hasn't used it before knows how to make use of it.

This is how I see it with the current version:

There are two screens; the normal EPG screen & the Ignore screen. An (*) is shown at the top right when in the Ignore screen.

To hide an EPG item:

• Enable Hide titles via MENU from the EPG.
• Exit back to the EPG & press STOP on a highlighted EPG item to hide that item.
• Enabling or disabling Hide titles will either show or not show the hidden item/s.
• To restore that item again if required; disable Hide titles, highlight the previously hidden item & press STOP.

To ignore an EPG item:

• Enable Hide titles via MENU from the EPG.
• Exit back to the EPG & press SUBTITLE to change to the Ignore screen.
• Press STOP on a highlighted EPG item to ignore that item.
• Pressing SUBTITLE when in the EPG will toggle between the normal EPG screen & the Ignore screen & will either show or not show the ignored item/s.
• To restore that item again if required; press SUBTITLE to change to the normal EPG screen, or EXIT the EPG & re-enter it. Disable Hide titles, highlight the previously ignored item & press STOP.

I don’t know how to condense all that so it still makes sense.

[adoxa]

Are you able to add the service & possibly the start time of each EPG entry to that menu list, or is that too much trouble?

Too much trouble, and since hide ignores service, not really relevant. I'll see about getting that done tomorrow.

Currently the description for Hide titles reads: “Exclude selected titles from the EPG".

That is what it does but it doesn’t explain what pressing SUBTITLE or STOP (when enabled or disabled) does so a user who hasn't used it before knows how to make use of it.

I agree the description could do with work; HELP will show SUBTITLE and STOP. I almost changed the description to something along the lines of "Use STOP to hide/show titles", but didn't want to assume the key, even though that's pretty unlikely to change, I guess.

This is how I see it with the current version:

I'd love to do something like that, but as you say, how? Hm, I don't think config screens use INFO, maybe that could pop up a longer help...

[sub3R]

Too much trouble, and since hide ignores service, not really relevant. I'll see about getting that done tomorrow.

Fair enough, I understand what you are saying.

It got the tick of approval this morning when browsing the EPG looking for something to record. Yesterday I set all home shopping type shows & all foreign news to ignore & it made browsing through the EPG much faster.

I will probably change those above items from ignore to hide mainly because of the Harmony 650 remotes I use. On the 650 I have the SUBTITLE button hidden away in the LCD screen options so it takes a few key presses to get to it each time the EPG is loaded. In my unique situation hide would work better, but when I change to using hide I’ll have to leave Hide titles enabled so I’ll have be careful not to accidently press the larger PLAY button which I’ve configured as the STOP button. I was thinking a confirmation popup would be good for this but that would slow down adding hide items. I doubt that other user would have this problem anyway.

I assume I can transfer the current items in /etc/enigma2/epg_ignore to a newly created /etc/enigma2/epg_hide followed by deleting /etc/enigma2/epg_ignore without breaking anything. If it does I’ll post back.

[sub3R]

I assume I can transfer the current items in /etc/enigma2/epg_ignore to a newly created /etc/enigma2/epg_hide followed by deleting /etc/enigma2/epg_ignore without breaking anything. If it does I’ll post back.

For anyone wanting to do this, it worked fine. Just follow adoxa’s advice about disabling Hide titles before editing & enable it when finished.