On 07/01/2014 09:32 PM, Paul McNett wrote:
On 7/1/14, 9:03 AM, Werner wrote:
Hi John,
On 7/1/2014 16:39, John Fabiani wrote:
On 07/01/2014 07:27 AM, Werner wrote:
...
wx._core.wxAssertionError: C++ assertion "m_created" failed at
..\..\src\generic\grid.cpp(2311) in wxGrid::SetSelectionMode():
Called wxGrid::SetSelectionMode() before calling CreateGrid()
I think/guess that dPemMixin._constructed at some point returns True
if so CreateGrid or SetTable is not yet called on the grid.
If my guess is correct any suggestion on how that could be fixed in
Dabo?
Werner
I have seen the same error for a very long time while running any Dabo
code from within my editor (Wing). I ignored the message from within
Wing and the code just worked. So I'm wondering if the exception is
causing the program to actually stop. Or is this error coming from
your editor?
Using WingIDE too, so it looks like it is the configuration of catching
assert errors in Wing.
Will ignore it for the moment but there should be a way of fixing the
code so that the assert doesn't fire, no?
Hmm, a Wing problem. The root cause could be rooted in some of the way
we abstract things, and/or the way we do multiple-inheritance. I don't
have any suggestions for getting code that otherwise works running
inside of Wing.
Paul
Thanks for thinking about it. But I have seen other similar issues that
appear on the Linux side but not on the windows side (almost never test
under Mac). For example on the Linux side my code gets into a loop in a
'notifiy' method in the core. Never happens on windows. There is a
suggestion that it due to the timing loop in Dabo (came from the
wxPython guys). The calendar sometimes does not popup in the correct
size and location - but only on my Linux side. There are small graphic
artifacts that appear in the upper left hand corner than do not
disappear. But again only on Linux. These things occur within Wing and
outside of Wing. BTW the grid exception does not just occur in Wing's
debug mode but also in other editors (that is not a just a Linux issue).
Except for the timing issue (unconfirmed) none of the above appears to
be a result of Dabo code. When I debug I always get to the core - and I
stop. To further complicate the issue I only see these problems as the
code grows. IOW I never see the problem in small code examples. This
sounds like a rant but it's not my intent. I just want to point out the
issues going forward.
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
