I have a wxpython app that I'm developing on a Windows NT 4 box. When
I've tried running the app on a Windows 98 computer I get these two
error dialogs:
c:\projects\wx\src\msw\settings.cpp(236): assert "wxFalse" failed:
failed to get LOGFONT
c:\projects\wx\src\msw\font.cpp(858): assert "wxFalse" failed: invalid
font
I have a wxpython app that I'm developing on a Windows NT 4 box. When
I've tried running the app on a Windows 98 computer I get these two
error dialogs:
c:\projects\wx\src\msw\settings.cpp(236): assert "wxFalse" failed:
failed to get LOGFONT
c:\projects\wx\src\msw\font.cpp(858): assert "wxFalse" failed: invalid
font
I wouldn't expect it to ever fail at that point. It is just trying to
initialize stock system fonts. Does the demo fail too?
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I discovered that this was caused by using the unicode enabled binary.
I did test the demo, and it Segfaulted with out those error messages.
The sample app wxProject worked as normal. I didn't explore more than
that.
Using the nonunicode binaries worked like a champ.
if there is any more info I can give, let me know
thanks Robin,
myers
···
On Tue, 2002-07-30 at 13:06, Robin Dunn wrote:
>
> I have a wxpython app that I'm developing on a Windows NT 4 box. When
> I've tried running the app on a Windows 98 computer I get these two
> error dialogs:
>
> c:\projects\wx\src\msw\settings.cpp(236): assert "wxFalse" failed:
> failed to get LOGFONT
>
> c:\projects\wx\src\msw\font.cpp(858): assert "wxFalse" failed: invalid
> font
I wouldn't expect it to ever fail at that point. It is just trying to
initialize stock system fonts. Does the demo fail too?
>
> I wouldn't expect it to ever fail at that point. It is just trying to
> initialize stock system fonts. Does the demo fail too?
I discovered that this was caused by using the unicode enabled binary.
I did test the demo, and it Segfaulted with out those error messages.
The sample app wxProject worked as normal. I didn't explore more than
that.
Using the nonunicode binaries worked like a champ.
Yeah, the unicode support is still flakey on Win9x/Me, mainly because the
MSLU library is not as rock-solid as MS would lead you to believe. The
uniocde version of the wxPython demo is crashing because of the
wxTaskbarIcon. If you take it out of the demo then most things will work,
although it is still difficult to navigate because the EVT_TREE_SEL_CHANGED
event seems to get lost...
For now, I can not reccommend that the Unicode version of wxPython be used
on Win9x/ME, but it works perfectly well on NT/2000 and I assume on XP as
well.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!