Textfield resize

[hiflyer]

I've been looking a bit at the way textfields handles resize and I have to say that I don't like the current implementation. If you keep typing a text that is longer than what can fit in the field, the field just grows making almost any layout break.

I would like UITextField to work as close to JTextField as possible where you can specify a maximum number of columns and if you enter more text than fits the text "scrolls" to the left keeping the caret at the rightmost border. I've been looking a bit at the source code to see if it would be a simple fix but I just end up doing too major changes

What is your opinion on this matter?

[renanse]

Sounds like a bug to me... Something that should be changed. Looks like it comes down to setText and updateMinimumSizeFromContents in AbstractUITextEntryComponent. The difficulty of doing a straight up setColumns is that we allow styled text that can include different font sizes. We could base it on the main font size set on the component itself... That would make height easy enough, but we'd need some kind of font max char width to determine what columns means.

[hiflyer]

I guess the columns could as easily be handled outside of the component. Just as long as the handling of long values is correct. The reason the swing version can do it is that they only support one font in their JTextField (they use 'm' to measure btw, but you can change the method).

Will you add it as an issue?

[renanse]

I guess you mean add the positioning of the text as an issue, right? I can, but it seems like the default behavior for sizing should make sense too...

[hiflyer]

I thought of the two things as one issue actually. The text field shouldn't resize based on textlength (at least not by default. If anyone wants this then we need a plugable ResizeStrategy) and if you keep on writing when you've reached the end of the field, the text should scroll.

[Zippy]

Just wondering if any progress has been made on this; I'm using 0.7, and it's possible this has been fixed in svn, so I figured I'd check.

[renanse]

No, nothing new on this issue afaik (or can recall).