RemoteXY community — Why the intermediate dialogs between the Edit box and the Keyboard ?

Re: Why the intermediate dialogs between the Edit box and the Keyboard ?

null@example.com (Daba) — Sat, 11 Aug 2018 08:30:04 +0000

Another problem with the Edit box is that it automatically populates it with the value the control currently has, which is unhelpful because the only reason for using the control is that you want to change the value.

Say I have "123" in the control's value, and I want to change it to "456". I press the control, and it brings up the "Enter New Value" dialog with "123" already populated. To change this to "456" I have to press "backspace" 3 times, before entering the new number.

Even worse if it is a string with 20 characters, for example.

Re: Why the intermediate dialogs between the Edit box and the Keyboard ?

null@example.com (Guillaume) — Sat, 07 Oct 2017 22:25:06 +0000

I understand the need of an intermediary step between edit box and keyboard, but why the user need to know about it? I mean, there is like 99.9% chance the user will press "Enter", not "Cancel" So in my opinion, this is an uneccessary step, which could be automated.

Re: Why the intermediate dialogs between the Edit box and the Keyboard ?

null@example.com (remotexy) — Sat, 07 Oct 2017 18:08:20 +0000

Hello,
There is a problem when the input field is at the bottom of the screen. The keyboard hide it field. The input field is not a native view control. It drawed as graphical. The keyboard does not understand what need to move the screen. Implementing this solution requires a lot of code that will implement the data entry in the field as well as scrolling the screen.
Мay be in the future..

Why the intermediate dialogs between the Edit box and the Keyboard ?

null@example.com (Guillaume) — Fri, 06 Oct 2017 04:43:40 +0000

Hello,

I don't understand why there is an intermediate dialog ("Enter new value") between the Edit box and the keyboard. Why not show the keyboard directly when you press the Edit box ?