wxlua-users Mailing List for wxLua

Daniel Aquino wrote:
> but I was referring to , "web browser alert style boxes" vs "a log
> window".  If the log window is closed it should not produce, "web
> browser alert style boxes"

Setting the last parameter of wx.wxLogWindow() to false seems to solve
the problem:

local log = wx.wxLogWindow( frame, "Log", true, false )
wx.wxLog.SetVerbose(true)

After that, any call to wx.wxLogVerbose() will produce output in the log
window. If it's closed, nothing happens.

The last option is "passToOld":
(see http://docs.wxwidgets.org/stable/wx_wxlogwindow.html)

Setting it to false means every log message is processed by the log
window only. Therefore the default handler which shows a message box for
wx.wxLogVerbose is ignored.

On Mon, Aug 24, 2009 at 11:57 AM, Tyson Roberts<wx...@ca...> wrote:
> Hello, thanks for the feedback.  I discovered something as part of going
> through the example, notably that I was forgetting to setup the viewport in
> GL before trying to display.  I took the following lines from the cube demo
> and tried to use them:
>
> const wxSize ClientSize = GetClientSize();
> glViewport(0, 0, ClientSize.x, ClientSize.y);
>
> However, when implementing these in wxLua, I found that ClientSize ends up
> being (0, 0)!  I'm not sure what to make of this - it seems like the canvas
> is creating itself with a zero width/height.  But is this a direct problem,
> or a symptom of something else awry?  Any suggestions?

http://wxlua.sourceforge.net/docs/wxluaref.html#wxGLCanvas

The wxGLCanvas constructor takes a wxSize as an input. You probably
have to specify it, though if it is the first and only child of the
wxFrame it should take the client size of the frame and you should use
wxDefaultSize. However, sometimes you need to call
wxFrame::SendSizeEvent() before wxFrame::Show() to have it correctly
lay itself out. Either that or slightly resize the frame by hand while
printing wxGLCanvas::GetSize() in your wxEVT_PAINT handler to test
what the size is.

Hope this helps,
     John

Hello, thanks for the feedback.  I discovered something as part of going
through the example, notably that I was forgetting to setup the viewport in
GL before trying to display.  I took the following lines from the cube demo
and tried to use them:

const wxSize ClientSize = GetClientSize();
glViewport(0, 0, ClientSize.x, ClientSize.y);

However, when implementing these in wxLua, I found that ClientSize ends up
being (0, 0)!  I'm not sure what to make of this - it seems like the canvas
is creating itself with a zero width/height.  But is this a direct problem,
or a symptom of something else awry?  Any suggestions?

I'm going to attempt to implement the cube demo in straight c++ inside my
current program's environment next to ensure that it works.

Cheers,

- Tyson

On Tue, Aug 25, 2009 at 12:13 AM, John Labenski <jla...@gm...> wrote:

> On Sat, Aug 22, 2009 at 11:22 AM, Tyson Roberts<wx...@ca...> wrote:
> >
>
> > I'm using wxLua on OSX10.5 and attempting to get a "Hello world" type
> > program working on wxGLCanvas().
> >
> > Basic problem:
> >     - Have my own custom wxWindows program, running as an OSX app.  Using
> a
> > wxLua interpreter.
> >     - Used the wxLua binding system to create rudimentary OpenGL bindings
> > (I've tried other pre-made GL bindings, but those approaches but got
> crashes
> > when dynamic libraries were being loaded that I couldn't track down).
> >     - Linked against the stock OSX OpenGL.framework.
> >     - Created a window in lua, added a wxGLContext.
> >
> > Result:
> >     - It shows up grey, no rendering.
> >
>
> I have never tried to use OpenGL with wxWidgets.
>
> You can look at the wxWidgets C++ samples to see if they do any
> special initialization of the GL canvas.
>
> http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/samples/opengl/
>
> The cube.h/cpp looks simple enough, they create a TestGLCanvas which
> is a wxGLCanvas, but notice that they use a TestGLCanvas::OnPaint()
> connected to a wxEVT_PAINT to do the drawing. Also note
> MyApp::GetContext() which is odd to me, but I think it simplifies to
>
> wxGLContext.SetCurrent(wxGLCanvas)
>
> I hope this helps,
>    John
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Well the thing is if the wxLogWindow is closed then the default
behavior will produce those alert dialogs...

I really don't want that...

I have a small function which I use for that purpose.

On Mon, Aug 24, 2009 at 11:26 AM, John Labenski<jla...@gm...> wrote:
> On Mon, Aug 24, 2009 at 11:12 AM, Daniel
> Aquino<mr....@gm...> wrote:
>> hm ok I'll look into that...
>>
>> but I was referring to , "web browser alert style boxes" vs "a log
>> window".  If the log window is closed it should not produce, "web
>> browser alert style boxes"
>>
>
> You mean a wxMessageDialog?  A dialog with optional Ok/Cancel/Yes/No buttons.
>
> http://docs.wxwidgets.org/stable/wx_wxmessagedialog.html#wxmessagedialog
>
> You could create a little function to centralize your logging that
> creates a wxMessageDialog with all the appropriate flags and takes
> your message string as a parameter.
>
> Hope this helps,
>    John
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

On Mon, Aug 24, 2009 at 11:26 AM, John Labenski<jla...@gm...> wrote:
> On Mon, Aug 24, 2009 at 11:12 AM, Daniel
> Aquino<mr....@gm...> wrote:
>> hm ok I'll look into that...
>>
>> but I was referring to , "web browser alert style boxes" vs "a log
>> window".  If the log window is closed it should not produce, "web
>> browser alert style boxes"
>>
>
> You mean a wxMessageDialog?  A dialog with optional Ok/Cancel/Yes/No buttons.
>
> http://docs.wxwidgets.org/stable/wx_wxmessagedialog.html#wxmessagedialog

See also

http://docs.wxwidgets.org/stable/wx_dialogfunctions.html#wxmessagebox

>
> You could create a little function to centralize your logging that
> creates a wxMessageDialog with all the appropriate flags and takes
> your message string as a parameter.
>
> Hope this helps,
>    John
>

On Mon, Aug 24, 2009 at 11:12 AM, Daniel
Aquino<mr....@gm...> wrote:
> hm ok I'll look into that...
>
> but I was referring to , "web browser alert style boxes" vs "a log
> window".  If the log window is closed it should not produce, "web
> browser alert style boxes"
>

You mean a wxMessageDialog?  A dialog with optional Ok/Cancel/Yes/No buttons.

http://docs.wxwidgets.org/stable/wx_wxmessagedialog.html#wxmessagedialog

You could create a little function to centralize your logging that
creates a wxMessageDialog with all the appropriate flags and takes
your message string as a parameter.

Hope this helps,
    John

On Sat, Aug 22, 2009 at 11:22 AM, Tyson Roberts<wx...@ca...> wrote:
>

> I'm using wxLua on OSX10.5 and attempting to get a "Hello world" type
> program working on wxGLCanvas().
>
> Basic problem:
>     - Have my own custom wxWindows program, running as an OSX app.  Using a
> wxLua interpreter.
>     - Used the wxLua binding system to create rudimentary OpenGL bindings
> (I've tried other pre-made GL bindings, but those approaches but got crashes
> when dynamic libraries were being loaded that I couldn't track down).
>     - Linked against the stock OSX OpenGL.framework.
>     - Created a window in lua, added a wxGLContext.
>
> Result:
>     - It shows up grey, no rendering.
>

I have never tried to use OpenGL with wxWidgets.

You can look at the wxWidgets C++ samples to see if they do any
special initialization of the GL canvas.

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/samples/opengl/

The cube.h/cpp looks simple enough, they create a TestGLCanvas which
is a wxGLCanvas, but notice that they use a TestGLCanvas::OnPaint()
connected to a wxEVT_PAINT to do the drawing. Also note
MyApp::GetContext() which is odd to me, but I think it simplifies to

wxGLContext.SetCurrent(wxGLCanvas)

I hope this helps,
    John

hm ok I'll look into that...

but I was referring to , "web browser alert style boxes" vs "a log
window".  If the log window is closed it should not produce, "web
browser alert style boxes"

On Mon, Aug 24, 2009 at 11:01 AM, John Labenski<jla...@gm...> wrote:
> On Sun, Aug 23, 2009 at 9:57 PM, Daniel Aquino<mr....@gm...> wrote:
>> If I do:
>>
>> wx.wxLog.SetVerbose(true)
>> wx.wxLogVerbose("blah")
>>
>> I still get a pop up window :[
>>
>> I only want the log window to be for informational purposes...
>
> I thought you wanted a popup window for your messages? I never look at
> the wxWidgets log messages, but if your problem is that you only want
> to display YOUR messages and are bothered by wxWidgets messages, I'm
> afraid that you will have to create your own wxFrame with a wxTextCtrl
> child window for logging. It should be pretty simple to implement and
> you will have full control and be able to show only your messages.
>
>> When it's closed or never created then it should never show pop up messages...
>>
>> Is this possible?
>
> Dunno.
>
>> Also when I create a wxLogWindow and then close the app it seems to crash!
>>
>> I have attached the dr watson log if that is of any help.
>
> I can't seem to figure out who is supposed to delete wxLogs, but from
> what I can tell so far, wxWidgets will do it for you. I'm afraid that
> I have to fix wxLua to not delete them in the next version.
>
> I'm away on travel for business right now... I will have time to work
> on this next week.
>
> I really suggest using your own wxFrame + wxTextCtrl. I think you will
> be much happier since you'll be able to control everything and it's
> trivial to implement.
>
> Regards,
>    John
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

On Sun, Aug 23, 2009 at 9:57 PM, Daniel Aquino<mr....@gm...> wrote:
> If I do:
>
> wx.wxLog.SetVerbose(true)
> wx.wxLogVerbose("blah")
>
> I still get a pop up window :[
>
> I only want the log window to be for informational purposes...

I thought you wanted a popup window for your messages? I never look at
the wxWidgets log messages, but if your problem is that you only want
to display YOUR messages and are bothered by wxWidgets messages, I'm
afraid that you will have to create your own wxFrame with a wxTextCtrl
child window for logging. It should be pretty simple to implement and
you will have full control and be able to show only your messages.

> When it's closed or never created then it should never show pop up messages...
>
> Is this possible?

Dunno.

> Also when I create a wxLogWindow and then close the app it seems to crash!
>
> I have attached the dr watson log if that is of any help.

I can't seem to figure out who is supposed to delete wxLogs, but from
what I can tell so far, wxWidgets will do it for you. I'm afraid that
I have to fix wxLua to not delete them in the next version.

I'm away on travel for business right now... I will have time to work
on this next week.

I really suggest using your own wxFrame + wxTextCtrl. I think you will
be much happier since you'll be able to control everything and it's
trivial to implement.

Regards,
    John

If I do:

wx.wxLog.SetVerbose(true)
wx.wxLogVerbose("blah")

I still get a pop up window :[

I only want the log window to be for informational purposes...

When it's closed or never created then it should never show pop up messages...

Is this possible?

Also when I create a wxLogWindow and then close the app it seems to crash!

I have attached the dr watson log if that is of any help.



On Sun, Aug 23, 2009 at 5:44 PM, Andreas Krinke<and...@gm...> wrote:
> wx.wxLog.SetVerbose(true)