[ViX_Misc] Virtual keyboard bugs

[abu baniaz]

So Nekrub2 is lying then?

 

[IanSav]

Hi Poster,

So Nekrub2 is lying then?

I did not, and would not, say that. There could be conditions unknown to me that could have caused the issue. All I can confirm is that the code with which I started did not support Swiss German.

Regards,
Ian.

 

[abu baniaz]

4. For German there is only the choice of the Germany layout - the Swiss German layout, which was available before is gone.

@Nekrub2, please explain yourself.

 

[adm]

As a matter of interest what is the floating "INS" text shown in the screen shot of the German keyboard and which is also present (in a slightly different place) on the English keyboard I have configured? Is it meant to be a toggling Insert/Replace and if so how is it selected?

 

[Huevos]

As a matter of interest what is the floating "INS" text shown in the screen shot of the German keyboard and which is also present (in a slightly different place) on the English keyboard I have configured? Is it meant to be a toggling Insert/Replace and if so how is it selected?

INSert / OVeerwRite. Press the info key.

 

[IanSav]

Hi,

INSert / OVerwRite. Press the INFO key.

You can also press the HELP button to get help with using the updated VirtualKeyBoard.

Regards,
Ian.

 

[nekrub2]

@Nekrub2, please explain yourself.

Hi Abu Baniaz

Before when I clicked on the yellow button I instantly got a different keyboard, but not a list of choice. As a result by click I could find a layout that had for instance in uppercase above ü è. For me it is obvious that if you provide a list and have different layouts for english, you should also have different ones for German etc.
Anyway, the key for ok (green) has gone.

Please don't hit on Ian who does an excellent job.

nekrub2

 

[IanSav]

Hi Nekrub2,

Anyway, the key for ok (green) has gone.

Is this a bug report or a problem? If so, what skin are you using. If you have a screen capture of the problem I will try and sort it out ASAP.

By the way, Huevos has just asked me to convert a few more skins (Bello and Confluence). I will try and look at these over the weekend.

Please don't hit on Ian who does an excellent job.

Thank you for your support. It is appreciated.

Regards,
Ian.

 

[birdman]

By the way, Huevos has just asked me to convert a few more skins (Bello and Confluence).

I've already started on Confluence and should be able to finish it this weekend. I could PM you what I've done once complete, to help with consistency (you might spot something I've missed)?

 

[IanSav]

Hi Birdman,

I've already started on Confluence and should be able to finish it this weekend. I could PM you what I've done once complete, to help with consistency (you might spot something I've missed)?

I would be happy to help in any way I can.

Regards,
Ian.

 

[IanSav]

Hi Birdman,

While you are adjusting Confluence do you want to make the matching changes in the rest of the related / shared code skins?

Regards,
Ian.

 

[birdman]

While you are adjusting Confluence do you want to make the matching changes in the rest of the related / shared code skins?

Do you mean the other ViXBMC ones?
I could have a look for commonality - or, given that the keyboard pops-up over everything else anyway, I could just put it all into ViXBMC_Common(?).

PS: I finally got a correctly-sized background in the correct place this evening...

 

[IanSav]

Hi Birdman,

Do you mean the other ViXBMC ones?
I could have a look for commonality - or, given that the keyboard pops-up over everything else anyway, I could just put it all into ViXBMC_Common(?).

From what I noted there is commonality among the ViXBMC skins. The VirtualKeyBoard screen is in the file "skin_ViXBMC_1080_Common.xml" in "ViXBMC_1080_Common" and is shared by all the skins. Each skin that uses this common file will need to have the "VirtualKeyBoard" font alias and parameters added. If you want to remove legacy support you can follow the instructions in the documentation file.

PS: I finally got a correctly-sized background in the correct place this evening...

Some skins have the VirtualKeyBoard decorated with graphical backgrounds. This are often more difficult or tedious to update.

Regards,
Ian.

 

[nekrub2]

Hi Ian

In order not to have a skin specific issue I temporary switched to the default skin. With the virtual keyboard Local de_DE but also on en-EN or en_US have no more the ok key in the button row. The green button still work.

For any reason OpenWebif does not work, despite of having connection from my laptop to the box through DCC (FTP). Will have to ask my kids to make a screenshot by mobile. Is there any other file from my box which could help you?

Thanks a lot nekrub2

 

[birdman]

From what I noted there is commonality among the ViXBMC skins. The VirtualKeyBoard screen is in the file "skin_ViXBMC_1080_Common.xml" in "ViXBMC_1080_Common" and is shared by all the skins.

But the VirtualKeyBoard parameter setting (which defines the size of the keys) is defined per-skin. Mind you, this seems ot make no sense given that the position/sizes set in the Common code are dependent on its set value.

Each skin that uses this common file will need to have the "VirtualKeyBoard" font alias and parameters added. If you want to remove legacy support you can follow the instructions in the documentation file.

I was going to leave it there to start with, but given that legacy support code doesn't exist it may as well go at the same time.

Some skins have the VirtualKeyBoard decorated with graphical backgrounds. This are often more difficult or tedious to update.

This is one. It's basically almost-black (so that any undefined keys look the correct colour), but does have a transparent border, which is what was causing the issue - until I realized it was not symmetric...

 

[nekrub2]

Default Skin - Keyboard de_DE


Army MoodBlue Skin - Keyboard de_DE

 

[birdman]

But the VirtualKeyBoard parameter setting (which defines the size of the keys) is defined per-skin. Mind you, this seems to make no sense given that the position/sizes set in the Common code are dependent on its set value.

Remembered later that this is because the parameters are set in a block, and others are skin dependent. The code only seems to cater for one <parameters> block.

 

[IanSav]

Hi Nekrub2,

The first image shows that the images for the VirtualKeyBoard are missing from your copy of the skin_default. The second image shows that the skin Army MoodBlue has not been updated.

The first issue is a problem. The second required the skin author to update their skin.

What happens if you select one of the default OpenViX skins?

Regards,
Ian.

 

[Huevos]

Army is not a vix skin. Must be coming fron ATV.

 

[ccs]

Army is not a vix skin. Must be coming fron ATV.

That could explain a lot.