Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Developer
Posts: 263
Registered: ‎05-18-2011
My Device: Curve 9300, BB10 Dev Alpha C, Z10

Re: equivalent of legacy BB ActiveRichTextField

[ Edited ]

BBSJdev wrote:
A non-editable TextField is basically a Label.

This is totally wrong.

1. A Label does not allow you to select text while a non-editale TextArea does.

2. There is no non-editable TextField as I said.

--tom
Developer
Posts: 6,152
Registered: ‎07-05-2012
My Device: Playbook, Dev Alpha C, Z10 LE, Z30
My Carrier: Orange

Re: equivalent of legacy BB ActiveRichTextField

[ Edited ]

Not a very nice way to react for someone who has spent time helping you over the last few hours.

1. I was talking about non enabled TextField as we had already established that the TextField has no editable property.
2. Just set enabled to false, you can also suppress signals and override active text which is what I had to do in my app to get active text in a non-editable Text Field

 

You can also use overlays and limit the size and scope of TextArea to make it behave as if it were a non-editable TextField, there are lots of ways to achieve what I think you are looking for but you now seem to be here not to find an answer but make some kind of dogged point about TextFields so I'll leave you to figure it out, or not, on your own from now on.


If you've been helped click on Like Button, if you've been saved buy the app. Smiley Happy

Developer of stokLocker, Sympatico and Super Sentences.
Highlighted
Developer
Posts: 263
Registered: ‎05-18-2011
My Device: Curve 9300, BB10 Dev Alpha C, Z10

Re: equivalent of legacy BB ActiveRichTextField

I appreciate your time answering my questions as I already marked the thread as solved. After that, i just wanted to make it clear so that if someone comes across this thread, it won't confuse them because of incorrect statements we made here. So, I just wanted to clarify those incorrect statements.

Yes, there are many ways to implement a solution. We are here to find the simple way or 'native way' to do things by helping each others, rather than re-invent it.
--tom