So as a first approach, we should use the ParagraphEditor #handleDisabledKey: behavior. Should we?
Cheers, Guille On Mon, Oct 4, 2010 at 7:29 AM, Gary Chambers <[email protected]>wrote: > Well, the short answer is "yes" if we want the (previously requested long > ago) features of being able to copy text, browse classes etc. from > selections in disabled text. > > Regards, Gary > > ----- Original Message ----- From: "Gary Chambers" < > [email protected]> > To: <[email protected]> > Sent: Monday, October 04, 2010 11:17 AM > Subject: Re: [Pharo-project] do we need handleDisabledKey: > > > > Catching up on emails after being away... will check once software update > completes... > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" < > [email protected]> > To: "Pharo Development" <[email protected]> > Sent: Friday, September 24, 2010 7:01 PM > Subject: [Pharo-project] do we need handleDisabledKey: > > > hi gary >> >> do we need handleDisabledKey: because this is not defined on the new >> editorHierarchy? >> >> http://code.google.com/p/pharo/issues/detail?id=3003 >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
