Typing in TextField does not follow the cursor

Unity Engine
1

When we type on the TextField, if the text is bigger than the TextField, the cursor leaves the screen as I keep typing, i.e. I don’t see the cursor nor the letters that I just typed.

Shouldn’t it always have the cursor viewable (e.g. if I did cmd+right arrow, it should “scroll” to the right of the text)?

Regards,
Afonso

2

I am hitting this problem too, did you ever find a solution to this one?

3

maybe this…

private void Update() {
	if (	(Input.inputString != "")  
		(m_textAreaMessageCursorIndex == m_textAreaMessage.Length - Input.inputString.Length) 
	) {
		m_textAreaMessageCursorIndex = m_textAreaMessage.Length;
		m_scrollPosition.y = Mathf.Infinity;
	}
}

and this…

void OnGui() {
	if (scrollViewHasMouseHover  Input.GetMouseButtonUp(0)) {
			m_textAreaMessageCursorIndex = 
				m_skin.textArea.GetCursorStringIndex( scrollViewRect, 
										new GUIContent(m_textAreaMessage), 
										Hangout.Gui.MouseToGUICoords(Input.mousePosition) );
		}
}
4

Actually… that doesn’t work for all cases. Isn’t there just some way I can get the textcursor position? There is only one “active” text input field that can/should be active at a time, and that input field should know what string it contains, and since it is rendering a cursor, it must know what the index is. Where do I get that from? I know I could keep going through all these calculations and conditionals, but seriously… this textcursor index should just be available.

5

This sounds like something i would like to have, too. What I want is for the text string to scroll to the left while typing a long string and the cursor remains pinned at the right edge.

6

Me three! The text cursor string index should be an accessible property that we can control, if desired. Either that, or it should not be allowed to disappear off the edge of the textfield. This is just a standard these days that users expect. Lets give them what they are used to!

7

I posted this on the wish list for the unity developers to see. Hopefully we will see this problem solved in the next Unity update.