Community
Participate
Working Groups
Build Identifier: There are some former bug reports (bugs 149662 and 196846) beeing declined. Some newsgroup posts also addressed this "problem" earlier. I cannot imagine that this is *that* difficult to enable this feature. Reproducible: Always
We already have a password box, it is: new Text(parent, SWT.PASSWORD). I don't understand why people need a styled text password box. Why our password box isn't good enough for you ?
Why do people need a styled text password box? Maybe the are delighted with the possibilities StyledText offers and don't want to miss it in their ui projects. Maybe they just take this feature for granted since even its kid brother (Text) supports it. Fact is: this is not the first request of that kind. Imagine following scenario: there is a generic gui built on demand according to a set of meta data. These meta data contain specific descriptions of how to edit different kind of data - numeric, alphanumeric (plane text as well as text spiced with pictograms/icons).. maybe date/time, ip-addresses and so on. There is one widget for all that different purposes - StyledText. It just has the most comfortable API.. and it also implements all the bidi stuff. The idea is: initialize it once and go on using it transparently (no instanceof magic) in the source code.
It's not an unwordly approach. I'd even go one step further and append the possibility of hidin' content to TextStyle. So it would be possible to use this feature in a passive way (TextLayout), too. I also miss a StyledText constructor with a TextStyle argument instead of initializing all the things manually. Just think of kinda "inline" editors within custom dialogs and widgets.
After all that time... no chance? I think, the benefits described in the previous posts speak in this features favour.
...ain't just the focus of development, hu? There's a possible solution: to use GlyphMetrix, StyleRanges and a PaintObjectListener. But: on some platforms (Linux/GTK) the typed character is first shown clearly and then as an asterisk. And: it's not a really straight forward solution.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
Nothing was done for this yet, so the "issue" still remains ;(
