|
From: Daan L. <daa...@xs...> - 2004-06-25 09:40:14
|
> I still notice one quirk - when I run a program, the window seems to appear briefly at a larger size, then quickly resizes to a smaller size. This produces an annoying "flash".
Yes, this is known "bug". It occurs because the initial window size is zero.
Then, you set the size using the "clientSize" attribute and the window is
resized to a proper size. There are two ways to solve this.
1) I added "creation" attributes: that are attributes that are treated specially
when given in the initial property list. This way, the window can immediately
be created with the correct size. The downside of "creation" attributes is that
it creates a distinction between:
w <- widget [...]
and
w <- widget []
set w [...]
2) I let the start function take an IO action that returns a "Frame", and
I keep frames hidden by default -- ie. you need to show them explicitly.
This way, the showing of a frame can be delayed until all size and layout constraints
are known.
Both solutions are not too nice however -- but I think I will implement solution
(1) anyways despite its disadvantages. It seems terribly useful in general even
though it is also terribly against the spirit of Haskell :-)
Bottom line: next version (0.8) will fix this one way or the other.\
If anyone knows a better solution, please tell me, so we can prevent
the introduction of "creation" attributes in wxHaskell.
All the best,
Daan.
>
> Does anyone know why this occurs, and how it can be avoided?
>
> Thanks,
> Lyle
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>
|