Re: dwgui now passes test_shake.py

Robin Becker wrote:
> OK I checked in some changes to
> 
> test/test_shake.py
> lib/anygui/backends/mswgui.py
> lib/anygui/backends/dwgui.py
> 
> The mswgui passes the shake test.
> 
> 
> I have a question related to the order in which things get done.
> 
> In a test I have a widget created
> 
> F = widget()
> 
> then later I do
> 
> F.height = 333
> 
> but since I have not yet done app.run() F doesn't have a widget so I
> have to reject the attempt at setting the height. Later when app.run()
> is done I see the final completion of F (with the wrong default
> geometry).  
> 
> How are backends supposed to handle this kind of deferred property
> setting?

It should be handled by push/pull magic, unless that's been
changed. If the front end pushes a geometry to the backend
before the native widget exists, the backend should just
ignore it. The frontend proxy still has the proper values
in its state, so when the widget is created the wrapper
does "self.proxy.push()" to push everything, and the widget
gets the right geometry.

That worked on mswgui last time I looked.

Cheers,

-- Joe




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en