incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxime Cowez <maxime.co...@gmail.com>
Subject Re: RichSelectableText-Component missing?
Date Tue, 20 Nov 2012 13:11:27 GMT
I'll correct myself ;)
RichText doesn't appear to be selectable.


On Tue, Nov 20, 2012 at 2:08 PM, Maxime Cowez <maxime.cowez@gmail.com>wrote:

> Correct me if I'm wrong, but doesn't RichText do what you describe?
>
>
> On Tue, Nov 20, 2012 at 1:42 PM, Sebastian Mohr <flex.masuland@gmail.com>wrote:
>
>> Hi,
>>
>> In a few projects I need the text to be selectable but not editable.
>> Therefore, I usually create a RichSelectableText-Component [1]
>> that should help me achieving this task. Obviously, this approach
>> is not optimal because it's extending from RichEditableText to block
>> functionality from its superclass.
>>
>> What about splitting up the functionality of RichEditableText into 2
>> classes? The proposed new inheritance chain could look like this:
>>
>>         RichEditableText < RichSelectableText < UIComponent
>>
>> If this proposal is not suitable, would you see a better way?
>>
>>
>> Sincerely Yours,
>>
>> Sebastian Mohr
>> Apache Flex Developer (PPMC),
>> Interaction Designer & Musician
>> http://www.linkedin.com/in/masuland
>>
>>
>> [1] RichEditableText-Component:
>>
>> package spark.components
>> {
>>         import spark.components.RichEditableText;
>>
>>         public class RichSelectableText extends RichEditableText
>>         {
>>                 public function RichSelectableText()
>>                 {
>>                         super();
>>
>>                         editable = false;
>>                 }
>>         }
>> }
>>
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message