Freeze() and Thaw()

Hi Bob,

I tried self.Hide() instead of self.Freeze(). No change.
Then I eliminated the hide and freeze. No change.

Soooo, there must be something else besides an explicit object.Show()
that can cause the display to occur despite the presence of
object.Freeze() or object.Hide().

I'm all ears.

Having Freeze() and Thaw() inside an __init__ method shouldn't make
any difference, as Chris mentioned, because the main frame is not
shown during the __init__ . If it's not shown, Freeze() and Thaw()
have no effect as far as I know (but I may be wrong). Now, it looks
*very* strange to me that you can actually see the layout creation and
adjustments during __init__ . It never happened to me, even with very
complex interfaces.
However, I work only on Windows... which platform are you on? Is there
a way you could reproduce it somehow in a sample?

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/

···

On 10/5/07, Bob Klahn wrote:

Andrea, I too work only on Windows. Windows XP SP2. Using wxPython 2.8.4 with Python 2.5.1.

I have been unable to reproduce this behavior in a sample.

I don't know what else to try at this point, but I'll keep thinking.

Bob

···

At 09:59 AM 10/5/2007, Andrea Gavana wrote:

Hi Bob,

On 10/5/07, Bob Klahn wrote:
> I tried self.Hide() instead of self.Freeze(). No change.
> Then I eliminated the hide and freeze. No change.
>
> Soooo, there must be something else besides an explicit object.Show()
> that can cause the display to occur despite the presence of
> object.Freeze() or object.Hide().
>
> I'm all ears.

Having Freeze() and Thaw() inside an __init__ method shouldn't make
any difference, as Chris mentioned, because the main frame is not
shown during the __init__ . If it's not shown, Freeze() and Thaw()
have no effect as far as I know (but I may be wrong). Now, it looks
*very* strange to me that you can actually see the layout creation and
adjustments during __init__ . It never happened to me, even with very
complex interfaces.
However, I work only on Windows... which platform are you on? Is there
a way you could reproduce it somehow in a sample?

Hi Bob:

I have no idea what your problem is, but whenever I get into a situation
like this, I start stripping out chunks of the misbehaving app, until either
the problem goes away, or I have a small sample that shows it. If the
problem does go away at some point, then I know it results from the
latest chunk I removed, and can probe more finely from there. Good luck.

···

On 10/5/07, Bob Klahn <bobstones@comcast.net> wrote:

Andrea, I too work only on Windows. Windows XP SP2. Using wxPython
2.8.4 with Python 2.5.1.

I have been unable to reproduce this behavior in a sample.

I don't know what else to try at this point, but I'll keep thinking.

Bob