Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.

View Entry Info: Virtual keyboard bugs

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
5.2.011
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Attachments
Page 9 of 10 FirstFirst ... 78910 LastLast
Results 121 to 135 of 146

Thread: Virtual keyboard bugs

  1. #121
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,421
    Thanked 9,146 Times in 6,224 Posts
    @Mickie, have you removed the default skin? I am not referring to Vix Night HD.

  2. #122

    Title
    Senior Member
    Join Date
    Nov 2017
    Posts
    201
    Thanks
    35
    Thanked 25 Times in 23 Posts
    Quote Originally Posted by abu baniaz View Post
    @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:

    Code:
    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?
    Kind regards,

    Mick

  3. The Following User Says Thank You to Mickkie For This Useful Post:

    abu baniaz (15-04-19)

  4. #123
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,421
    Thanked 9,146 Times in 6,224 Posts
    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.

  5. #124

    Title
    Senior Member
    Join Date
    Nov 2017
    Posts
    201
    Thanks
    35
    Thanked 25 Times in 23 Posts
    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:
    Code:
    <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?
    Kind regards,

    Mick

  6. #125
    Valiant's Avatar
    Title
    Senior Member
    Join Date
    May 2016
    Posts
    144
    Thanks
    99
    Thanked 37 Times in 32 Posts
    The text entry field is not cleared out when choosing New Search as it used to be.
    VU+ Uno 4K SE Twin FBC Tuner 1TB HDD - Magic-FHD skin
    TV - LG OLED55CS6LA
    Remote - Logitech Harmony One

  7. #126

    Title
    Senior Member
    Join Date
    Mar 2015
    Posts
    1,184
    Thanks
    31
    Thanked 371 Times in 239 Posts
    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.

  8. #127

    Title
    Senior Member
    Join Date
    Mar 2015
    Posts
    1,184
    Thanks
    31
    Thanked 371 Times in 239 Posts
    Hi Valiant,
    Quote Originally Posted by Valiant View Post
    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.

  9. #128
    Valiant's Avatar
    Title
    Senior Member
    Join Date
    May 2016
    Posts
    144
    Thanks
    99
    Thanked 37 Times in 32 Posts
    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.
    VU+ Uno 4K SE Twin FBC Tuner 1TB HDD - Magic-FHD skin
    TV - LG OLED55CS6LA
    Remote - Logitech Harmony One

  10. The Following User Says Thank You to Valiant For This Useful Post:

    IanSav (15-04-19)

  11. #129

    Title
    Senior Member
    Join Date
    Nov 2017
    Posts
    201
    Thanks
    35
    Thanked 25 Times in 23 Posts
    Quote Originally Posted by IanSav View Post
    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?
    Kind regards,

    Mick

  12. #130

    Title
    Senior Member
    Join Date
    Mar 2015
    Posts
    1,184
    Thanks
    31
    Thanked 371 Times in 239 Posts
    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.

  13. #131

    Title
    Senior Member
    Join Date
    Nov 2017
    Posts
    201
    Thanks
    35
    Thanked 25 Times in 23 Posts
    Excellent! I hadn't looked into the help page. Thanks!
    Kind regards,

    Mick

  14. #132

    Title
    ViX Beta Tester
    Join Date
    Jan 2011
    Posts
    14,099
    Thanks
    3,389
    Thanked 4,102 Times in 3,198 Posts
    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.

  15. #133

    Title
    Senior Member
    Join Date
    Mar 2015
    Posts
    1,184
    Thanks
    31
    Thanked 371 Times in 239 Posts
    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.

  16. The Following User Says Thank You to IanSav For This Useful Post:

    judge (23-04-19)

  17. #134

    Title
    Senior Member
    Join Date
    Mar 2015
    Posts
    1,184
    Thanks
    31
    Thanked 371 Times in 239 Posts
    Hi Mick,

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

    Regards,
    Ian.

  18. #135

    Title
    Senior Member
    Join Date
    Jul 2011
    Posts
    189
    Thanks
    84
    Thanked 66 Times in 46 Posts
    https://github.com/OpenViX/skins/com...612eac5bd0cbc2
    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).
    Last edited by norhap; 23-04-19 at 11:46.

  19. The Following User Says Thank You to norhap For This Useful Post:

    Andy_Hazza (23-04-19)

Page 9 of 10 FirstFirst ... 78910 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.