2
« on: September 03, 2013, 09:20:24 AM »
Thanks, Enay, yes, I agree, it is a system problem, not a fault of NGUI.
Here's how I used your OnClick suggestion: I created a table of 5 input rows with the UITable script and checked the sort option. Named the rows Row2, Row3, etc, reserving Row1. Then, in the OnClick event (I'm using Playmaker to program this), I rename whatever input row is clicked to Row1 which, because of the sort function of UITable, moves whatever row was clicked to the top and therefore above the iPhone keyboard. When the user hits return, ending input, I rename the input row back to its original name which, again because of sort, moves it back to its original position.
Perhaps not too elegant a solution, since it doesn't really scroll as you suggested, but it works. Is there a simple way to scroll the screen instead which I am missing?