thanks! On Jun 30, 2010, at 10:55 PM, Denis Kudriashov wrote:
> I found that when color selector tools opened for both gradient colors > they not change same GradientStyle instance. > They just copy origin style with new color (first or last). Its not siutable > for user. > > > I add another fix > > 2010/6/28 Stéphane Ducasse <[email protected]> > Cool! > > Stef > > On Jun 27, 2010, at 11:19 PM, Denis Kudriashov wrote: > > > I done slice for this. See > > http://code.google.com/p/pharo/issues/detail?id=2595 > > > > 2010/6/27 Denis Kudriashov <[email protected]> > > I can't see full morph appearance. I just see what color I select. > > But It's nothing because I need see my little changes in full morph > > appearance. > > > > For example color of button should satisfy color of pane. And when I change > > button color I want immediately see full picture of my application view. > > > > I think It is very important for UI design. > > > > 2010/6/27 Stéphane Ducasse <[email protected]> > > > > I do not understand because you can see the selected color in the selected > > color little pane. > > Is it not what you need? > > Stef] > > On Jun 27, 2010, at 11:53 AM, Denis Kudriashov wrote: > > > > > I try last Pharo 1.1 rc2 10.06.10. > > > > > > I found that tool for changing color by user is changed. ColorPickerMorph > > > is removed. Now I can't dynamically change color by mouse and see my > > > changes immediately. Now I must select color in new tool, press ok > > > button. And after that tool close and I must open it again if I dont like > > > my changes. > > > > > > It is bad behavior compare with pharo 1.0/squeak. But I really like new > > > color picker morph. > > > > > > New tool is ColorSelectorDialogWindow. > > > How I can hookup It for tracking color selection? > > > Maybe I must add some event triggering in #basicSelectedColor: method. > > > But I see many #changed: sends in #basicSelectedColor: method. And maybe > > > I already can implement some dependent class for needed stuff. > > > > > > What you think? > > > _______________________________________________ > > > 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 > > _______________________________________________ > 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
