"TextField" ?

[mrlacey]

How (and why) is there a new TextField control?
I don't see what this adds beyond TextBox.
Is this just about creating a name that is more familiar to people coming from other platforms?
Will this control also make it back to WinUI3 so it can be used there, too?

[dotMorten]

@mrlacey I searched the entire Reactor library for TextInput and didn't find any controls by that name. Only thing I found was ColorPicker.IsColorChannelTextInputVisible.

I do see TextField which is the Reactor wrapper around TextBox though.

[mrlacey]

Ok, Yes "TextField", not "TextInput"
I obviously find it so confusing, I typed the wrong word entirely

[dotMorten]

Gotcha. Yeah I’ve have some of the same thoughts. On one hand having the elements use different names to avoid type conflicts makes sense, it also means having to learn about the mapping of all the equivalent WinUI to reactor types and I often spend a lot of time trying to figure out what to type to get the UI component I want. Intellisense isn’t super helpful because of the sheer amount of extension methods it shows. I’m not sure what the right solution to that is though.

[codemonkeychris]

yeah, i'll fix this right now - it should be TextBox to align with WinUI... initially it went with the SwiftUI name... boo!... PR incoming.

[codemonkeychris]

Fixed: #387

will remove TextField in a few minutes