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.
Results 1 to 7 of 7

Thread: Usb keyboard dongle ascii not work

  1. #1

    Title
    Junior Member
    Join Date
    Nov 2015
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Usb keyboard dongle ascii not work

    The usb keyboard dongle works correctly for the actionmap, but the ascii codes are not recognized, the problem is that GetPrevAsciiCode returns on any ascii key the value 71 not the correct ascii code.
    So every time GetPrevAsciiCode is called, the result for each key does not change, it always returns the value 71.

  2. #2

    Title
    Junior Member
    Join Date
    Nov 2015
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Looking, another team has removed these days, the VUPLUS_RC_WORKAROUND, tested the image (in the last image, the ascii code, not work): remote control 100% works, USB keyboard 100% works.

  3. #3

    Title
    Junior Member
    Join Date
    Nov 2015
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Test the .006 with driver changes: [rc] assumes remote control when name says so

    Keyboard still does not work.
    In virtual keyboard, each key returns "G"
    Inputbox, etc, etc does not work.

    Remote control:
    No more need to enable, text support.
    In virtual keyboard, the numeric keys work both as number and text (2abcABC, 3defDEF, etc, etc)
    before changes returns "G"
    Inputbox, etc, etc works.

  4. #4

    Title
    Junior Member
    Join Date
    Nov 2015
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Now the remote control works 100%

    To enable the ascii on the keyboard, you need to turn off "text support" for the remote contrrol.
    but every ascii key returns G
    Trying virtualkeyboard:
    From def selectAsciiKey(self, char)
    char value:
    The remote control returns the correct character (a, b, c, etc, etc.)
    The keyboard always returns G does not load the ascii character of the key.

  5. #5

    Title
    Junior Member
    Join Date
    Nov 2015
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Check all the files in .py (config, keyboar, consol, etc, etc,) of the two images.
    The management of ascii codes are the same.
    Infofargeneric returns: key 510 (fom enigma: ascii code)
    Actionmap returns: gotAsciiCode (InputAsciiActions >> KEY_ASCII >> gotAsciiCode)
    The problem in vix: gotAsciiCode does not return the ascii code for the key. (always G)

    The only difference is that in the vix there is the option RC code text support, which must be disabled to enable the ascii on the keyboard.

    The keyboard is recognized and loads the keymap ( default US ).

  6. #6
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,339
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    We have removed the text support
    We have removed a commit that caused this.

    This has been fixed in the Dev branch, (at least for a non-Vu mips receivers). Please wait for next Release image.

  7. #7

    Title
    Junior Member
    Join Date
    Nov 2015
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    After the changes i tried the 5.1.9 text support it's not useful,
    but always the ascii codes always return "G"
    The same thing was done by the remote control before removing the workaround (text support disable, remote control returned for each key "G" )

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.