search

artemevil83 / app-inventor-for-android

Automatically exported from code.google.com/p/app-inventor-for-android
0 stars 0 forks source link

TextBox still works (can still be typed in) even if disabled #26

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
ANDROID OS: 2.1 Update 1
PHONE: Samsung Vibrant (SGH-T959)

DESCRIPTION OF ISSUE:

I made an app that has five text boxes with the first text box 
disabled so that users aren't able to type or edit the text that is in 
it, but when the app starts/initiates, the first text box is in focus 
and the keyboard pops up allowing users to type/delete the text within 
that text box even when it has been disabled. It is only till I click 
elsewhere to take text box 1 out of focus that I am unable to edit the 
text within the first text box.

Look like this: 

1) [text box 1] ... disabled, but is in focus when the app starts. (Please 
refer to file "on initiate.jpg")
Users are still able to edit/type in this box. (Please refer to file "edit.jpg"
2) [text box 2] ... enabled 
3) [text box 3] ... enabled 
4) [text box 4] ... enabled 
5) [text box 5] ... enabled

Original issue reported on code.google.com by RZh...@gmail.com on 9 Sep 2010 at 7:34

Attachments:

GoogleCodeExporter commented 9 years ago 
In the TextBox properties set it to 'disable' when you dragged and created it. 
The default setting is 'Enabled'.

Original comment by sen...@gmail.com on 20 Sep 2010 at 9:51

GoogleCodeExporter commented 9 years ago 
@sendGV: that doesn't work when depending on what the user chose the field 
should be editable or not.

I have the same issue, "disabled" darkens the input area, but does not stop the 
field from being modified, you just don't get a blinking cursor.

Original comment by irwin....@gmail.com on 23 Sep 2010 at 12:48

GoogleCodeExporter commented 9 years ago 
I have had this same problem every time I try to disable text boxes as well.

Original comment by jim.stephen@gmail.com on 23 Sep 2010 at 6:29

GoogleCodeExporter commented 9 years ago 
I have a similer issue. I can stop the text boxes from accepting text, but when 
i scroll up and down in the App i can suddenly type in the box.

Original comment by armcl...@gmail.com on 8 Oct 2010 at 8:41

GoogleCodeExporter commented 9 years ago 
I have seen this bug as well.  I would add that it would be better if the 
keyboard did not appear when the app opens.  In my app, there is only one test 
box, and after the first time the app is run, that box is disabled.  Yet 
changes can be made in the text box and the keyboard opens.  My workaround for 
now is to regularly rewrite the correct value into the text box.

Original comment by robert.s...@gmail.com on 10 Oct 2010 at 5:25

GoogleCodeExporter commented 9 years ago 
Same issue, however when my app starts the text box doesn't allow anything to 
be entered by the keyboard...its not until the text is changed via the app 
itself when the text box can be edited by the keyboard. The weird thing is that 
only 1 of the 4 text boxes can be edited (even though they are all disabled)

Original comment by akrutsinger@gmail.com on 23 Oct 2010 at 11:10

GoogleCodeExporter commented 9 years ago

Original comment by ma...@google.com on 28 Oct 2010 at 7:49

GoogleCodeExporter commented 9 years ago 
I also encountered this bug and it is easily reproducable even in the emulator. 
 The issue is that the textBox will accept text input whenever it has focus 
even if it is disabled.  To reproduce:
   1) create a button which toggles the Enabled state of an entry box
   2) Tap into the box when it is enabled
   3) Tap the button to flip the state of the TextBox to disabled (notice the TextBox is still highlighted)

Now when you tap on the disabled field the keyboard will come up and you can 
enter text.

Original comment by drusi...@gmail.com on 28 Dec 2010 at 2:16

GoogleCodeExporter commented 9 years ago 
Well this is starting to sound like an app-inventor issue, not good. Hope they 
fix that in the next build.

Original comment by seal...@gmail.com on 16 Jan 2011 at 1:18

GoogleCodeExporter commented 9 years ago 
Unfortunately, this looks like a bug in the Android OS itself, with no 
workarounds that App Inventor can take advantage of:
http://code.google.com/p/android/issues/detail?id=2771

Original comment by k...@google.com on 15 Mar 2011 at 9:48