Pierre Hébert In an old post, someone had a bug with Jay M posted a suggestion about the script editor, and you…
Pierre Hébert In an old post, someone had a bug with Jay M posted a suggestion about the script editor, and you suggested to not show the keyboard automatically.
Testing a lot with the script editor, in my opinion it will be better to not show it right after you open the app (and also when you close the drawer) and leave it to the user as a normal textbox (so it is shown when you click)
But maybe in general people like it to do that.
Comments? Opinions?
]]>« Hi everyone :) (Previous Post)
(Next Post) Not sure if it was already requested, or if it’s implemented but can’t find it, but I really wish there’s a way to… »
< ![CDATA[
That was me it wasn’t a bug it was just a suggestion to have an option to lock scripts because I sumtyms end up editing them by accident because the keyboard shows straight away.
]]>
< ![CDATA[
I agree with keyboard closed until field tapped.
]]>
< ![CDATA[
Agreed
]]>
< ![CDATA[
Agree
]]>
< ![CDATA[
Pierre Hébert? (In case you missed the post)
]]>
< ![CDATA[
Yes I missed it (was busy with other things this day…).
No problem, it make sense, I will do it for the next version.
]]>
< ![CDATA[
Done. But I am wondering: when tapping on the textfield when the drawer is open, should the keyboard be displayed right now, or should the user tap a second time to display the keyboard ? It seems to me that both are valid behaviors, but that may be a matter of taste.
]]>
< ![CDATA[
Personally, when you tap to open the keyboard is because you tapped where you want the cursor(pointer) to be.
If you tap to close the drawer is because you(I) want to close the drawer, then I’ll tap when necessary to open the keyboard.
Maybe you can make the shadow to dim all the code text. In phones this won’t be noticeable, in tablets this will help to understand that you need to tap twice: once to close the drawer, again to start writing.
]]>
< ![CDATA[
That works for me
]]>
< ![CDATA[
Me 2
]]>
< ![CDATA[
Me 3
]]>