I think TextArea's textField was private in Beta 3, but it's protected
in the final release.
That's right. Since upgrading the solution works great. Thanks so
much for everyones help.
Non selectable text area:
http://www.jessewarden.com/archives/2006/07/nonselectable_t.html
--
: [flexcoders] Re: has
anyone ever disabled selectability for a textArea??
Thanks to everyone for the help. I'm still getting an
error:
Attempted access of inaccessible property textField through a
reference with static type...
Obviously the code you guys gave me is good, so I have
I already have editable = false. That prevents user input but
doesn't stop the I-beam on mouseover and the selectability.
--- In flexcoders@yahoogroups.com, Tom Chiverton [EMAIL PROTECTED]
wrote:
On Monday 24 July 2006 23:34, JesterXL wrote:
I thought it was TextArea.selectable = false;
One way to do this would be to create a new component that inherits from textArea, but where you have overridden the event handling function(s). I would have to look to figure out what those functions are, but it shouldnt be too hard since you have the source. You really just need to find the
Try this:
mx:TextArea enabled=false disabledColor=0x33
text=Some text /
--- In flexcoders@yahoogroups.com, JClouz [EMAIL PROTECTED] wrote:
I'm sorry to be a bother but this seems like it should be so easy
but its driving me nuts.
I want to get rid of selectability/i-beam
Thanks. That does make the textArea unselectable but unfortunately
it also wipes out my background color and text color. For the life
of me I don't understand why Flex doesn't have a simple selectable
attribute included with textArea.
--- In flexcoders@yahoogroups.com, Doug Lowder [EMAIL
--- In flexcoders@yahoogroups.com, hank williams [EMAIL PROTECTED]
wrote:
One way to do this would be to create a new component that inherits
from
textArea, but where you have overridden the event handling function
(s). I
would have to look to figure out what those functions are, but it
Thanks, I've never done that sort of thing before but it sounds like
the route I may be forced to go down. Do you think it'd involve
overriding the 'mouseover' handler with an empty function?
Just seems absolutely bizarre why Flex wouldn't include a
simple 'selectable' attribute with the
]
To: flexcoders@yahoogroups.com
Sent: Tuesday, July 25, 2006 2:03 PM
Subject: [flexcoders] Re: has anyone ever disabled selectability for a
textArea??
Thanks. That does make the textArea unselectable but unfortunately
it also wipes out my background color and text color. For the life
of me I don't
Can you not just set those styles?
mx:TextArea enabled=false disabledColor=0xFF text=Some
text backgroundColor=0xC0C0C0/
Just use disabledColor instead of color in your css, mxml, or script.
--- In flexcoders@yahoogroups.com, jpc14_99 [EMAIL PROTECTED] wrote:
Thanks. That does make the
package
{
import mx.controls.TextArea;
class MyTextArea extends TextArea
{
protected override function createChildren():void
{
super.createChildren();
textField.selectable = false;
}
}
}
And then use view:MyTextArea
From:
flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of jpc14_99
Sent: Tuesday, July 25, 2006 2:47
PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: has
anyone ever disabled selectability for a textArea??
package
{
import mx.controls.TextArea
so you only have to write it once.
- Original Message -
From: jpc14_99 [EMAIL PROTECTED]
To: flexcoders@yahoogroups.com
Sent: Tuesday, July 25, 2006 5:47 PM
Subject: [flexcoders] Re: has anyone ever disabled selectability for a
textArea??
package
{
import mx.controls.TextArea
did you declare an xml namespace for it in the mxml page which calls
it? something like
xmlns:view=*
At 05:47 PM 7/25/2006, you wrote:
package
{
import mx.controls.TextArea;
class MyTextArea extends TextArea
{
protected override function
Thanks for all the help. I have it recognizing my class just fine
now. Unfortunately I'm getting this error:
Attempted access of inaccessible property textField through a
reference with static type...
So the class I'm using (below) isn't quite cutting it. Any ideas for
changes?
@yahoogroups.com
Subject: [flexcoders] Re: has
anyone ever disabled selectability for a textArea??
Thanks for all the help. I have it recognizing my
class just fine
now. Unfortunately I'm getting this error:
Attempted access of inaccessible property textField through a
reference
Out of curiosity, what is the use case to disable selection of text?
Dustin thanks so much for the assistance. In my application I'm
displaying text in a textArea that I don't want the user to be able to
select. To have the I-beam cursor popup on mouseover just looks
wrong. There's no
that after I had sent out that last message, made perfect
sense :).
From:
flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of jpc14_99
Sent: Tuesday, July 25, 2006 6:20
PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: has
anyone ever disabled selectability
TextArea just got owned.
http://www.jessewarden.com/archives/2006/07/nonselectable_t.html
- Original Message -
From: jpc14_99 [EMAIL PROTECTED]
To: flexcoders@yahoogroups.com
Sent: Tuesday, July 25, 2006 7:37 PM
Subject: [flexcoders] Re: has anyone ever disabled selectability
Thanks to everyone for the help. I'm still getting an error:
Attempted access of inaccessible property textField through a
reference with static type...
Obviously the code you guys gave me is good, so I have to assume it's
because I'm running Beta 3 Flex. I'm upgrading in the next few days so
I thought it was TextArea.selectable = false; Does it have that
property?
No, it doesn't. I can't imagine why not. I am using Beta3 though, was
the property selectable added in the release version? I didn't see it
in any of the release notes.
--
Flexcoders Mailing List
FAQ:
I thought it was TextArea.selectable = false; Does it have that
property?
No, it doesn't. I can't imagine why not. I am using Beta3 though, was
the property selectable added in the release version? I didn't see it
in any of the release notes.
--
Flexcoders Mailing List
FAQ:
22 matches
Mail list logo
