wxlua-users Mailing List for wxLua

Change all the call to LuaPCall to setup the result only when the code succeed
ex:
        m_wxlState.LuaPCall(1, 1);
to
	if (m_wxlState.LuaPCall(1, 1) == 0)
the are a number of those lines

This cause the program to crash particularly if the console is active.

Thank you

Andre

Hi all!

Is that possible to load the wxlua modules one-by-one, so load just that
what I really need? Because memory usage is quite high: after startup it's
12-13 Mb...

Regards: Attila

Please change all 
                m_wxlState.LuaPCall(.*)
to 
		if (m_wxlState.LuaPCall(.*) == 0)

checking for the status is necessary when a console is active. At other times 
we probably just lucked out.

If the console is active and Error is invoked within the callback then the 
program crash.

Thank you

Andre

PS: The default value seems to be righ.

If you do not use the TypeSeparator in completion then add the following line 
of code to your editor initialization.

    editor:AutoCompSetTypeSeparator(0)

this will set the separator to null which is not likely to be a valid 
character in your string.

If you do not do that and you have a ? in your completion string then you will 
simply crash in UserListShow.

Andre

PS: As you probably already know I found this the hard way.

On Tue, Nov 25, 2008 at 12:19 PM, arpin <ar...@ki...> wrote:
> arpin <arpin@...> writes:
>
>>
>> If one code the following function
>>
>>     --wxString BugsGridTable::GetRowLabelValue( int col )
>>     gridtable.GetRowLabelValue = function( self, row )
>>         error("unexpected row");
>>         return "x"..row;
>>     end
>>
> This occurs when you are in the debugger it does not happen if just run the
> program. I got so used to have the debugger behave that I ignore this
> important aspect of the problem.

It is interesting that it only happens in the debugger. In the past
I've only had problems that for some reason won't occur in the
debugger and those are particularly difficult to diagnose.

Lets just chalk it up to a bad interaction of the long jump with the
debugger. However, I do appreciate the reports of things not working
as expected.

Regards,
    John

arpin <arpin@...> writes:

> 
> If one code the following function
> 
>     --wxString BugsGridTable::GetRowLabelValue( int col )
>     gridtable.GetRowLabelValue = function( self, row )
>         error("unexpected row");
>         return "x"..row;
>     end
> 
This occurs when you are in the debugger it does not happen if just run the 
program. I got so used to have the debugger behave that I ignore this 
important aspect of the problem.

Sorry 

Andre

On Tue, Nov 25, 2008 at 8:36 AM, arpin <ar...@ki...> wrote:
> If one code the following function
>
>    --wxString BugsGridTable::GetRowLabelValue( int col )
>    gridtable.GetRowLabelValue = function( self, row )
>        error("unexpected row");
>        return "x"..row;
>    end
>
> then the program crash instead of reporting the error

This is the same problem as your last report. You're in a virtual C++
function handing the call to your Lua function and apparently the long
jump out of the C++ function corrupts the stack (I assume).

I will try to debug this, but I don't have very high hopes since I
imagine that I would have to override the error() function, save the
values, set a flag, and then call it later when it is safe, but I'd
still have to return "something" from the C++ function just to get out
of it...

I'd use a print statement and handle the error as gracefully as
possible so the program can continue.

Regards,
    John

On Tue, Nov 25, 2008 at 8:04 AM, arpin <ar...@ki...> wrote:
> How to reproduce:
>
> change
>    gridtable.GetTypeName = function( self, row, col )
>        if col == Col_Id or col == Col_Priority then
>            return wx.wxGRID_VALUE_NUMBER
>
> to
>    gridtable.GetTypeName = function( self, row, col )
>        if col == Col_Id or col == Col_Priority then
>            return wx.wxEmptyString
>
> I realize that this is not a type but this is purely to demonstrate the
> problem I found it in a more complex situation.
>
> Returning '' will properly report the error it seems to be related to
> wx.wxEmptyString.
>
> Hope someone can figure out how to fix the problem

This is always going to be a problem I imagine. wxLua merely wraps
wxWidgets and doesn't rewrite it. Therefore, when you return nil, but
a string is expected, a lua_error is thrown (actually a long jump) and
the C++ stack is corrupted since we're in a virtual C++ function
handling your Lua function. A good fix for this would take a lot of
work and make updating to new versions of wxWidgets very painful since
they would have to be done by hand. You do get an error stating that a
string was expected right? The best I can say is take heed of the
error message and return a string!

Regards,
    John

On Tue, Nov 25, 2008 at 3:36 AM, Éjjeli Őrjárat <ejj...@gm...> wrote:
> Thanks for the fast reply, I have already checked wxTaskbarIcon, but there
> is just a PopupMenu(), which shown a menu, not a warning message. I couldn't
> find the wxPopupWindow in the reference manual, is that really implemented
> and exists, or just I was blind? (I am using 2.8.7.0 version)

You're right, I forgot to add wxPopupWindow. Try wxMiniFrame, which
might even be better since you'll get a close button too. I'd use a
wxTimer for the delay, but be sure to connect to the EVT_CLOSE_WINDOW
event so that if the user closes it you can ignore the timer event.

Regards,
    John

If one code the following function

    --wxString BugsGridTable::GetRowLabelValue( int col )
    gridtable.GetRowLabelValue = function( self, row )
        error("unexpected row");
        return "x"..row;
    end

then the program crash instead of reporting the error

Andre

How to reproduce:

change
    gridtable.GetTypeName = function( self, row, col )
        if col == Col_Id or col == Col_Priority then
            return wx.wxGRID_VALUE_NUMBER

to 
    gridtable.GetTypeName = function( self, row, col )
        if col == Col_Id or col == Col_Priority then
            return wx.wxEmptyString

I realize that this is not a type but this is purely to demonstrate the 
problem I found it in a more complex situation.

Returning '' will properly report the error it seems to be related to 
wx.wxEmptyString.

Hope someone can figure out how to fix the problem

Andre

Thanks for the fast reply, I have already checked wxTaskbarIcon, but there
is just a PopupMenu(), which shown a menu, not a warning message. I couldn't
find the wxPopupWindow in the reference manual, is that really implemented
and exists, or just I was blind? (I am using 2.8.7.0 version)
Greets: Attila

On Mon, Nov 24, 2008 at 11:23 AM, Raúl Huertas <rax...@ho...> wrote:
> Here is more info with lua builded for debug:
>
> (idb) file dist/Release/IntelSDK-Linux-x86/luaexample
...
> Program received signal SIGSEGV
> free () in /lib/tls/i686/cmov/libc-2.7.so
> (idb) bt
> #0  0xb7cdc4ac in free () in /lib/tls/i686/cmov/libc-2.7.so
> #1  0x08060ab2 in l_alloc (ud=0x8054d7f, ptr=0x0, osize=3077778016,
> nsize=28) at lauxlib.c:631
> #2  0x08054d7f in luaM_realloc_ (L=0x8243d38, block=0x80aa008,
> osize=134914056, nsize=134593111) at lmem.c:79
> #3  0x0805ba57 in luaH_free (L=0x0, t=0x8243d38) at ltable.c:376
> #4  0x080549be in luaC_freeall (L=0x0) at lgc.c:487
> #5  0x0805a6d4 in lua_close (L=0xb7db7ff4) at lstate.c:212
> #6  0x08049d5a in main () in
> /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample
>
> I will now compile wxlua for debug

Let me know the result of that. The above doesn't seem to show that
wxLua is misbehaving, but on the other hand Lua itself shouldn't have
problems like this nor should libc as you mention in your last post.

You can also try running $ldd luaexample and $ldd wx.so to make sure
that both your program and the wxLua lib are linked to the same Lua
lib.

By the way, on Linux you might as well always compile in debug mode,
unless you're going to distribute your program or actually  require
speed.

Regards,
    John

Here is more info with lua builded for debug:

(idb) file dist/Release/IntelSDK-Linux-x86/luaexample 
Reading symbols from /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample...done.
(idb) run
Starting program: /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample
Version de Lua: Lua 5.1.4
Se cargó el archivo
Lua: Hola Lua and C    lun 24 nov 2008 11:21:05 PET
Lua: Se terminó de ejecutar el script de lua
No hubieron errores interpretando el archivo'
Se cargó y ejecutó el archivo por completo
get field 'probandolua' 
push 1 y push 2 
Esta es la función de prueba Lua    nil    12312,56
No hubieron errores llamando la función 'probandolua'
Se va  a llamar a 'luaclose'
Program received signal SIGSEGV
free () in /lib/tls/i686/cmov/libc-2.7.so
(idb) bt
#0  0xb7cdc4ac in free () in /lib/tls/i686/cmov/libc-2.7.so
#1  0x08060ab2 in l_alloc (ud=0x8054d7f, ptr=0x0, osize=3077778016, nsize=28) at lauxlib.c:631
#2  0x08054d7f in luaM_realloc_ (L=0x8243d38, block=0x80aa008, osize=134914056, nsize=134593111) at lmem.c:79
#3  0x0805ba57 in luaH_free (L=0x0, t=0x8243d38) at ltable.c:376
#4  0x080549be in luaC_freeall (L=0x0) at lgc.c:487
#5  0x0805a6d4 in lua_close (L=0xb7db7ff4) at lstate.c:212
#6  0x08049d5a in main () in /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample


I will now compile wxlua for debug

Discover the new Windows Vista Learn more!
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

Hello!

Here is the debug output(Intel debugger), the skyblue code is my program output:

raulhuertas@raulhuertas-desktop:~/Documentos/Proyectos/LuaExample$ /opt/intel/idb/10.1.018/bin/idb dist/Release/IntelSDK-Linux-x86/luaexample 
Intel(R) Debugger for applications running on IA-32, Version 10.1-35 , Build 20080310
------------------ 
object file name: dist/Release/IntelSDK-Linux-x86/luaexample 
Reading symbols from /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample...done.
(idb) file dist/Release/IntelSDK-Linux-x86/luaexample
Reading symbols from /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample...done.
(idb) run
Starting program: /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample
Version de Lua: Lua 5.1.4
Se cargó el archivo
Lua: Hola Lua and C    lun 24 nov 2008 11:04:02 PET
Lua: Se terminó de ejecutar el script de lua
No hubieron errores interpretando el archivo'
Se cargó y ejecutó el archivo por completo
get field 'probandolua' 
push 1 y push 2 
Esta es la función de prueba Lua    nil    12312,56
No hubieron errores llamando la función 'probandolua'
Se va  a llamar a 'luaclose'
Program received signal SIGSEGV
free () in /lib/tls/i686/cmov/libc-2.7.so
(idb) bt
#0  0xb7d634ac in free () in /lib/tls/i686/cmov/libc-2.7.so
#1  0x080609e2 in l_alloc () in /home/raulhuertas/Documentos/Proyectos/LuaExample/dist/Release/IntelSDK-Linux-x86/luaexample
#2  0xb77b9a60

I've not debugged before(), can this be a libc bug? or a free to an already deleted memory location?

_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

On Mon, Nov 24, 2008 at 2:12 AM, Raúl Huertas <rax...@ho...> wrote:
>
> Whel, what I did for use lua 5.1.4 was to change all the content in the lua
> source bundle with wxLua(v5.1.3) with the more recent 5.1.4. Since it's just
> a bug fix release, there is no problem.

Ok, but I might be wary of this. You can fetch the CVS version of
wxLua which has been upgraded to Lua 5.1.4.

> I'm working in Linux Ubuntu 8.10. I've tested with GCC 4.2 and Intel
> compiler 11.0, both the same result.
>
> In the program I sent there wasn't a requiere("wx") beacuse I was using the
> class wxLuaState. But then I removed the wxLua stuff from the C Code and add
> the 'require' function. The two frames are showed. Then the application
> crash just in lua_close.

If you use require("wx") then lua_close(L) is appropriate, however if
you use a wxLuaState then use wxlState.CloseLuaState(true); to have it
cleanup wxLua properly.

> There wouldn't be a problem if I only would need one lua_State(and I think I
> shouldn't use more), but, what if I need more LuaStates?

You can have many lua_States each with wxLua loaded with no problem.

-----------------------------------------

Could you compile wxLua and Lua with debug symbols and run your
program in gdb? When the program crashes just type "bt" (for
backtrace) and post the results.

Regards,
     John

On Mon, Nov 24, 2008 at 5:48 AM, Éjjeli Őrjárat <ejj...@gm...> wrote:
> Hi all!
> In my application I need a popup image like this:
> http://www.threebuttes.com/MicroTouch/NewHardwareSystrayBalloon.jpg
> Is this possible to do it in wxLUA? Or with any other Lua module? Hope I can
> implement it in my app...

I don't believe that this is supported in wxWidgets 2.8.x, but I
believe that it might be in the upcoming 2.9.x. You can try using the
wxTaskBarIcon and maybe a wxPopupWindow to simulate one though.

-John

Hi all!
In my application I need a popup image like this:
http://www.threebuttes.com/MicroTouch/NewHardwareSystrayBalloon.jpg
Is this possible to do it in wxLUA? Or with any other Lua module? Hope I can
implement it in my app...
P.S.: I've checked an another app using this balloon, and if I am correct,
that used a dll (User32.dll maybe...). I want to find a platform fre
solution.
Best regards:
Attila

Thank u J!


Whel, what I did for use lua 5.1.4 was to change all the content in the lua source bundle with wxLua(v5.1.3) with the more recent 5.1.4. Since it's just a bug fix release, there is no problem.

I'm working in Linux Ubuntu 8.10. I've tested with GCC 4.2 and Intel compiler 11.0, both the same result.

In the program I sent there wasn't a requiere("wx") beacuse I was using the class wxLuaState. But then I removed the wxLua stuff from the C Code and add the 'require' function. The two frames are showed. Then the application crash just in lua_close.

There wouldn't be a problem if I only would need one lua_State(and I think I shouldn't use more), but, what if I need more LuaStates?




_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us

I don't see anything immediately wrong with your code. But I don't
think it is complete, I assume that in the Lua program you have the
line:

require("wx")

The program should show the two frames, the program "hangs" in the
wxWidgets event loop until you close them by hand and then your
probandoLua function is called.

Can you debug it? What platform? Did you compile everything,
wxWidgets, wxLua, Lua, etc all on your system or are you using
somebody's else's binaries? You note that you had to change the Lua
from 5.1.4... but I'm not sure I understand what you mean by that. The
crash could be because you linked against different versions of Lua
perhaps?

Regards,
    John


2008/11/22 Raúl Huertas <rax...@ho...>:
> Hi!
>
> I've been using Lua 5.1.4 and lua_close never failed. Then I started to play
> with wxLua, and works great. The problem is that a call to lua_close(), when
> lua have loaded the wxLua module ,makes the aplication crash, a core dump.
> This is the lua file:
>
>
> function probandoLua( a, b  )
>     print("Esta es la función de prueba Lua", a, b)
>
> end
>
>
>
> frame = wx.wxFrame( wx.NULL,            -- no parent for toplevel windows
>                     wx.wxID_ANY,          -- don't need a wxWindow ID
>                     "Hola Raul")
>
> frame:Show(true)
>
> frame2 = wx.wxFrame( wx.NULL,            -- no parent for toplevel windows
>                      wx.wxID_ANY,          -- don't need a wxWindow ID
>                      "Hola Raul2",
>                      wx.wxDefaultPosition, wx.wxSize(168, 100),
>                      wx.wxDEFAULT_FRAME_STYLE)
>
> frame2:Show(true)
>
> wx.wxGetApp():MainLoop()
>
> Print("Lua: Se terminó de ejecutar el script de lua")
>
> And this is my C code:
>
> /*
>  * File:   Main.cpp
>  * Author: raulhuertas
>  *
>  * Created on 21 de noviembre de 2008, 15:32
>  */
>
> #include <stdlib.h>
> #include <lua.hpp>
> #include <iostream>
>
>
> using namespace std;
>
>
> const char* commandFile = "Hello.lua";
>
> /*
>  *
>  */
> int main(int argc, char** argv) {
>
>     lua_State* lua = luaL_newstate();
>     luaL_openlibs( lua );
>
>     cout<<"Version de Lua: "<< LUA_RELEASE <<endl;
>
>     if( luaL_loadfile( lua, "Hello.lua") ){
>         cout<<"Ha habido un error cargando el archivo "<<endl;
>         return(-1);
>     }
>     cout<<"Se cargó el archivo"<<endl;
>         switch( lua_pcall( lua, 0,0,0) ){
>         case 0: cout<<"No hubieron errores interpretando el archivo'"<<endl;
> break;
>         case LUA_ERRRUN: cout<<""<<endl; break;
>         case LUA_ERRMEM: cout<<""<<endl; break;
>         case LUA_ERRERR: cout<<""<<endl; break;
>         default: cout<<"Error desconocido de Lua"<<endl;
>     }
> //load file carga el archivo y su contenido lo coloca en la stack.
>     //Al momento de 'call' una chunk, lo que se realiza es interpretar todo
> su contenido
>
>     cout<<"Se cargó y ejecutó el archivo por completo"<<endl;
>     /******Invocnado Lua desde C*******/
>     //Vamos a llamar la función 'probandoLua' que se definió en el archivo
> anterior
>
>     lua_getfield( lua, LUA_GLOBALSINDEX, "probandoLua");
>     cout<<"get field 'probandolua' "<<endl;
>     lua_pushstring(lua, argv[1] );
>     lua_pushnumber(lua, 12312.56);
>     cout<<"push 1 y push 2 "<<endl;
>     switch( lua_pcall( lua, 2,0,0) ){
>         case 0: cout<<"No hubieron errores llamando la función
> 'probandolua'"<<endl; break;
>         case LUA_ERRRUN: cout<<""<<endl; break;
>         case LUA_ERRMEM: cout<<""<<endl; break;
>         case LUA_ERRERR: cout<<""<<endl; break;
>         default: cout<<"Error desconocido de Lua"<<endl;
>     }
>
>     cout<<"Se va  a llamar a 'luaclose'"<<endl;
>     lua_close(lua);
>
>     int r;
>     cin>>r;
>
>     return (EXIT_SUCCESS);
> }
>
>
> In the wxLua installation files I changed the lua module for the version
> 5.1.4.(else 'make install' would my system lua.h to 5.1.3).
>
> Some help please
>
>
> ________________________________
> Discover the new Windows Vista Learn more!
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

Hi!

I've been using Lua 5.1.4 and lua_close never failed. Then I started to play with wxLua, and works great. The problem is that a call to lua_close(), when lua have loaded the wxLua module ,makes the aplication crash, a core dump.
This is the lua file:


function probandoLua( a, b  )
    print("Esta es la función de prueba Lua", a, b)

end



frame = wx.wxFrame( wx.NULL,            -- no parent for toplevel windows
                    wx.wxID_ANY,          -- don't need a wxWindow ID
                    "Hola Raul")

frame:Show(true)

frame2 = wx.wxFrame( wx.NULL,            -- no parent for toplevel windows
                     wx.wxID_ANY,          -- don't need a wxWindow ID
                     "Hola Raul2",
                     wx.wxDefaultPosition, wx.wxSize(168, 100),
                     wx.wxDEFAULT_FRAME_STYLE)

frame2:Show(true)

wx.wxGetApp():MainLoop()

Print("Lua: Se terminó de ejecutar el script de lua")

And this is my C code:

/* 
 * File:   Main.cpp
 * Author: raulhuertas
 *
 * Created on 21 de noviembre de 2008, 15:32
 */

#include <stdlib.h>
#include <lua.hpp>
#include <iostream>


using namespace std;


const char* commandFile = "Hello.lua";

/*
 * 
 */
int main(int argc, char** argv) {

    lua_State* lua = luaL_newstate();
    luaL_openlibs( lua );

    cout<<"Version de Lua: "<< LUA_RELEASE <<endl;
        
    if( luaL_loadfile( lua, "Hello.lua") ){
        cout<<"Ha habido un error cargando el archivo "<<endl;
        return(-1);
    }
    cout<<"Se cargó el archivo"<<endl;
        switch( lua_pcall( lua, 0,0,0) ){
        case 0: cout<<"No hubieron errores interpretando el archivo'"<<endl; break;
        case LUA_ERRRUN: cout<<""<<endl; break;
        case LUA_ERRMEM: cout<<""<<endl; break;
        case LUA_ERRERR: cout<<""<<endl; break;
        default: cout<<"Error desconocido de Lua"<<endl;
    }
//load file carga el archivo y su contenido lo coloca en la stack.
    //Al momento de 'call' una chunk, lo que se realiza es interpretar todo su contenido

    cout<<"Se cargó y ejecutó el archivo por completo"<<endl;
    /******Invocnado Lua desde C*******/
    //Vamos a llamar la función 'probandoLua' que se definió en el archivo anterior

    lua_getfield( lua, LUA_GLOBALSINDEX, "probandoLua");
    cout<<"get field 'probandolua' "<<endl;
    lua_pushstring(lua, argv[1] );
    lua_pushnumber(lua, 12312.56);
    cout<<"push 1 y push 2 "<<endl;
    switch( lua_pcall( lua, 2,0,0) ){
        case 0: cout<<"No hubieron errores llamando la función 'probandolua'"<<endl; break;
        case LUA_ERRRUN: cout<<""<<endl; break;
        case LUA_ERRMEM: cout<<""<<endl; break;
        case LUA_ERRERR: cout<<""<<endl; break;
        default: cout<<"Error desconocido de Lua"<<endl;
    }

    cout<<"Se va  a llamar a 'luaclose'"<<endl;
    lua_close(lua);

    int r;
    cin>>r;

    return (EXIT_SUCCESS);
}


In the wxLua installation files I changed the lua module for the version 5.1.4.(else 'make install' would my system lua.h to 5.1.3). 

Some help please 


_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

On Thu, Nov 20, 2008 at 11:14 PM, John Labenski <jla...@gm...> wrote:

>
> What about GetString()? Doesn't that return the string of the URL? The
> only thing that the wxTextUrlEvent adds are functions to get the
> integer start and end position of the URL in the textctrl.
>

Currently GetString() gives me back an empty string on this event. I just
went down the list and tried all of the getter functions, but nothing seemed
to be returning any actual info.

Thanks,

Evan

On Thu, Nov 20, 2008 at 9:55 PM, Evan DeMond <eva...@gm...> wrote:
> Hello all,
>
> Hate to bother the list, but I've been trying to figure out how to handle
> URL clicks in wxTextCtrl and I haven't been too successful:
>
> I've connected a handler to wxEVT_COMMAND_TEXT_URL and am able to receive an
> event when I click or mouse over a URL. From there, I'd like to extract that
> URL so I can launch a browser for it. The event I get is a wxCommandEvent,
> though, and it doesn't seem to have any data. Being a wxCommandEvent, it
> doesn't have the functions I read about here -
> http://wiki.wxwidgets.org/WxTextUrlEvent - and of all of the Get functions
> return 0, nil, false, etc.

What about GetString()? Doesn't that return the string of the URL? The
only thing that the wxTextUrlEvent adds are functions to get the
integer start and end position of the URL in the textctrl.

> My Googling turns up a few bug bounties about this in wxWidgets itself; it
> seems like it's not supported on all platforms yet. That being the case,
> does wxLua have a binding for this currently?

I think the wxTextUrlEvent is new(ish) and I will add it for the 2.8.9
version of wxLua.

Regards,
    John

Hello all,

Hate to bother the list, but I've been trying to figure out how to handle
URL clicks in wxTextCtrl and I haven't been too successful:

I've connected a handler to wxEVT_COMMAND_TEXT_URL and am able to receive an
event when I click or mouse over a URL. From there, I'd like to extract that
URL so I can launch a browser for it. The event I get is a wxCommandEvent,
though, and it doesn't seem to have any data. Being a wxCommandEvent, it
doesn't have the functions I read about here -
http://wiki.wxwidgets.org/WxTextUrlEvent - and of all of the Get functions
return 0, nil, false, etc.

My Googling turns up a few bug bounties about this in wxWidgets itself; it
seems like it's not supported on all platforms yet. That being the case,
does wxLua have a binding for this currently?

Thanks,

Evan

On Tue, Nov 18, 2008 at 11:17 AM, John Labenski <jla...@gm...> wrote:

>
> Just use your wxFrame or any wxWindow; you can even use wxGetApp(),
> the wxApp. There's nothing special about any particular wxEvtHandler.
> The only thing you have to worry about is being able to determine
> where the events come from, use unique IDs.


Sounds like a better idea than mine. Thanks.

> As an aside, is there any known reason why wxSocketBase shouldn't derive
> > from wxEvtHandler? That choice doesn't entirely make sense to me.
>
> Because it doesn't in C++.
>

Sure, I realize that. I was just asking if anyone knew why it's that way in
wxWidgets to begin with. Off-topic for this list, I guess, so sorry for the
noise, and I'll take that question elsewhere.

Thanks again,

Evan