998 replies to this topic

[IanSav]

Hi Pr2,

 

So you want me to remove the "ø" glyph?

 

I think that having two shift keys will look unbalanced and not optimal.  Can I put the Euro symbol in its place to maintain the symmetry?

 

Regards,

Ian.

 

[IanSav]

Hi Adga,

 

Here are the samples of the Lithuanian keymaps.  Are they okay or would you like a change?

 

Regards,

Ian.

 

Attached Files

•  Lith0.jpg   254.83KB   0 downloads
•  Lith1.jpg   237.16KB   0 downloads
•  Lith2.jpg   195.07KB   0 downloads

[IanSav]

Hi Pr2,

 

Here is my revised French keymap.  Is this okay?

 

Regards,

Ian.

 

Attached Files

•  French0.jpg   176.23KB   0 downloads

[Pr2]

Hi Pr2,

 

So you want me to remove the "ø" glyph?

 

I think that having two shift keys will look unbalanced and not optimal.  Can I put the Euro symbol in its place to maintain the symmetry?

 

Regards,

Ian.

 

Yes replace "ø"  because it is never used in french.

[Pr2]

Hi Pr2,

 

Here is my revised French keymap.  Is this okay?

 

Regards,

Ian.

 

Yes it is OK now.

[Adga]

Hi Adga,

 

Here are the samples of the Lithuanian keymaps.  Are they okay or would you like a change?

 

Regards,

Ian.

Missing euro currency symbol.
The main character of the keypad, the letter box must be the same as the picture, and the other characters are ok

The layout of the letters could be in the picture

Attached Files

•  LT.jpg   50.53KB   0 downloads
•  Euro.png   41.04KB   0 downloads

Edited by Adga, 23 August 2018 - 12:56.

[IanSav]

Hi Adga,

 

Thank you for checking.  Are you saying that the numbers on shift level 0 and symbols on shift level 1 should go to shift level 2 and the lower / upper case characters I now have on shift level 2 should go on the top line of shift level 0 and shift level 1?

 

I have also found a few more symbols that I missed on the first pass.

 

Regards,

Ian.

Edited by IanSav, 23 August 2018 - 13:03.

[Adga]

Hi Adga,

 

Thank you for checking.  Are you saying that the numbers on shift level 0 and symbols on shift level 1 should go to shift level 2 and the characters I now have on shift level 2 should go on the top line of shift level 0 and shift level 1?

 

I have also found a few more symbols that I missed on the first pass.

 

Regards,

Ian.

Yes

[IanSav]

Hi Adga,

 

Okay, standby for an update.

 

Regards,

Ian.

[ims]

I think, there is some side effect when was changed something around key actions some time ago ... In VK help some helptexts missing - if more keys call same function.

Try in keymap.xml set same function under VirtualKeyboardActions - f.eg "prev" for RED and for GREEN and same - f.eg - "next" for YELLOW.and BLUE. See, they are as first 4 lines in actions in .xml.

 

What happens:

- in help in VirtualKeyboard helptexts will be for first founded "prev" and "last" only - in this case for RED and for YELLOW, but for any next ( GREEN, BLUE and next definitions for "prev" and "next" are missing) are ignored. 

Edited by ims, 23 August 2018 - 13:16.

[IanSav]

Hi Ims,

 

I think this is a bug in the help engine.  This was fixed on the Beyonwiz version.  I don't know if it works on OpenViX but I think it is broken there too.

 

I suppose the fastest solution would be to bring over the improved help system.

 

Regards,

Ian.

[IanSav]

Hi Adga,

 

How do these look?

 

If you need any corrections please give me detailed instructions.

 

Regards,

Ian.

Attached Files

•  Lith0.jpg   177.82KB   0 downloads
•  Lith1.jpg   168.91KB   0 downloads
•  Lith2.jpg   154.18KB   0 downloads

Edited by IanSav, 23 August 2018 - 14:03.

[ims]

Hi Ims,

 

I think this is a bug in the help engine.  This was fixed on the Beyonwiz version.  I don't know if it works on OpenViX but I think it is broken there too.

 

I suppose the fastest solution would be to bring over the improved help system.

 

Regards,

Ian.

But I think, it worked well before changes in Actions made by ....

[IanSav]

Hi Ims,

 

Actually I suspect that the new smarter ActionMaps code allows for situations that the old help engine can't process.  Would you like me to look at porting the new help system over as well?

 

Regards,

Ian.

Edited by IanSav, 23 August 2018 - 14:16.

[Adga]

Hi Adga,

 

How do these look?

 

If you need any corrections please give me detailed instructions.

 

Regards,

Ian.

Now everything is fine   

[IanSav]

Hi Adga,

 

Thank you.  I will raise a pull request with this new update. 

 

Regards,

Ian.

[IanSav]

Hi,

 

All the language changes have been submitted in Pull Request #1689.

 

Regards,

Ian.

[ims]

This Help system reads actions defined in "actions" in .py only. Nothing more, nothing less. Then any next mapping KEY_xxx to same function in keymap.xml has no effect, as I saw.

May be better then in keymap.xml f.eg

 

KEY_XYZ map to "xyz"

KEY_ABC" map to "abc"

 

and in .py call same function from more maps:

"xyz": runFunctionA ...

"abc": runFunctionA ...

 

 

and not as (in this time not working):

KEY_ABC map to "abc"

KEY_XYZ map to "abc"

 

and in python then

 

"abc": runFunctionA

 

Or, if is so good cooperate, there could be offered fix of BeyonWiz

[IanSav]

Hi Ims,

 

There are lots of fixes and improvements in the Beyonwiz help system.  Let me try and port it over so it can be reviewed by OpenPLi.

 

Regards,

Ian.

[IanSav]

Hi,

 

While people are waiting for the new help system, does anyone want to try out the new NumericalTextInput code?  Most of the changes are in cleaning up the code and offering more SMS helper options for different screen requirements.  One visible change is that all non alphanumeric characters are now available for entry via the SMS data entry method.

 

The old "search=" calling options is intended to be replaced with the new "mode=" option.  The "search=" option is still supported but if this new code is acceptable I propose to adjust all the code to remove the "search=" option and replace it with the appropriate "mode=" option.

 

No skin changes are required but I suggest that the "<" and ">" buttons are actually confusing and should be removed.  In the style of this UI users may be tricked into thinking that these physical buttons are how you enter the "<" and ">" characters.  WRONG!

 

I haven't written a /doc guide to the new code as yet.  Would people like a document explaining the removal of the "search=" option and the addition of the "mode=" option and its values?

 

I would welcome feedback from anyone who want to give this code a try.  I would also like to know if people would like me to submit this code as a pull request.

 

Regards,

Ian.

Attached Files

•  NumericalTextInput.py   7.53KB   6 downloads

Edited by IanSav, 23 August 2018 - 15:37.