wxlua-users Mailing List for wxLua

Hi John,

John Labenski ha scritto:
>> 2. Are there any plans to support wxWidget 3.0?
> 
> Yes, but the binding generator should be completely rewritten to take
> advantage of the interface files that they use to generate the docs.
Just in case it's useful: I already wrote a set of (simple) C++ classes to parse 
the XML produced by doxygen when it's run over wxWidgets interface files.
The code is in wx SVN: wxWidgets/utils/ifacecheck/src/xmlparser.*

I think the classes "wxMethod, wxClass, wxXmlDoxygenInterface" (which basically 
represent the wxWidgets/interface/wx/*.h contents as an in-memory tree) should 
contain everything you need to generate wxLua bindings...
obviously those helps in case you want to use C++... AFAIK Kevin Ollivier wrote 
some python scripts for parsing the doxygen XML, too...

Just my 2 cents,
Keep up the good work!
Francesco

Thanks for answer.

> because Lua only uses ASCII C strings

Lua may store within string any binary data including zeros in between.

> and the strings will be converted as they're 
> passed between Lua and wxWidgets

Strings will be converted from current codepage to Unicode?
In this case it is not really make sense - still have only-one-codepage
limitation.

LuaCom module uses another approach - it converts all strings from UTF-8
to Windows wide-char and back on the fly.

>From http://docs.wxwidgets.org/trunk/overview_unicode.html
>> Since wxWidgets 3.0 Unicode support is always enabled

wxWidget 3.0 gives to developer a full freedom to use any encoding:
- codepage (when passing char*)
- wide char (when passing wchar_t*)
- UTF-8 (when using FromUTF8(char*) )

What are you planning for this part?
I would advocate UTF-8 string encoding for Lua binding.
Disadvantages:
- Yes, it will have some performance penalty on Windows, but I don't see
how to use wide chars from Lua anyway.
Advantages:
- Sources will be portable
- Support ANY national characters
- No performance penalty on Linux - UTF-8 is internal string
representation

Regards
Alexander Altshuler



-----Original Message-----
From: John Labenski [mailto:jla...@gm...] 
Sent: Tuesday, August 25, 2009 4:25 PM
To: wxl...@li...
Subject: Re: [wxlua-users] wxWidget 3.0 etc

On Tue, Aug 25, 2009 at 5:36 AM, Alexander Altshuler<al...@ka...>
wrote:
>
> I have two questions both related Unicode support in wxLua:
>
> 1. Are current Windows binaries compiled with Unicode support?

No, because Lua only uses ASCII C strings, but you can build it with
wxWidgets unicode support and the strings will be converted as they're
passed between Lua and wxWidgets. I'm not sure that you get any
advantage by building wxWidgets in unicode mode, but you do get a
performance penalty doing the translation.

> 2. Are there any plans to support wxWidget 3.0?

Yes, but the binding generator should be completely rewritten to take
advantage of the interface files that they use to generate the docs.
This will make it easier to follow changes in wxWidgets in the future.
I have to immediate plans to do this, but it will be done.

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/interface/wx/

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

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.409 / Virus Database: 270.13.65/2322 - Release Date:
08/24/09 12:55:00

But if it's not opened then it will ?

I have to test later when i get home...


On Tue, Aug 25, 2009 at 9:22 AM, Andreas Krinke<and...@gm...> wrote:
> Daniel Aquino wrote:
>> hm yea ok i guess that is fine...
>>
>> i was setting verbose true and then not opening the window which
>> caused a pop up...
>>
>> i guess if i close the window then it should be set back to false...
>
> No, that's not nescessary. Once a log window was created with the last
> argument set to false, it doesn't matter whether it has been closed or
> not. wxLogDebug will never create a message box.
>
> ------------------------------------------------------------------------------
> 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
>

Daniel Aquino wrote:
> hm yea ok i guess that is fine...
> 
> i was setting verbose true and then not opening the window which
> caused a pop up...
> 
> i guess if i close the window then it should be set back to false...

No, that's not nescessary. Once a log window was created with the last
argument set to false, it doesn't matter whether it has been closed or
not. wxLogDebug will never create a message box.

hm yea ok i guess that is fine...

i was setting verbose true and then not opening the window which
caused a pop up...

i guess if i close the window then it should be set back to false...

thanks...

On Tue, Aug 25, 2009 at 8:57 AM, Andreas Krinke<and...@gm...> wrote:
> Daniel Aquino wrote:
>> yea but that means you have to create the window.
>>
>> I guess at that point you could write a small wrapper function that
>> would only call wxLogVerbose if the window has been opened...
>>
>> But I was going for the simple approach of having wxLogVerbose lines
>> in my app which only took affect if the window was open...
>>
>> This would seem clean and the way I would have designed it.
>
> I think, I don't understand what you're trying to archive.
>
> If you want to have the log window you do:
>
> local log = wx.wxLogWindow( frame, "Log", true, false )
> wx.wxLog.SetVerbose(true)
>
> If you don't want the log window, you don't do this.
>
> This way, you can have calls to wx.wxLogVerbose everywhere in your program.
>
> ------------------------------------------------------------------------------
> 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
>

Daniel Aquino wrote:
> yea but that means you have to create the window.
> 
> I guess at that point you could write a small wrapper function that
> would only call wxLogVerbose if the window has been opened...
> 
> But I was going for the simple approach of having wxLogVerbose lines
> in my app which only took affect if the window was open...
> 
> This would seem clean and the way I would have designed it.

I think, I don't understand what you're trying to archive.

If you want to have the log window you do:

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

If you don't want the log window, you don't do this.

This way, you can have calls to wx.wxLogVerbose everywhere in your program.

On Tue, Aug 25, 2009 at 5:36 AM, Alexander Altshuler<al...@ka...> wrote:
>
> I have two questions both related Unicode support in wxLua:
>
> 1. Are current Windows binaries compiled with Unicode support?

No, because Lua only uses ASCII C strings, but you can build it with
wxWidgets unicode support and the strings will be converted as they're
passed between Lua and wxWidgets. I'm not sure that you get any
advantage by building wxWidgets in unicode mode, but you do get a
performance penalty doing the translation.

> 2. Are there any plans to support wxWidget 3.0?

Yes, but the binding generator should be completely rewritten to take
advantage of the interface files that they use to generate the docs.
This will make it easier to follow changes in wxWidgets in the future.
I have to immediate plans to do this, but it will be done.

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/interface/wx/

Regards,
    John

On Tue, Aug 25, 2009 at 7:52 AM, Klaas Holwerda<db...@nl...> wrote:
> Hi John,
>
> Would it be possible to change the hook_cpp_binding_includes to a bit higher
> in the generated binding? Or maybe add an extra variable??

I don't see why we couldn't move hook_cpp_binding_includes earlier
since we already have hook_cpp_binding_post_includes. You can do this
locally for now, I will change that when I get back home in a week.

Regards,
    John

Hi John,

Would it be possible to change the hook_cpp_binding_includes to a bit higher in 
the generated binding? Or maybe add an extra variable??

         table.insert(fileData, "#include \"wx/wxprec.h\"\n")
         table.insert(fileData, "\n")
         table.insert(fileData, "#ifndef WX_PRECOMP\n")
         table.insert(fileData, "     #include \"wx/wx.h\"\n")
         table.insert(fileData, "#endif\n")
         table.insert(fileData, "\n")
         table.insert(fileData, hook_cpp_binding_includes or "")
         table.insert(fileData, "\n")

to:

         table.insert(fileData, hook_cpp_binding_includes or "")
         table.insert(fileData, "\n")
         table.insert(fileData, "#include \"wx/wxprec.h\"\n")
         table.insert(fileData, "\n")
         table.insert(fileData, "#ifndef WX_PRECOMP\n")
         table.insert(fileData, "     #include \"wx/wx.h\"\n")
         table.insert(fileData, "#endif\n")

I have to define settings in my art2dsetup.h, before wxsetup.h is included.
This is currently not possible.

Regrads,

Klaas

-- 
Unclassified


------------------------------------------------------------------------------------------------------------
Disclaimer:

If you are not the intended recipient of this email, please notify the sender and delete it. 
Any unauthorized copying, disclosure or distribution of this email or its attachment(s) is forbidden. 
Thales Nederland BV will not accept liability for any damage caused by this email or its attachment(s). 
Thales Nederland BV is seated in Hengelo and is registered at the Chamber of Commerce under number 06061578.
------------------------------------------------------------------------------------------------------------

Hi
 
I have two questions both related Unicode support in wxLua:
 
1. Are current Windows binaries compiled with Unicode support?
2. Are there any plans to support wxWidget 3.0?
 
Regards
Alexander Altshuler

Hmmm...
I've tried both explicitly sending the initial size in any of the following
ways:

1) widget.gl = wx.wxGLCanvas(widgets.test, wx.wxID_ANY,
wx.wxDefaultPosition, wx.wxSize(200, 200), wx.wxFULL_REPAINT_ON_RESIZE)
2) widget.gl = wx.wxGLCanvas(widgets.test, wx.wxID_ANY,
wx.wxDefaultPosition, wx.wxDefaultSize, 3) wx.wxFULL_REPAINT_ON_RESIZE)
3) widget.gl:SetClientSize(wx.wxSize(200, 200))

1 and 3 report the correct size with widget:GetClientSize(), while 2 reports
(0, 0).

How none of these have any visual effect - the widget remains invisible.

- Tyson

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

> 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
>
>
> ------------------------------------------------------------------------------
> 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
>

yea but that means you have to create the window.

I guess at that point you could write a small wrapper function that
would only call wxLogVerbose if the window has been opened...

But I was going for the simple approach of having wxLogVerbose lines
in my app which only took affect if the window was open...

This would seem clean and the way I would have designed it.

On Mon, Aug 24, 2009 at 7:44 PM, Andreas Krinke<and...@gm...> wrote:
> 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.
>
> ------------------------------------------------------------------------------
> 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
>

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)

Daniel Aquino wrote:
> But nothing shows up in the log window and i don't know how to enable
> verbose logging.

Try this:

wx.wxLog.SetVerbose(true)

-- Andreas

	local log = wx.wxLogWindow( frame, "Log", true, true )
	wx.wxLogError("testing...")
	--wx.wxLogWarning("")
	--wx.wxLogMessage("")
	--wx.wxLogStatus("")
	--wx.wxLogDebug("")
	--wx.wxLogVerbose("blah")

That's basically all I have right now.

If you don't have the log window open it will generate a pop up window.

The only one that doesn't is wxLogVerbose.

But nothing shows up in the log window and i don't know how to enable
verbose logging.

On Sat, Aug 22, 2009 at 10:13 AM, Daniel
Aquino<mr....@gm...> wrote:
> Well I really just want a log window that only shows messages if it's open.
>
> I do not want the messages to show up as alert boxes when the log
> window is closed.
>
> I believe I need to enable verbose logging but can't seem to figure out how.
>
> I don't have access to my code right now, when I do I will send it...
>
>
> On Sat, Aug 22, 2009 at 8:00 AM, John Labenski<jla...@gm...> wrote:
>> On Fri, Aug 14, 2009 at 9:29 PM, Daniel Aquino<mr....@gm...> wrote:
>>> wxLogMessage appears to not send an alert window when the log window
>>> is open but it does when it's closed...
>>>
>>> Really I'm just looking for a debug method to send to the log window
>>> and not interfere with the other log messages..
>>>
>>> log = log window
>>> log:SetVerbose(true) seems to crash
>>>
>>> I tried log:SetLogLevel(wx.wxLOG_Max) crash as well
>>>
>>> and various other attempts...
>>
>> Sorry about the delay, I have not tried the wxLog functions with
>> wxLua, but they should work... Can you give an example of the code
>> that you are using, maybe modify the minimal sample and I can try to
>> debug it.
>>
>> Regards,
>>    John
>>
>>
>>> On Fri, Aug 14, 2009 at 9:15 PM, Daniel Aquino<mr....@gm...> wrote:
>>>> I seem to see messages when I do LogError but not LogVerbose
>>>>
>>>> On Fri, Aug 14, 2009 at 9:12 PM, Daniel Aquino<mr....@gm...> wrote:
>>>>> The application also appears to crash which must mean I need to clean
>>>>> up the log window some how on close...
>>>>>
>>>>> On Fri, Aug 14, 2009 at 9:09 PM, Daniel Aquino<mr....@gm...> wrote:
>>>>>> I created a wxLogWindow successfully and attached it to my current window.
>>>>>>
>>>>>> I called wxLogVerbose but don't seem to see any output.
>>>>>>
>>>>>> The error functions work fine (showing a pop up window).
>>>>>>
>>>>>> I noticed I had to bind wxLogWindow to a particular frame but then
>>>>>> when I call the log functions I doesn't need a window ref... Could
>>>>>> this be the issue?
>>>>>>
>>>>>> I also tried to set wxUSE_LOGWINDOW=true to no avail...
>>>>>>
>>>>>> Any help much appreciated...
>>>>>>
>>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>

Hello guys, I'm sorry if this has been asked before, but I'm having a heck
of a time, probably putting 16 hours of trying on this, and Google and the
archive have been no help so far.

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.

Any help is appreciated.  I can provide any further information that might
be needed.

Lua Code:
--------------------------------------------------------------------------------------------------------------

package.cpath = package.cpath ..
";./?.dll;./?.so;../lib/?.so;../lib/vc_dll/?.dll;../lib/bcc_dll/?.dll;../lib/mingw_dll/?.dll;./lua/?.so;"
package.path  = package.path .. ";./lua/?.lua;./lua/LuaCommon/?.lua;"

require 'wx'
require 'lpc'

require 'Utility'

require 'consoleTextCtrl_wx'

widgets    = { }
timers     = { }

function UpdateGL()
    Log("Test Timer!\n")

    local win = widgets.gl

    win:GetContext():SetCurrent()

    gl.glLoadIdentity()
    gl.glTranslatef(-1.5,0.0,-6.0)
    gl.glBegin(GL_TRIANGLES)
        gl.glVertex3f( 0.0, 1.0, 0.0)
        gl.glVertex3f(-1.0,-1.0, 0.0)
        gl.glVertex3f( 1.0,-1.0, 0.0)
    gl.glEnd()

    gl.glTranslatef(3.0,0.0,0.0)
    gl.glBegin(GL_QUADS)
        gl.glVertex3f(-1.0, 1.0, 0.0)
        gl.glVertex3f( 1.0, 1.0, 0.0)
        gl.glVertex3f( 1.0,-1.0, 0.0)
        gl.glVertex3f(-1.0,-1.0, 0.0)
    gl.glEnd()

    win:SwapBuffers()
end

function CreateMainWindow()
    widgets.test = wx.wxFrame(wx.NULL, wx.wxID_ANY, "Test")
    widgets.test:SetSize(wx.wxRect(860, 200, 480, 360))
    widgets.test:Show(true)

    widgets.gl = wx.wxGLCanvas(widgets.test, -1)
    timers.gl  = wx.wxTimer(widgets.gl)

    widgets.gl:Connect(wx.wxEVT_TIMER, UpdateGL)
    timers.gl:Start(500)

    widgets.gl:SetCurrent()
    widgets.gl:SetFocus(true)
    widgets.gl:Show(true)

    gl.glShadeModel(gl.GL_SMOOTH)
    gl.glClearColor(1.0, 0.0, 0.0, 0.5)
    gl.glClearDepth(1.0)
    gl.glEnable(gl.GL_DEPTH_TEST)
    gl.glDepthFunc(gl.GL_LEQUAL)
    gl.glHint(gl.GL_PERSPECTIVE_CORRECTION_HINT, gl.GL_NICEST)
end

----------------------------------------------------------------------------------------------------
-- Get this party started!
-------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------

CreateMainWindow()

wx.wxGetApp():MainLoop()