[ViX_Misc] Virtual keyboard bugs

[abu baniaz]

@Mickie, have you removed the default skin? I am not referring to Vix Night HD.

 

[Mickkie]

@Mickie, have you removed the default skin? I am not referring to Vix Night HD.

I don't think I have ... I mean, the default skin would be reinstalled each time I flash the Mut@nt with the latest OpenVix version? This is what I have listed under /usr/share/enigma2:

root@mutant51:~# ls /usr/share/enigma2/
MHD-Common                         keymap.xml
Magic-FHD                          menu.xml
Magic-HD-Night                     mutant51.png
Simple_Ten_Eighty                  po
ViX-Common                         prev.png
ViX-Day-HD                         radio.mvi
ViX-Night-HD                       rc_models
YouViX-Blue                        rcpositions.xml
YouViX-Common                      setup.xml
black.mvi                          skin.xml
display                            skin_default
distro-logo.png                    skin_default.xml
encoding.conf                      skin_subtitles.xml
freesat.t1                         spinner
freesat.t2                         startwizard.xml
groupedservices                    unicable.xml
hd-testcard.mvi                    userinterfacepositionerwizard.xml
iso-639-3.pck                      videowizard.xml

Which one is the default skin?

 

[abu baniaz]

It depends what context.

Enigma2 teams set the default skin. Vix Night HD is what OpenVix uses. OpenATV uses MetrixHD.

However, there is an emergency/fallback skin.
skin_default

To complicate issues, the emergency/fallback skin in OE-A images is based on Vix Night HD.

I have merged the skin changes.

 

[Mickkie]

Yes, it is complicated! LOL!

OK, I have a /usr/share/enigma2/skin_default directory full of skin related files and also have skin_default.xml which starts with:

<skin>
	<!--	Skin: Default-OE-A skin, based on ViX Vs 0.33 by Andy Blackburn
. @www.world-of-satellite.com, based on ViX Night	-->

So I assume my default skin is OK.

Thank you for merging skin changes. Do I wait for the next OpenVix release to try it out, or is it a matter of uninstalling/reinstalling the skin plugin and it will pull in the latest merged version?

 

[Valiant]

The text entry field is not cleared out when choosing New Search as it used to be.

 

[IanSav]

Hi Mick,

The skin fixes had to be reverted due to a problem with my submission. I am working on a fix at the moment and will try again soon.

Regards,
Ian.

 

[IanSav]

Hi Valiant,

The text entry field is not cleared out when choosing New Search as it used to be.

This is not related to the new VirtualKeyBoard. I believe that this is a new feature to help users make new searches based on the current program title. You can make any changes to the current text to complete the new search. If you prefer just use the "CLEAR" button (the picture of the old style eraser on the bottom right of the keyboard grid) to clear the current text and start entering the new text as required.

Regards,
Ian.

 

[Valiant]

Thanks Ian, I obviously have not looked at the keyboard closely enough, I had not noticed the clear button before. I assumed that the new look keyboard that has appeared since I upgraded from 5.1.017 was the subject of this thread. Thankyou again.

 

[Mickkie]

The skin fixes had to be reverted due to a problem with my submission. I am working on a fix at the moment and will try again soon.

No problem Ian, take your time. I'm grateful you're looking into it. This is not a function I use daily so I can wait as long as is needed.

Meanwhile, I think (but not sure) some of the buttons on the remote do not work as they used to; e.g. the Program Up/Down, and <> do not produce any output. With no keyboard showing up I was trying to press different buttons on the remote to delete the text field, but couldn't find anything suitable. Is this affected by recent code changes?

 

[IanSav]

Hi Mick,

Yes, the button arrangements have changed. Please press the HELP button for a complete list of button operations. (HELP is also new. )

PREV and NEXT are now used to jump to the beginning or end of the text buffer respectively. To delete characters to the left of the cursor press STOP or, if your remote control has it, BACK. To delete characters under the cursor press PLAY. Please use the HELP button to go review all the command options, there are a few new options available.

By the way, the code correction has been submitted. I am waiting for the submission to be checked out and, if okay, be merged. (This skin change required some build setup changes that I have never previously needed so my first attempt missed some details.)

Regards,
Ian.

 

[Mickkie]

Excellent! I hadn't looked into the help page. Thanks!

 

[judge]

Hi Ian, the keyboard also doesn't show up on OpenViX 5.2.039 using your OverlayHD skin.
Press yellow, yellow when iin live TV mode & no keyboard.

 

[IanSav]

Hi Judge,

Sorry for the delay in responding. It looks like I have to make OverlayHD catch up with the times. I was holding it back because the Beyonwiz image hasn't updated the VirtualKeyBoard code as yet but I don't think it is fair or okay to wait any longer. I will update OverlayHD as soon as I get a free moment.

Regards,
Ian.

 

[IanSav]

Hi Mick,

How if the VirtualKeyBoard with the updated Magic-HD-Night/Noire skins?

Regards,
Ian.

 

[norhap]

https://github.com/OpenViX/skins/commit/969d276a34abb2afde013b80cc612eac5bd0cbc2
in the next release should come out, VK by IanSav was added by abu in skin_default oe the same day as release 39 ... in my skin and access to keyboard from skin_default oe with change 17-04-2019. With these changes in my case it is no longer necessary to do anything in each skin. Only changes for 1080 skin (PNG size).

 

[judge]

Ian, been away for a while, just updated all boxes to 5.2.040 & your OverlayHD skin is now working fine on the VirtualKeyBoard, thanks.

 

[IanSav]

Hi Judge,

Are you a Skype user? Are you interested in testing and reporting on improvements that can be made to OverlayHD on OpenViX?

Regards,
Ian.

 

[abu baniaz]

Just for info, OpenATV are now using the same keyboard

https://github.com/openatv/enigma2/commit/0bead1bc5af8a0b1f7e30c3e1f9557408f26a4f6

 

[IanSav]

Hi Abu,

Just for info, OpenATV are now using the same keyboard

https://github.com/openatv/enigma2/commit/0bead1bc5af8a0b1f7e30c3e1f9557408f26a4f6

They have also adopted the common NumericalTextInput. They have made a change to Ukranian that I am discussing with OpenPLi before I synchronise all the versions.

Regards,
Ian.

 

[abu baniaz]

Can you upload your button pngs to that commit for benefit of anyone who want to have premade ones to use on their skins. I have the zip file you uploaded some time ago, not sure if it is the latest one.