Thanks, I guess. But yowza, this is you as a Pivot implementor speaking, not very helpful advice to an end developer. Let's see, I need to understand enough about skins to be able to subclass one and get my subclass installed. Then you quote a thread with a workaround that seems to require editing the Pivot sources. If I want to edit the sources, I'd just go and edit TextAreaSkin to add an "AcceptsEnter" property.
I've tried to avoid learning too much about skins. I suspect I will eventually have to learn more, since I'm pondering creating a custom container class. But skins are a royal pain. I can sorta see how they provide an avenue to extravagant customization, like WPF control templates do. But to the average programmer, the distinction between component classes and their skins and which properties live where frequently seems arbitrary. Every time I want to set attributes on an object, I have to look two places in the javadocs, and use two different syntaxes in bxml. Add to that the fact that there's no smart editor for bxml files, and the result is it takes me an order of magnitude longer to write a bxml file than it does to write the corresponding xaml file in WPF. Sorry to rant like that, but the preceding paragraph spells out what I think is by far the greatest weakness of the Pivot framework. Meanwhile, I guess I should just submit a feature request? Seems like adding an "AcceptsEnter" property to TextAreaSkin ought to be a super easy change.
