[wx-dev] Blank wxMessageBox msg when using wxEntryStart in MSW from a dll

[John Labenski]

On 5/2/07, Vadim Zeitlin <vadim at wxwindows.org> wrote:
> On Tue, 1 May 2007 23:01:17 -0400 John Labenski <jlabenski at gmail.com> wrote:
>
> JL> In wxWidgets 2.8.3 (zip download) and 2.8 CVS branch the wxMessageBox
> JL> text is blank when using wxEntryStart to initialize wxWidgets from a
> JL> dll in both release and debug ANSI.
>
>  This is really strange, there is not much that could break in wxMessageBox.
>
> JL> This worked in wxWidgets 2.8.0 and the code on this end hasn't changed
> JL> at all. Any ideas what changed?
>
>  No :-(

I don't think it's a problem with a change in wxWidgets anymore. After
downloading the sources used to create a working version
(wxMSW-2.8.0.zip and wxLua-2.8.0.0.zip) and compiling myself I have
the same problem. IIRC the binary dlls for wxLua 2.8.0 that work
correctly were compiled with MSVC6, but by Francesco.

ps. I've installed SP5 for MSVC6, using Windows XP SP2 with all
updates, McAfee anti-virus... anything else?

> JL> Then (in wxLua)
> JL>
> JL> require("wx") -- this calls the above code
> JL> wx.wxMessageBox("I'm correctly displayed", "No message text shown")
> JL> frame = wx.wxFrame(wx.wxNull, -1, "Frame caption shown")
> JL> button = wx.wxButton(frame, wx.wxID_ANY, "Text is not displayed")
> JL> frame:Show(true)
> JL> wx.wxGetApp():MainLoop()
>
>  Can you debug this and check what's going on inside wxMessageBox, i.e.
> whether the correct strings are passed to ::MessageBox() function?

I forgot to mention that the text for the "Ok" button doesn't even
show up. In fact, if you cause an assert in debug mode the dialog for
the wxCHECK_MSG is blank. For example wx.wxWindow(wx.wxNull, -1)
asserts about an invalid parent and the wxCHECK_MSG dialog is shown
with a " wxWidgets Debug Alert" caption, the red X error icon, sized
correctly for the text, but other than that it is totally blank -
including the buttons.

I will try on another machine tomorrow night with basically the same
install, maybe that'll work and then try to debug... whatever is
wrong.

Thanks for any thoughts, I'm totally at a loss
     John Labenski