2008/11/21 Stéphane Ducasse <[EMAIL PROTECTED]>: > If you want to have fun > > do > > Object new setHaltOnce > > redefine > > Object>>isTransparent > self haltOnce. > Beeper beep. > ^ false > > > I found a kind of fix by initializing correctly SimpleBorder (my fix is not > totally convincing yet since it crashed the image). > SimpleBorder is used in BorderedSubpaneDividerMorph > > Now what is amazing to me is the number of time isTransparent is invoked > on Object when just typing text, I think that there is bogus there. > > If one UI expert can have a look this would be great. >
There are many senders of isTransparent . Much of uses showing a conceptually wrong usage of colors. Maybe its faster to write: fillStyle isTransparent ifTrue: [^ self ]. instead of: fillStyle fill: someArea. and then in #fill: it can check if no fill necessary. That's one of the moves which we discussed with Gary, that it is up to fill style to determine how to fill an area. It should play role a full object with own behavior , not just holder of static information like color & gradient. But currently, if you look at uses of colors and gradients - they used as value holders, and this is why all those #isTransparent #isTransulent, instead of simply dispatching into this object and let it decide how to fill / draw things and with what color. > Stef > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
