On Wednesday 10 February 2010 02:59:14 pm Ed Leafe wrote:
> On Feb 10, 2010, at 5:48 PM, Larry wrote:
> > RE: Your question as to why we are using the wx.Clear: If I recall
> > correctly, we had to use the clear before a re-assigned set of values
> > for the list would show, otherwise the old list would show.
>
> That would be a MAJOR bug. Can you try removing the wx Clear() call and
> seeing if this is still the case? Also, if removing the Clear() call does
> cause a problem, can you try with the Dabo clear() call instead? I'm very
> curious why your lists are not behaving, and why the Dabo-level
> self.removeAll() didn't work, since it calls the wx-level method.
>
>
> -- Ed Leafe
Ok I've run several experiments with respect to the Clear().
1. Removing the self.Clear():
When I attempt to close the form Dabo displays the save dialog.
2. Changing to self.clear():
When I attempt to close the form Dabo displays the save dialog.
3. Using self.Clear():
Dabo does NOT display the save dialog.
Our showchanges() method (provides the table and field name not matching
mementos) reveals that the field in question is the one associated with the
dropdown.
I believe this is the same experience we had in the past. I don't even have a
guess as why this is required.
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
