OpenVix 5.4 Numerical text input not working

[seagen]

Hi i have a question about the numerical text input not working anymore only the VirtualKeyboard is working.
The numerical buttons have been locked and dont respond anymore.

I understand that some like the Virtual keyboard very much but i see no good reason why the numerical input have been locked out?
If i upload the ConfigList.py from OpenVix 5.3 all works just fine but of cause then i have revert back all keys to old style.

I really hope that this can be worked out so we can choose how to input text again

[ccs]

... can I add that I only ever see the virtual keyboard (even in 5.3) in epg search, everything else (eg inputting wifi passwords) comes up with numerical text input.

Do I have to enable the virtual keyboard, or am I just getting old?

[abu baniaz]

You have to press the text key to show the virtual keyboard.

That being said, people should not be prevented from using the phone style input if that is their preferred method.

[Ev0]

Yes the new system is crap (and that is being polite).

[Andy_Hazza]

I’m all for the VK method, loads quicker at inputting than the old crappy mobile phone method. But as @Abu says, should still be an option.


Sent from my iPhone using Tapatalk

[seagen]

Maybe @IanSav can shade som light on this issue

[IanSav]

Hi Seagen,

This thread has just been brought to my attention.

The NumericalTextInput system should still be fully functional and available to all users. I will update my test box to the latest 5.4.002.007 (Developer) build to investigate the issue. Could you please give me some example screens that manifest the issue. If you are not using 5.4.002.007 then may I please know what build you are using.

Regards,
Ian.

[IanSav]

Hi Ev0,

Yes the new system is crap (and that is being polite).

If you can please remain polite and tell me what aspect of the UI you consider "crap". I consider the user interface to be my primary area of interest in Enigma2. If you have found something that is broken I would like an opportunity to fix it. If you have an issue with designed changes then I would like to know the issue specifics so that I can consider if there are workable / appropriate changes that can be adopted.

Regards,
Ian.

[Ev0]

Hi Ev0,

If you can please remain polite and tell me what aspect of the UI you consider "crap". I consider the user interface to be my primary area of interest in Enigma2. If you have found something that is broken I would like an opportunity to fix it. If you have an issue with designed changes then I would like to know the issue specifics so that I can consider if there are workable / appropriate changes that can be adopted.

Regards,
Ian.

Ian I have pointed out the issue's to you several times on various (off topic) threads over the last couple of months as you well know.

I told you which plugins were not working correctly, I gave you screen shots, ipk's and links to git's of some of the plugins as you said you would take a look and fix things (then said it's not your place to fix things and you are not responsible for things no longer working as they did).

I made it clear that numerical input was no longer working and your reply was use the VK as it's better.

You did nothing except repeat the same mantra of we must not hold enigma2 progress back due to plugins.

[IanSav]

Hi Ev0,

Ian I have pointed out the issue's to you several times on various (off topic) threads over the last couple of months as you well know.

I told you which plugins were not working correctly, I gave you screen shots, ipk's and links to git's of some of the plugins as you said you would take a look and fix things (then said it's not your place to fix things and you are not responsible for things no longer working as they did).

I made it clear that numerical input was no longer working and your reply was use the VK as it's better.

You did nothing except repeat the same mantra of we must not hold enigma2 progress back due to plugins.

Have you actually tested all the issues against the current code? I suspect not. You seem to want to complain rather than be constructive. You are posting quotes and comments allegedly from me with which I totally disagree and dispute. All comments need to be taken in consideration of the context and the tone of the conversation.

Changes have been made to ConfigList.py that should completely restore *all* code and plugins, both internal and external, to their previous operational status. No one has made me aware of *any* further issues in this area.

As a result of your, and other feedback, the "<" and ">" buttons have been returned to the delete functions and the new list navigation options that were proposed for these buttons has been made inactive (but still available if a user wishes to have the newer functionality).

I believe that these changes have fully addressed all your objections yet you still feel inclined to spam the forums, with totally off topic posts, regarding complaints about me that, I believe, are now without basis or justification. If you still know of any problems *directly* attributable to changes I have made then I welcome appropriately detailed bug reports in an appropriate thread. Please notify me of the thread so I can investigate the issues for you.

Regards,
Ian.

[IanSav]

Hi,

To bring this thread back on topic, I have found that "Fallback Tuner Setup" screen is most definitely broken. Not only does NumericalTextInput not work but neither does the VirtualKeyBoard. I am investigating that code now but would welcome further reports from *any* users of any other screens that have issues.

Regards,
Ian.

[IanSav]

Hi,

Just another update, I believe that Huevos has completely refactored this code.

Please alert us to any other issues.

Regards,
Ian.

[Ev0]

Hi Ev0,

Have you actually tested all the issues against the current code? I suspect not. You seem to want to complain rather than be constructive. You are posting quotes and comments allegedly from me with which I totally disagree and dispute. All comments need to be taken in consideration of the context and the tone of the conversation.

Changes have been made to ConfigList.py that should completely restore *all* code and plugins, both internal and external, to their previous operational status. No one has made me aware of *any* further issues in this area.

As a result of your, and other feedback, the "<" and ">" buttons have been returned to the delete functions and the new list navigation options that were proposed for these buttons has been made inactive (but still available if a user wishes to have the newer functionality).

I believe that these changes have fully addressed all your objections yet you still feel inclined to spam the forums, with totally off topic posts, regarding complaints about me that, I believe, are now without basis or justification. If you still know of any problems *directly* attributable to changes I have made then I welcome appropriately detailed bug reports in an appropriate thread. Please notify me of the thread so I can investigate the issues for you.

Regards,
Ian.

The OP of this thread has alerted you to the issue I was and still am talking about.

Numerical text input does not work in plugins.

[Huevos]

Nothing wrong with current version of Fallback tuner config screen. I just tested it. This code has not changed in months. The refactor code is not yet in the public domain.

[IanSav]

Hi,

I was incorrect in claiming that the Fallback Tuner Screen was broken. I was misusing the UI in that the item I was trying to edit was a ConfigSelection and *NOT* a ConfigText as I thought it to be.

We are still awaiting a complete bug report detailing the screens that have an issue so that they can be corrected.

@Ev0: The OP has not provided any details about the issue. Both Huevos and I have tried various screens and we have not yet found anything wrong. If you have a list of screens that are broken then please provide the list.

We need complete and detailed bug reports if issues are to be corrected. Bug reports along the lines of "It is broken" can't be fixed when there is no information about "It".

Regards,
Ian.