Re: [wxlua-users] Preliminary wxLua Binaries for 2.8.12 for MSW

[Paul K <pau...@ya...>]

Hi John,

One more update. I didn't mention how I got the app running, which is
the best configuration I can get so far. I deployed wx.dll and
wxlua_lua_shared-wx28mswu-2.8.12.dll as well as lua_shared.exe
(renamed as lua.exe) and kept my *current lua5.1.dll* file. This way I
could get the app started even though it still crashes in several
places (but at least the luasocket library is working).

I'm also getting strange errors where I had none before; for example,

Expected an 'unsigned integer' for parameter 1, but got a 'number'.
Function called: 'wxMilliSleep(number)'
01. wxMilliSleep(integer)

Is it possible that there is something wrong with the binding as
"unsigned integer" should be easily mappable to "number"?

Another strange error is this:

wxLua: Creating a callback function in a coroutine is not allowed
since it will only be called when the thread is either suspended or
dead.
stack traceback:
	[C]: in function 'Connect'

This is probably in reference to this normally looking code (it's not
using any coroutines):

  frame:Connect(wx.wxEVT_CLOSE_WINDOW,
    function(event)
      if inloop then event:Skip() frame = nil else os.exit() end
    end)

In addition to that, I'm getting an appcrash when I close the app
(inside ntdll.dll), but this is likely because I'm using your lua.exe
with my dll from a previous version. For some reason using my current
lua.exe crashes the app with an error in
wxlua_lua_shared-wx28mswu-2.8.12.dll (which I reported earlier).

Paul.

On Thu, Jun 28, 2012 at 11:51 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> Couple of other things. The new version seems to be using
> significantly less memory. When I can get the app to start, it's only
> using about 7.8M memory, where the old one was using 13-14M. This may
> be related to the reduced size of the dlls.
>
> Also, the error message box is gone and the app seems to be failing
> silently where the old one was reporting errors in a nice dialog with
> wxLua title and a message "Lua: error while running chunk". This was
> one of the primary reasons we stayed with the binaries we are
> currently using and I'd love to have that error message back.
>
> The error messages we used to be getting seem to be coming from
> "wxString wxlua_LUA_ERR_msg(int LUA_ERRx)" function in wxlstate.cpp
> with the value LUA_ERRRUN. I'm not sure why the new version doesn't
> trigger/report that anymore.
>
> Paul.
>
> On Thu, Jun 28, 2012 at 11:34 PM, Paul K <pau...@ya...> wrote:
>> Hi John,
>>
>> Thank you for making the binaries available! I gave the Unicode
>> binaries a try, but the results are a mixed bag. I can barely get them
>> running for my application, which allows me to confirm that UTF-8
>> encoding is now working, but other encodings stopped working. For
>> example, if I set font encoding to wx.wxFONTENCODING_CP1251, I see no
>> difference (it looks like it's always "fixed" to utf-8). This may be a
>> feature though. If this is going to be the way it is, I'm fine with
>> it.
>>
>> Also, I can't get the binaries to work correctly with my application.
>> The first issue is that the existing lua socket binaries fail to load:
>>
>> ...\bin\lua.EXE: error loading module 'socket.core' from file
>> 'bin/clibs/socket\core.dll':
>>        The specified module could not be found.
>>
>> even though the module *is* there and loads fine using the old
>> binaries. This may be related to the fact that socket\core.dll seems
>> to be compiled against lua5.1.dll, which you didn't include in the
>> package (and my existing one didn't work as it's not for 5.1.5).
>>
>> If I comment luasocket out, the app crashed somewhere in
>> wxlua_lua_shared-wx28mswu-2.8.12.dll:
>>
>> Problem Event Name:     APPCRASH
>>  Application Name:     lua.exe
>>  Application Version:  0.0.0.0
>>  Application Timestamp:        4fed3948
>>  Fault Module Name:    wxlua_lua_shared-wx28mswu-2.8.12.dll
>>  Fault Module Version: 0.0.0.0
>>  Fault Module Timestamp:       4fed3947
>>  Exception Code:       c0000005
>>  Exception Offset:     0000d8b2
>>  OS Version:   6.0.6002.2.2.0.256.6
>>  Locale ID:    1033
>>  Additional Information 1:     fd00
>>  Additional Information 2:     ea6f5fe8924aaa756324d57f87834160
>>  Additional Information 3:     fd00
>>  Additional Information 4:     ea6f5fe8924aaa756324d57f87834160
>>
>> This is running on Windows Vista (32bit). I only deployed wx.dll and
>> wxlua_lua_shared-wx28mswu-2.8.12.dll (not sure what
>> wxlua_lua_shared-wx28mswu-2.9.4.dll was for as wx.dll didn't want to
>> work without 2.8.12.dll). I thought I could pick what version of
>> wxwidgets I want to use (2.8.12 vs. 2.9.4), but it didn't work that
>> way.
>>
>> I don't quite understand the difference between lua.exe and
>> lua_shared.exe. It seems like lua.exe doesn't need lua51.dll, but
>> lua_shared.exe runs without that dll also, as you don't seem to
>> include the dll.
>>
>> Also,  wxLua* binaries (Freeze, Edit, etc.) seem to be statically
>> compiled and the previous version had them dynamically compiled (which
>> would be my preference, although other people may prefer it
>> differently).
>>
>> Paul.
>>
>> On Thu, Jun 28, 2012 at 10:29 PM, John Labenski <jla...@gm...> wrote:
>>> These are not well tested and things are not as complete as I would
>>> like, but better sooner than never.
>>>
>>> https://sourceforge.net/projects/wxlua/files/wxlua/2.8.12.0/
>>>
>>> Enjoy!
>>>
>>> -John Labenski
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> wxlua-users mailing list
>>> wxl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wxlua-users