Hi Fernando,
Now I see #initializeTranslucentPatterns is there.
BUT: I expected it ON THE CLASS SIDE since usually initializing class variables
is done
with class side methods. This is my opinion also a better style of coding
in
Smalltalk.
For instance if one resets a class variable in the browser:
TranslucentPatterns := nil.
or sets it to other values for experiments one can easily reinitialize by
sending a
class side message.
FormCanvas initializeTranslucentPatterns
No need to create instances (which may be hard to construct in some cases).
Would you mind moving it to the class side?
Thx
T.
> I found the bug! it is that FormCanvas>>translucentMaskFor: alphaValue
> depth: d, should use the accessor !
>
> Maybe when my settings our initialised the
> FormCanvas>>translucentPatterns get evaluated...
>
> I'll open an ISSUE and submit the code ASAP.
>
>
>
>
> On Thu, Sep 12, 2013 at 1:12 PM, Fernando Olivero
> <[email protected]> wrote:
> > Hi,this is strange, because everything works just fine for me.
> >
> > I'm using Pharo3.0: Latest update: #30391
> >
> > That's ok, the class var is lazy initialized. See
> > FormCanvas>>translucentPatterns.
> >
> > I don't understand which missing method are you referring to, because
> > FormCanvas class>>initializeTranslucentPatterns is there.
> >
> > Are you using #30391 ?
> >
> > Fernando
> >
> >
> > On Thu, Sep 12, 2013 at 1:05 PM, Marcus Denker <[email protected]>
> > wrote:
> >>
> >> On Sep 12, 2013, at 12:59 PM, Torsten Bergmann <[email protected]> wrote:
> >>
> >>> Marcus wrote:
> >>>> This should be fixed in 3.0 390…. at least I can't reproduce it anymore.
> >>>
> >>> Hi Marcus,
> >>>
> >>> No its not. I tried in the latest 3.0 image from today. To make sure I
> >>> cleanly downloaded a fresh
> >>> Pharo3.0 Latest update: #30391 and still can reproduce the problem.
> >>> One has to do some moving on the Workspace.
> >>>
> >>> If you look you will into an updated image you will also see that still
> >>> class var
> >>> "TranslucentPatterns" in FormCanvas is uninitialized and class side
> >>> methods on FormCanvas for
> >>> initialization are missing. So the problem still persists ...
> >>
> >> This is strange. now I can reproduce it, but when I tested it before I
> >> could not.
> >>
> >> Marcus
>
