[no Bug] Virtual keyboard issues (1 Viewer)

[greybox]

1. Virtual keyboard always had a loop feature, meaning we could get, for example, from "a" to "j" by pressing left arrow two times. Now we are stuck at the left edge of the keyboard if we use left arrow. To get from "a" to "j" we have to press right arrow 9 times - what a waste of time and battery! Right, up and down arrows work fine as before. Please keep in mind this is not a feature request - everything worked fine before - we had a seamless loop in all directions in alfa, so I take it as a bug.

2. Minor cosmetic issue - the word "STANDARD" is wider then the key and not centered.

3. Switching to SMS keyboad is very convenient, but please keep in mind that not everybody knows the SMS layout by heart. I would suggest to display the SMS layout when it is active.

4. National language support for the virtual on-line keyboard is highly desirable. I know it is in mantis and scheduled for year 2015: 0003228: Virtual Keyboard should load strings from language file - MediaPortal Bugtracker. But considering the international nature of MediaPortal, please, please, please make this happen sooner!

MediaPortal Version: MediaPortal 1.2.0 Beta
MediaPortal Skin: Default Wide with MePo added and analog clock removed
Windows Version: Windows 7 Ultimate
CPU Type: Intel Core I7 2.8GHz
HDD: WDC SATA-2 80GB; Samsung SATA2, 750GB; Blu Ray drive: LiteOn iHES108
Memory: 4GB DDR3
Motherboard: Asus P7P55D PRO
Video Card: ASUS GeForce 9600GT Silent 650MHZ 512MB 1.8GHZ DDR3 PCI-E Dual DVI-I HDCP HDTV
Video Card Driver: Latest
Sound Card: IDT High Definition
Sound Card AC3: Optical out
Sound Card Driver: Latest
1. TV Card: Hauppauge WinTV HVR-1800, PCIe
1. TV Card Type: analog, ATSC
1. TV Card Driver: Latest
2. TV Card: Twinhan AD-SE200 (1028), PCIe
2. TV Card Type: DVB-S
2. TV Card Driver: Latest
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider: FTA/Cable/OTA
HTPC Case: Custom
Cooling:
Power Supply:
Remote: Universal, URC 200
TV: Samsung 58" 1080p Plasma HDTV (PN58B530)
TV - HTPC Connection: DVI/HDMI

 

[mbuzina]

a-d: +1

 

[Deda]

You're not alone in this , not to mention when you type 20 letters and press left too many times it starts to delete your hardworked txt so you need to do all again

 

[mlburgoon]

would love to have these issues corrected. Especially the looping part.

 

[greybox]

would love to have these issues corrected. Especially the looping part.

At least to confirm the bug (item #1), which is very easy to do..

 

[elliottmc]

would love to have these issues corrected. Especially the looping part.

At least to confirm the bug (item #1), which is very easy to do..

I can confirm this behaviour. Right now, it is by design, so not strictly a bug. However, I do take your point, and I also feel that it is incorrect.

Mark

 

[Seidelin]

At least to confirm the bug (item #1), which is very easy to do..

I think a patch would be welcome. I don't like the new behavior either, probably it was changed by mistake when VK was reworked.

 

[elliottmc]

Hi,

In GUIKeyboard.cs we have

        case Action.ActionType.ACTION_MOVE_LEFT:
          if (_useSmsStyleTextInsertion && _currentKey == 0)
          {
            Press(Xkey.XK_BACKSPACE);
            smsLastKeyPressed = -1;
            return;
          }
          break;

This suggests that the delete behaviour with the left arrow should only happen when using SMS style text insertion. Need to check.

Edit: this is correct. At least, when the keyboard button reads 'SMS' (so I assume the standard text entry is used) then 'left' when you are already on the left acts as delete. If you are using the standard text entry, it does not.

IMO, we need to differentiate these keyboards properly, so that the SMS keyboard looks like a SMS keyboard.

Mark

 

[SilentException]

Hi,

elliottmc is right. Keyboard is looping when in standard mode. Why would anyone need looping in SMS mode anyhow?

IMO, there is nothing to fix, at least not for 1.2, other then making SMS and STANDARD input modes more distinguishable.

 

[Deda]

IMO, there is nothing to fix, at least not for 1.2, other then making SMS and STANDARD input modes more distinguishable.

That's the whole point . If it tricked me, than I think it will trick many .