OverlayHD Skin...

[adoxa]

I've installed 1.66 on the U4. [...]

A minor gripe is the install step states the Execution progress step but not Execution finished. After waiting a few minutes I exited and restarted the GUI. [...]

1.66 on a T2 with 20180729 (no patches) installed in about 30 seconds.

[Paul_oz53]

I've installed 1.66 on the U4. [...]

A minor gripe is the install step states the Execution progress step but not Execution finished. After waiting a few minutes I exited and restarted the GUI. [...]

1.66 on a T2 with 20180729 (no patches) installed in about 30 seconds.

The only patch I have installed is the loading progress indicator for the U4. Wouldn't expect that to be an issue.

[adoxa]

The only patch I have installed is the loading progress indicator for the U4. Wouldn't expect that to be an issue.

Shouldn't be. If it's convenient, could you remove it, enable debugging, and install again? Of course, you can bet it'll work...

[Paul_oz53]

The only patch I have installed is the loading progress indicator for the U4. Wouldn't expect that to be an issue.

Shouldn't be. If it's convenient, could you remove it, enable debugging, and install again? Of course, you can bet it'll work...

Yep, that's exactly correct.

Last time I installed it over version 1.60. This time I removed it first then installed 1.66 over the FMW skin. No dramas. No point to the logs given it worked.

[adoxa]

FWIW, I had 1.64 installed, FMW active.

[IanSav]

Hi Adoxa,

I am looking at the code changes in MovieList.py and the default the mark icon width is set to 16 pixels. The mark images are then loaded and the the height checked against the item height to clip the height of the image. The hard coded mark icon width is never reset the width of the actual icon! It looks like the width override MUST be used to make this work.

I just copied what iconsWidth did.

I will look at fixing the code later.

Why is the existing list data offset by 50 pixels? The original data default offset should be related to the width of the mark icon. This setting requires a specific override but is a setting that shouldn't need to even exist.

I wanted the icon drawn before 50, but the list to remain at 50. The way I solved this was to have the list at 0 and add listPos to seemingly move it back to 50. The icon is then drawn its width (markWidth) and space before it.

This code does not conform to the way the UI widgets normally work. This solution breaks the line highlighting. Again, I will look at fixing this later.

You were right about the FileCommander icons not looking very good in this context.

There's a first.

I have no problems acknowledging when I make a mistake. Once I recognised the issue it was quick and easy to create a better looking set of icons.

The current code can not be used to create a clean left aligned list in OverlayHD.

I'm not sure what you mean. Here's how I do it (well, I would have, if I patched it right):
myway.png

Code: Select all

	<screen name="MovieSelectionListBeyonwiz">
		<widget name="list" position="0,80" size="810,525" backgroundColor="MenuBackground" backgroundColorSelected="MenuSelected" enableWrapAround="1" foregroundColor="MenuText" foregroundColorSelected="MenuTextSelected" scrollbarMode="showOnDemand" transparent="0"
			font="MovieSelectionFont;20" pbarHeight="10" pbarLargeWidth="45" spaceIconeText="5" iconsWidth="25" spaceRight="5" dateWidthScale="9.0" lenWidthScale="4.0" sizeWidthScale="5.0" listPos="50" />

and here's what I think you're after:
yourway.png

Code: Select all

	<screen name="MovieSelectionListBeyonwiz">
		<widget name="list" position="50,80" size="760,525" backgroundColor="MenuBackground" backgroundColorSelected="MenuSelected" enableWrapAround="1" foregroundColor="MenuText" foregroundColorSelected="MenuTextSelected" scrollbarMode="showOnDemand" transparent="0"
			font="MovieSelectionFont;20" pbarHeight="10" pbarLargeWidth="45" spaceIconeText="5" iconsWidth="25" spaceRight="5" dateWidthScale="9.0" lenWidthScale="4.0" sizeWidthScale="5.0" markWidth="20" listPos="25" />

After doing that I'll admit it could be better.

I strive for pixel perfect alignment of all on screen elements. This is a case where I can not achieve the alignment I desire. I will look at fixing this when I look at the other UI changes I would like to make to this code.

Regards,
Ian.

[adoxa]

[...] This solution breaks the line highlighting. [...]

Ah yes, that was another thing - I didn't want the mark to be highlighted, especially when it's blank.

You were right about the FileCommander icons not looking very good in this context.

There's a first.

I have no problems acknowledging when I make a mistake. [...]

No no, I meant it was the first time I was right.

I strive for pixel perfect alignment of all on screen elements. This is a case where I can not achieve the alignment I desire. I will look at fixing this when I look at the other UI changes I would like to make to this code.

I still don't believe you've told me what you actually want, so I'll just shut up and wait for your patch.

[IanSav]

Hi Paul,

A minor gripe is the install step states the Execution progress step but not Execution finished. After waiting a few minutes I exited and restarted the GUI. As it was not clear it had installed, I reinstalled. On the subsequent attempt, the message came up that it is already installed.

Is this still a problem? I can't reproduce the issue. Once 1.66 is installed you can't reinstall using the GUI, you need to remove OverlayHD and reinstall it again.

Checking the FC screen, I see Help has been added and the "True" icon image is a blue dot.

The HELP button is compliments of Prl's changes to FileCommander.

Yes, the switch icon has had a refresh. Is it okay?

Also, the screen for Menu->YouTube has been redesigned but otherwise appears complete and functional. These were the obvious changes. Anything else is quite subtle.

There are a lot of changes under the covers and a few on top. If things are generally looking "normal" then that is good. If any screens look wrong or don't follow the OverlayHD style I would like the problems and screen captures reported.

In Network->DLNA setup, the following screen is not usable to amend setting: miniDLNA setup (Blank screen but not an issue with 1.60 on the T3).

Can I please have some screen captures with instructions on how to reproduce the issue.

The green tick sits on top of a visible red cross with the TiVo settings, etc. on the previous screen: miniDLNA.

I don't seem to be able to enable the TiVo option on my box. Can you please give me more information about what you are experiencing. (My issue may be due to my new setup engine but it could be an existing bug.)

Mountpoints management -> Mountpoint viewer screen: No borders around green ticks? (General observation: Newer screens use the selection box border around green ticks but older screens do not [See Autotimer options]. This is not consistent through the whole interface.)

In Mountpoints management there are three icons used. The green tick indicates that the mount is active. The red cross indicates that the mount is inactive. The yellow exclamation mark indicates an error condition. These icons are a status report and not a call to action. The ticks in boxes represent an option that has been selected and can optionally be deactivated (like file selection). Think of these boxed icons like checkboxes on a web page. The two sets of icons have different meanings in the UI.

I have the next version of OverlayHD (1.67) ready to go. It has the CutList editor changes, the new FileCommander headings and an improved MovieSelection screen (though it is not as good as I would like it to be - yet). Obviously I will look at the issues you mentioned once I understand them. Other than those issues is there anything in the skin that should stop me releasing it to everyone as an automated update?

Regards,
Ian.

[Paul_oz53]

Hi Paul,

A minor gripe is the install step states the Execution progress step but not Execution finished. After waiting a few minutes I exited and restarted the GUI. As it was not clear it had installed, I reinstalled. On the subsequent attempt, the message came up that it is already installed.

Is this still a problem? I can't reproduce the issue. Once 1.66 is installed you can't reinstall using the GUI, you need to remove OverlayHD and reinstall it again.

No, not a problem for me the second time around. Only happened when I installed it without removing 1.60. The second time I uninstalled the OverlayHD skin before running the install.

Checking the FC screen, I see Help has been added and the "True" icon image is a blue dot.

The HELP button is compliments of Prl's changes to FileCommander.

Yes, the switch icon has had a refresh. Is it okay?

Thanks prl. FC usability is now very much improved.

Re the icon: I do tend to get used to the way things are so sorry to say I prefer the old icon. Mainly because I find it easier to see when I access the machines using Openwebif. At the end of the day, it is a matter of personal preferences.

Also, the screen for Menu->YouTube has been redesigned but otherwise appears complete and functional. These were the obvious changes. Anything else is quite subtle.

There are a lot of changes under the covers and a few on top. If things are generally looking "normal" then that is good. If any screens look wrong or don't follow the OverlayHD style I would like the problems and screen captures reported.

I did not find any other screens that were wrong, apart from the two MiniDLNA screens on the U4.

In Network->DLNA setup, the following screen is not usable to amend setting: miniDLNA setup (Blank screen but not an issue with 1.60 on the T3).

Can I please have some screen captures with instructions on how to reproduce the issue.

The green tick sits on top of a visible red cross with the TiVo settings, etc. on the previous screen: miniDLNA.

I don't seem to be able to enable the TiVo option on my box. Can you please give me more information about what you are experiencing. (My issue may be due to my new setup engine but it could be an existing bug.)

Bear in mind I am testing 1.66 on the U4 and using the T3 for comparison with the current production OverlayHD. I suspect if there is a difference with 1.66 on your T3 to the U4 results, it may have something to do with the way the U4 presents video. I seem to recall some early discussion of that but it has long since gone quiet.

Attached are screenshots of the two screens on the U4 and the T3 for comparison. Access as Menu>>Network>>DLNA Setup. On the U4 both the red cross and green tick are visible but on the T3 it is either / or. If one now presses Menu, the U4 screen is blank, whilst the T3 has the MiniDLNA setup options displayed.

Mountpoints management -> Mountpoint viewer screen: No borders around green ticks? (General observation: Newer screens use the selection box border around green ticks but older screens do not [See Autotimer options]. This is not consistent through the whole interface.)

In Mountpoints management there are three icons used. The green tick indicates that the mount is active. The red cross indicates that the mount is inactive. The yellow exclamation mark indicates an error condition. These icons are a status report and not a call to action. The ticks in boxes represent an option that has been selected and can optionally be deactivated (like file selection). Think of these boxed icons like checkboxes on a web page. The two sets of icons have different meanings in the UI.

OK, that clears up the distinction.

I have the next version of OverlayHD (1.67) ready to go. It has the CutList editor changes, the new FileCommander headings and an improved MovieSelection screen (though it is not as good as I would like it to be - yet). Obviously I will look at the issues you mentioned once I understand them. Other than those issues is there anything in the skin that should stop me releasing it to everyone as an automated update?

Regards,
Ian.

I don't believe so Ian, MiniDLNA aside.

I haven't explored all the screens under Media->Menu but those I did look at were fine (also Media, IMDB, EPG, Timers, Autotimers). I checked nearly all the screens under Menu. These were all OK. The only really obvious change is in the YouTube screens and it worked OK for me with the new skin screens.

Since I bought the Denon AVR, it has the WizTV dongle installed and that is now my preferred YouTube viewer. Consequently, I no longer use the inbuilt version as my primary YouTube source. This is not because of the skin but because the interface on the dongle is full-featured whereas the inbuilt version is not.

[prl]

Checking the FC screen, I see Help has been added ...

The HELP button is compliments of Prl's changes to FileCommander.

Thanks prl. FC usability is now very much improved.

Thanks. There's more to come

Progress on the work on File Commander is logged here.

[IanSav]

Hi Prl,

I don't have a U4. Could you please see if the DLNA issues that Paul is reporting are actually a U4 issue rather than a skin issue?

Regards,
Ian.

[Grumpy_Geoff]

I don't have a U4. Could you please see if the DLNA issues that Paul is reporting are actually a U4 issue rather than a skin issue?

There's no issue with those screens on a U4 running F-M-W.

[prl]

There doesn't seem to be any problem with the MiniDLNA screens for me, U4 with OverlayHD 1.66 and firmware 20180729beta.:

[prl]

I don't have a U4. Could you please see if the DLNA issues that Paul is reporting are actually a U4 issue rather than a skin issue?

There's no issue with those screens on a U4 running F-M-W.

I think the question relates just to IanSav's recent changes to OverlayHD. In the pre-loaded skins, the file that contains the MiniDLNA main screen hasn't changed since early April.

[Paul_oz53]

I don't have a U4. Could you please see if the DLNA issues that Paul is reporting are actually a U4 issue rather than a skin issue?

There's no issue with those screens on a U4 running F-M-W.

I'm beginning to think this has something to do with the first failed attempt to install 1.66 on the U4. FMW and easy-aus are both corrupt on my U4. (BTW - in my earlier post where I say version 1.60, I suspect it is in fact version 1.64 that is running on the T3/T4.)

I'll reflash back to 20180417 and try again.

[Paul_oz53]

You can rest easy Ian.

The problem must have been induced with the original install. It has now been restored to normality.

[IanSav]

Hi,

Thanks to everyone for testing out the DLNA screens.

@Paul, are you getting used to the new switch icon? If you still don't like it then how could I improve it?

Regards,
Ian.

[Paul_oz53]

Hi,

Thanks to everyone for testing out the DLNA screens.

@Paul, are you getting used to the new switch icon? If you still don't like it then how could I improve it?

Regards,
Ian.

Hi Ian.

I can live with the icons. I still prefer the older style which has a greater area coloured blue when selected. If you could make the blue circle larger, that would be a compromise but it's up to you.

Cheers,

[IanSav]

Hi Paul,

I can live with the icons. I still prefer the older style which has a greater area coloured blue when selected. If you could make the blue circle larger, that would be a compromise but it's up to you.

I asked because I wanted to improve the acceptability for everyone. No suggestion or comment will be ignored.

I can make the blue LED larger or I can make the entire top of the switch blue. The reason I changed the icons was because having the switch background change colour looked wrong to me. Do any of the attached versions appear better to you?

Regards,
Ian.

[prl]

The reason I changed the icons was because having the switch background change colour looked wrong to me.

I've seen that convention used in some physical slide switches.

[IanSav]

Hi Prl,

The reason I changed the icons was because having the switch background change colour looked wrong to me.

I've seen that convention used in some physical slide switches.

As have I, and I didn't like it there either. Though the physical and three dimensional aspect of a physical switch did help.

Regards,
Ian.

[Paul_oz53]

Hi Paul,

I can live with the icons. I still prefer the older style which has a greater area coloured blue when selected. If you could make the blue circle larger, that would be a compromise but it's up to you.

I asked because I wanted to improve the acceptability for everyone. No suggestion or comment will be ignored.

I can make the blue LED larger or I can make the entire top of the switch blue. The reason I changed the icons was because having the switch background change colour looked wrong to me. Do any of the attached versions appear better to you?

Regards,
Ian.

At the risk of appearing indecisive, I can live with either. The criteria I use is can I tell at a glance whether it's selected or not. The original draft replacement is a bit small. I do prefer icons to text for this function.

Alternate 1 is an improvement on the draft icon and has the more modern LED feel so I'd be happy to go with that. Being old fashioned, I'm also very happy to use alternate 2 is if that's on offer. The latter is more reminiscent of manual slide switches.

[IanSav]

Hi Paul,

Given that I didn't get the off switch in alternative 1 quite right (I think it is still too dark) I am happy to switch to alternative 2. Consider it done.

Regards,
Ian.

[sub3R]

Hi Ian,

I can’t help much with any comments about your new version of OverlayHD except what I read or see on the forum every now & again (we are away for a few weeks).

My two cents worth about the On/Off buttons; I think the On & Off switch Alternate 2 looks much better than Alternate 1.

In OverlayHD 1.64 I don’t know if the random ‘flashing’ in the corners of the four bottom coloured buttons is something that crept in somehow some time ago & if it can be easily corrected. It appears to be some sort of background video bleed through at the outside of the button corners. For a quality skin like OverlayHD, it just doesn’t look right when it happens. When it happens, it appears worse on the U4/TV combination than on the T2/TV combination.

[IanSav]

Hi Dennis,

The flashing/sparkling around the edges of images is resolved in 1.66+ as a result of changing the alphatest="on" attribute to alphatest="blend" in all images.

Regards,
Ian.

[sub3R]

That’s good to know Ian. Nice work.

[sub3R]

Hi Ian,

I have just updated our U4 & T2 to beta f/w 17.5 20180823 (with OverlayHD 1.64). When running some scripts after this upgrade I noticed that in File Commander the file list header area was blank (no path, permissions etc.). I suspected that this was work in progress in your next version of OverlayHD, so I checked the in-build skins to see if this was the case or if something had gone missing in this latest beta.

When checking this in 'easy-skin-aus-hd' I noticed that the permissions only show, for example, as ‘-rwxr-xr-x’ instead of Octal ‘755’ like the older File Commander version did.

Do you intend to follow suit with OverlayHD & not show the Octal permissions number in the File Commander file list header? The reason I ask is because I find the Octal permissions number easier to see at a glance to tell if a script is currently executable or not, than the way it is now shown in the File Commander file list header of 'easy-skin-aus-hd', & think it would be a shame to lose this.

[prl]

Do you intend to follow suit with OverlayHD & not show the Octal permissions number in the File Commander file list header? The reason I ask is because I find the Octal permissions number easier to see at a glance to tell if a script is currently executable or not, than the way it is now shown in the File Commander file list header of 'easy-skin-aus-hd', & think it would be a shame to lose this.

The skin can show the symbolic mode, octal mode or both in the list header, but there's not a lot of spare space. Previously the content was decided entirely in the code.

I prefer the symbolic view, and I think it's a little less geeky than the octal. The octal mode has also been extended to 4 digits to show the state of the setuid, setgid and sticky bits, though they will be 0 on the large majority of files. The symbolic version also reflects those bits (e.g. 4755, rwsr-xr-x).

I think IanSav has an implementation of the header changes in OverlayHD needed for the new version of File Commander (and for backward compatibility to the old one), but I don't think it's in a release yet.

[Grumpy_Geoff]

...The reason I ask is because I find the Octal permissions number easier to see at a glance to tell if a script is currently executable or not, ...

You shouldn't need to worry about a script not having execute permissions when running it in FileCommander, as prl fixed that a while back.

[IanSav]

Hi Dennis,

I have just updated our U4 & T2 to beta f/w 17.5 20180823 (with OverlayHD 1.64). When running some scripts after this upgrade I noticed that in File Commander the file list header area was blank (no path, permissions etc.). I suspected that this was work in progress in your next version of OverlayHD, so I checked the in-build skins to see if this was the case or if something had gone missing in this latest beta.

I have OverlayHD 1.66 almost ready to go. Unfortunately I am seeing a crash in one of the converters but I can't see a bug in OverlayHD that triggers it. The infoRecBm is poorly written and has no error detection or protection code. I am still investigating. The bug causes a crash when two sequential timers run on the same service and triggers when the second timer in the sequence starts. infoRecBm gets called with a None parameter that it doesn't understand and just crashes. I think the bug may not be in my code but could be in the timer starting pop ups.

When checking this in 'easy-skin-aus-hd' I noticed that the permissions only show, for example, as ‘-rwxr-xr-x’ instead of Octal ‘755’ like the older File Commander version did.

Do you intend to follow suit with OverlayHD & not show the Octal permissions number in the File Commander file list header? The reason I ask is because I find the Octal permissions number easier to see at a glance to tell if a script is currently executable or not, than the way it is now shown in the File Commander file list header of 'easy-skin-aus-hd', & think it would be a shame to lose this.

OverlayHD 1.66 and later show both the symbolic and octal values using the facility that Prl baked into the new code..

Regards,
Ian.

[prl]

...The reason I ask is because I find the Octal permissions number easier to see at a glance to tell if a script is currently executable or not, ...

You shouldn't need to worry about a script not having execute permissions when running it in FileCommander, as prl fixed that a while back.

I'm a little puzzled by the claim, too, because the execute bit is set for octal digits 1, 3, 5 & 7, and though 3 is a slightly unusual combination, write and execute, but not read, the other three are quite sensible combinations.

[sub3R]

The skin can show the symbolic mode, octal mode or both in the list header, but there's not a lot of spare space. ...

Understood. I did recently notice the comment about the space problem in your FileCommander topic.

I prefer the symbolic view, and I think it's a little less geeky than the octal. ...

I think it depends on one’s background &/or what one has become used to. Since using the T & U series wizzes I find the 755 octal number easy to recognise as executable compared to ‘-rwxr-xr-x’.

To give one example of my use. With adoxa’s ‘/user/bin/enigma2_pre_start.sh’, I just change permissions on this from 755 to 644 then reboot before updating f/w, & change back to 755 then reboot when finished. I like to just glance at the header for confirmation. I find it quicker to do this with File Commander compared to FileZilla when doing a f/w update.

But I don’t use the in-built skins so I shouldn’t be concerned.

I haven’t fully explored it but there has been a lot of nice work done in the latest File Commander.

You shouldn't need to worry about a script not having execute permissions when running it in FileCommander, as prl fixed that a while back.

Yes, I remember that. I just like to confirm what the permissions are set to & find the File Commander file list header any easy way to do that if I’m in front of the box instead of checking via MENU in File Commander.

OverlayHD 1.66 and later show both the symbolic and octal values using the facility that Prl baked into the new code..

Excellent Ian, that covers everyone’s preference. Good luck with the crashing issue.

[prl]

... I find the 755 octal number easy to recognise as executable compared to ‘-rwxr-xr-x’.

While 755 is a common permissions setting for executables, it's by no means the only one. Anyway, it sounds like OverlayHD will display the octal value.

[sub3R]

While 755 is a common permissions setting for executables, it's by no means the only one. ...

Agree, but that is the one that sticks in my mind, & with 777 from a FAT32 USB flash drive.

Edit: I always appreciate your comments & explanations.

[IanSav]

Hi All,

I think I have found the issue behind the crash problem. The condition that triggers the crash should occur twice today. If there are no more crashes I will move to releasing a new OverlayHD soon.

Regards,
Ian.

[Paul_oz53]

Good to hear Ian.

I assume that the new version will also include the missing mark on/mark off icons and any changes needed in the OverlayHD patch for the updated Cutlist Editor to work properly.

I think I eventually had a crash when I tried OverlayHD 1.66 Alpha with the Beta version of CLE. The current patch only works with version 1.64.

Code: Select all

...[ePNG] couldn't open /usr/share/enigma2/OverlayHD/spinner/wait13.png
 ... 
[Skin] screen 'menu_information' widget 'widget': [Skin] {OverlayHD/skin.xml}: screen 'menu_information' does not have source 'key_yellow'.

There are two messages I see in the logs [Edit: for v1.64] that you might care to comment on. They don't appear to have any adverse effects but they may indicate something minor is missing.

[IanSav]

Hi Paul,

I will ask for a complete restart for all testing on the next OverlayHD. That is, test for all the issues, check out all the screens, play with everything and let me know EVERYTHING you find. Please report items that you think I already know. Now that I am working on three different images some things may get forgotten.

Regards,
Ian.

[IanSav]

Hi Paul,

I think I have a stable and functional OverlayHD for you to test. Please download OverlayHD 1.67 and give it a good test run. If you can please let me know ASAP what you think. If acceptable I will update the feed so that all users can be offered the update.

Regards,
Ian.

[Paul_oz53]

Hi Paul,

I think I have a stable and functional OverlayHD for you to test. Please download OverlayHD 1.67 and give it a good test run. If you can please let me know ASAP what you think. If acceptable I will update the feed so that all users can be offered the update.

Regards,
Ian.

Any preferences for a test bed?

I can run it on the U4 later today and, if it looks ok, extend it to the T3 and T4 Wednesday/Thursday.

[IanSav]

Hi Paul,

I don't think the platform will matter. Just check that everything appears to be working as expected. Particularly check all the screens that have had changes.

There will be one more correction, when I complete it, to improve the CutList Editor for both Beyonwiz and Enigma2.

Regards,
Ian.

[Paul_oz53]

Hi Paul,

I don't think the platform will matter. Just check that everything appears to be working as expected. Particularly check all the screens that have had changes.

There will be one more correction, when I complete it, to improve the CutList Editor for both Beyonwiz and Enigma2.

Regards,
Ian.

Hi Ian,

It's looking promising.

On the U4 on 20180910 firmware, I uninstalled 1.64, selected easy-aus and rebooted. I then installed 1.67 and rebooted. I then went through the screens and menus as methodically as I could and tried every screen that I routinely encounter and quite a few I rarely use. May have missed one or two but they would be the oddities. The images were crisp, clean, ordered and functional. EPG was ok, as was the IMDB screens. CutListEditor worked fine.

I do have one quirk as per the image with the Media List. The boxes on the LHS of the Folders and File names are missing the RHS vertical bar. I recall having a quirk last time with 1.66 which had to do with the state of the machine at install time. Can't help but wonder if it is the same issue as previous reappearing in a different guise or if it is a bug.

Ironically, I did encounter a problem with the Virtual Keyboard. I still have the alpha(?) installed but it does not work with 1.67. Rather, it gets stuck on the screen and I have to restart the GUI via Openwebif to restore operation. Is the new keyboard inbuilt into 1.67 or is it separate?

The SMS keyboard works normally where that is the default. I also managed a crash but I think it was due to file rename in File Commander, which is a different bug. I'll update the beta and try again but I'm off to a meeting for the next hour or two.

Paul

[IanSav]

Hi Paul,

The MovieSelection Slim screen was broken. The new selection boxes did not have the appropriate positioning options. Now fixed. The CutList Editor is also currently broken but will be fixed shortly. (The playback status display space is too small so some displays are confusingly clipped.)

The VirtualKeyBoard screen in OverlayHD has been coded to support the old version of VirtualKeyBoard on Beyonwiz boxes and the new version everywhere else. Unfortunately I can't support both versions on the Beyonwiz image. If you want to keep using the new VirtualKeyBoard then I will have to build you an updated VirtualKeyBoard patch. Please let me know if you want me to build one for you.

If there are no other issues I will work on producing another OverlayHD update to address the outstanding items and issue another test. If that goes well I will publish the update.

Regards,
Ian.

[Paul_oz53]

Hi Paul,

The MovieSelection Slim screen was broken. The new selection boxes did not have the appropriate positioning options. Now fixed. The CutList Editor is also currently broken but will be fixed shortly. (The playback status display space is too small so some displays are confusingly clipped.)

The VirtualKeyBoard screen in OverlayHD has been coded to support the old version of VirtualKeyBoard on Beyonwiz boxes and the new version everywhere else. Unfortunately I can't support both versions on the Beyonwiz image. If you want to keep using the new VirtualKeyBoard then I will have to build you an updated VirtualKeyBoard patch. Please let me know if you want me to build one for you.

If there are no other issues I will work on producing another OverlayHD update to address the outstanding items and issue another test. If that goes well I will publish the update.

Regards,
Ian.

Thanks Ian,

I tend to overlook that I use the "Slim" screen, which is actually full width in OverlayHD! I much prefer the extended text line for filenames. It was the feature that drew me to OverlayHD at the beginning.

Admittedly, my testing of CLE was less thorough - I actually did a quick edit as an afterthought via Openwebif. Your corrections will be welcome.

I am happy enough to revert to the old version of the onscreen virtual keyboard so as to minimise differences with mainstream OverlayHD development on the Wiz. It is not a feature I use much - I tend to use physical keyboards most of the time to rename stuff.

[IanSav]

Hi Paul,

Could you please download OverlayHD 1.68 and give it a good test run. The only significant changes I intended to make were to fix the CutList Editor screen and the Slim MovieSelection screens. There are a few image and font tweaks but not much else should have changed.

Please let me know ASAP what you think. If acceptable I will update the feed so that all users can be offered the update.

Regards,
Ian.

[Paul_oz53]

No worries Ian.

I think I will reinstall 20180417 on the U4 to test on a fresh install with no frills to get the best read on 1.68. I'll then run the beta update and retry with no frills.

I do use Adoxa's loading update on the U4 and the additional cast information. These probably have no relevance but best avoided for now.

[IanSav]

Hi Paul,

Thanks for your testing. The Slim MovieSelection change is to address the formatting error you reported. The Beyonwiz CutList Editor change is to fix and improve the display of the Beyonwiz version of the CutList Editor.

Here is the current draft of the change release notes from OverlayHD 1.64 to OverlayHD 1.68.

OverlayHD version 1.65:

• Correct spacing in CutListEditor templates
• Correct spelling of the ETSI-ALL.png file
• Optimise some of the the IceTV configuration tests
• [skin_plugins.xml] Correct some overlapping components in IMDb screen
• [skin_filemanagers.xml] Use MovieInfo converter enhancements
  • This change uses an enhanced MovieInfo converter that uses the same display options as the EventName converter. Specifically a new FullDescription option is now available together with the [Not]Separated and [Not]Trimmed options.
• [skin.xml] Update colour buttons to use new objectTypes attribute
  • This new attribute allows screen objects to be overlapped in the screen definition but restrict the actual item being displayed based on the control used to produce the object.
• Update skin and plugin to latest version of objectTypes implementation
  • This version of the skin and plugin now matches and supports the latest implementation of the objectTypes attribute.
• [skin.xml] Add missing fonts used in OpenViX

OverlayHD version 1.66:

• [skin_plugins.xml] Remove duplicated screen definitions
• [skin_filemanagers.xml] Correct colour button heights
• [skin_setup.xml] Update font size in IpkgInstaller
• Update ON/OFF switch images for Setup screens
• [skin.xml] Update ConfigList parameters
• [skin.xml] Use new switchpixmap alphatest attribute
• Update old PlexDVR plugin screen to new HRTunerProxy plugin screen
• [skin_plugins.xml] Support ShootYourScreen plugin
• [skin_system.xml] Improve TaskList screen
• [skin_media.xml] Correct comment and move Web Cams to correct section
  • The Media Player was mislabelled as Music section
  • The Web Cams were incorrectly in the Photos section and not the Video section where they belong
• [skin_media.xml] Add YouTube plugin screens
• [skin.xml] Add initial support for auto display buttons
• [skin.xml] Add noWrap attribute to all colour buttons
• Allow multiple selections in the movie list (Prl - Pull request #26)
  • Add PNGs required for pull request #409
  • Allow multiple selections in the movie list in the easy-ui-4 repository.
• Fix up default LCD picon (Prl - Pull request #27)
  • The default LCD picon, lcd_picon_default.png (used when no valid picon can be found) is an 8-bit greyscale colourmapped 76 x 45 pixel image with alpha plane. Picons need to be 8-bit direct greyscale 170 x 40 pixel images with a black background and no alpha plane. Changed lcd_picon_default.png accordingly.
• Replace alphatest="on" with alphatest="blend"
  • This change aligns the skin with updated image processing code.
• [skin_filemanagers.xml] Update FileCommander screens
  • Add the new FileCommander file/directory information screen.
  • Remove the old definition for the FileCommander settings screen which is now replaced by the system Setup screen.
• [skin.xml] Add Setup image for FileCommander
• Fix issue #674: [skins] Increase default font size for FileList (Prl - Pull request #29)
  • Add new FileList font alias with font size 20 (code default 18) and height 25 (code default 25).
• [skin_filemanagers.xml] Add missing help buttons from FileCommander
• Add DejaVu fonts
  • This change is prompted by Pull Request #28 made by Prl but it conflicted with a pending change already in the works.
  • These open source fonts have better support none non English languages.
• Add user defined colour place-holders
• Fix issue #678: Settings and actions menu for FileCommander (Prl - Pull request #30)
  • Add screen skin FileCommanderContextMenu for new context menu in FileCommander.
• [skin.xml] Add Setup image templates Add place-holder templates for more of the Setup screens.
• [skin.xml] Correct DejaVu font file names
• Update button templates and plugin
  • Update colour buttons to latest implementation based on objectTypes attribute
  • Move colour buttons into ScreenTemplate
  • Move automatic version of MENU, INFO, TEXT and HELP buttons into ScreenTemplate
  • Remove unnecessary calls to ScreenTemplateButtonColours from through out the skin
  • Update OverlayHD plugin to latest Python support module standards (OpenViX now supports Beyonwiz style ActionMaps

OverlayHD version 1.67:

• Fix issue #673: Tidy up FileCommander list headers (Prl - Pull request #31)
  • Use two widgets for the header entries, one a name widget for the file path and the other a source with a List/TemplatedMultiContent/Listbox chain to display the file status.
  • Display the symbolic file mode, the scaled file size and the modification time in the file mode.
  • Put the File Commander file lists skin into a panel so that the panel can be used in both FileCommanderScreen and FileCommander
• Fix issue #681: Show link targets in File Commander file status (Prl - Pull request #31)
  • Add skin widgets for the link contents label, the contents themselves and a hideable separator pinstripe.
  • Reduce the height of the list so that the widgets can be placed just under the list.
• Update CutListEditor to match update in easy-ui-4 (Adoxa - Pull request #25)
• Update FileCommander mark icons
• Update ON/OFF switch images for Setup screens
• [skin_fiemanagers.xml] Update FileCommander
  • This change brings in compatibility with the latest FileCommander changes. Both the old and new style header codings are supported.
• [skin_filenamagers.xml] Change movie search font
  • Change the MovieSelection search character font to allow full access to glyphs for all languages.
• [skin_filemanagers.xml] Update MovieSelection Beyonwiz screen
  • This change adapts the Beyonwiz version of the MovieSelection screen to cope with the new file selection UI.
• [skin.xml] Minor corrections - Correct the TextNormal font size
  • Remove the forced HELP button from the Setup screen
  • Correct the title for the Screensaver screen
• [skin.xml] Update VirtualKeyBoard screen
  • Make the VirtualKeyBoard a full screen display rather than a pop up screen
  • Provide different VirtualKeyBoard screens for Beyonwiz and OpenViX
• [skin.xml] Update NumericalTextInputHelpDialog font and layout
  • Use the DejaVu font to have more support for different languages
  • Widen the columns to allow for more characters per digit
  • Remove the "<" and ">" to the left and right of "0" as these characters are not available via those buttons

OverlayHD version 1.68:

• Replace image that causes a crash in OpenViX
  • This is a replacement small black 1 x 1 pixel image. The previous version caused a crash when loaded into OpenViX 5.2 firmware.
• Improve transport control icons
• [skin_filemanagers.xml] Update Slim MovieSelection Beyonwiz screen
  • This change adapts the Beyonwiz version of the Slim MovieSelection screen to cope with the new file selection UI. (This change was missed in the 43b696c92da2a09943b6973cba46e0b3ed6b0375 commit.)
• [skin_plugins.xml] Rework and improve CutList Editor screen
  • The CutList Editor screen layout has been reworked to improve presentation and resolve clipping of the speed display.
  • There are now two versions of the CutList Editor screen to account for the different versions of the plugin on Beyonwiz and elsewhere.
• [plugin.py] Match SMSHelperFont and bump version number
  • Set default SMSHelperFont to match the new font used in skin.xml.
  • Bump the plugin version number to reflect skin and plugin changes.

Unless you find something broken I would like to get this out to users ASAP to eliminate the problems due to recent changes from annoying users.

Regards,
Ian.

[Paul_oz53]

Ian,

Congratulations, I think this is fine.

I haven't found any reason to delay the release. I see that the 201809xx beta is a minimum requirement for 1.68. Everything I explored looked fine and works, including the cutlist editor and execute cuts. No other tweaks were necessary to have it work well. I went through all the main screens and tried some odd functions like create a directory and rename a file.

I would suggest for the Virtual Keyboard, the text for the GREEN and RED buttons (OK/EXIT) be added to the buttons at the bottom of the screen but this is a small detail. I did notice that pressing OK adds the current selected character to the filename if not on OK whereas GREEN saves and exits.

[IanSav]

Hi Paul,

Congratulations, I think this is fine.

Thank you for your assistance.

I haven't found any reason to delay the release. I see that the 201809xx beta is a minimum requirement for 1.68. Everything I explored looked fine and works, including the cutlist editor and execute cuts. No other tweaks were necessary to have it work well. I went through all the main screens and tried some odd functions like create a directory and rename a file.

I will prepare the update feed shortly.

I would suggest for the Virtual Keyboard, the text for the GREEN and RED buttons (OK/EXIT) be added to the buttons at the bottom of the screen but this is a small detail. I did notice that pressing OK adds the current selected character to the filename if not on OK whereas GREEN saves and exits.

This is all as expected for the old VirtualKeyBoard. If Beyonwiz ever adopts the new version then the UI is different and much improved.

Regards,
Ian.

[sub3R]

I just had an on-line update to OverlayHD 1.68 come through. I was running f/w 17.5 20181003 at the time. The update went without issues on both our T2 & U4 (but before updating I ran OverlayHD-patch remove.sh & uninstalled other patches/scripts just to be on the safe side).

This version looks nice. I am sure there are a lot of changes/fixes, but the most obvious & pleasing to me after a very quick look were: No more live TV bleed through of the icons. No more flashing around the coloured buttons. Octal file permissions (plus other info) are shown in the header of File Commander as each file is highlighted.

I haven’t worked out yet what the selection boxes are for in the Movie List but I’m sure that will become obvious after a bit of use.

It will be good not to have to worry about OverlayHD-patch when each f/w update comes through.

Nicely done Ian, many thanks for your hard work & making a good skin even better. And to Paul for beta testing.