wxlua-users Mailing List for wxLua

Hi John,
> Yes, note that From8BitData() is static and To8BitData() is not.
Thank you for the prompt change! Unfortunately, it didn't have the
desired effect for me; maybe I misread wxwidgets documentation.
Let's say I have three invalid UTF-8 characters: string.char(0x80,
0x81, 0x82). If I assigned them to a variable u, it has proper length
(#u == 3). If I try to add them to wxSTC, nothing happens (the length
of the content doesn't change).
If I use From8BitData(), then I get 6 bytes instead of 3:
#wx.wxString.From8BitData(string.char(0x80, 0x81, 0x82)) == 6, but
this looks like "fixed" UTF-8 code. When I add the result to wxSTC, I
do get 6 bytes of content there, but that's not what I expected: I
expected three characters displayed with 0x80, 0x81, and 0x82 as their
codes.
What am I doing wrong?
Paul.
On Wed, Feb 19, 2014 at 9:53 PM, John Labenski <jla...@gm...> wrote:
> On Wed, Feb 19, 2014 at 1:27 AM, Paul K <pau...@ya...> wrote:
>>
>>
>> Do we also get To8BitData(), as I may need it to save the data back to a
>> file?
>>
>
> Yes, note that From8BitData() is static and To8BitData() is not.
>
> Regards,
> John

----- Original Message -----
From: John Labenski
Date: 2/20/2014 10:47 AM
> wxWebView shouldn't be too hard to wrap, it looks like a single c++ 
> header file and a new lib to link to, wx30+ only.
I don't know the first thing about creating a wxLua binding, but if 
nobody else is already working on it or wants to, I'll see if I can find 
some time. I primarily desire to hook up wxWebViewChromium 
(https://github.com/steve-lamerton/wxWebViewChromium) in my wxLua 
application.
>
> I asked previously about wxPropertyGrid, but I believe John said that
> it's going to be more work than seems from the API, so I found a
> different way to do what I wanted.
>
>
> Yes, wxPropertyGrid is a huge project with lots of little helper 
> classes. Admittedly, most people need only a tiny part of it. I 
> remember that there was something funny about it though, something 
> about #defines and pointers that seemed like wrapping it might be 
> awkward, but looking now I don't see why I thought that.
As a small sampling for information's sake, in looking at a fairly 
complete sample of how I use wxPropertyGrid in C++ code, I touch:
* wxPropertyGridManager
* wxPropertyGridPage
* wxPropertyGridEvent
* wxPGId
* wxPGProperty
* wxEVT_PG_CHANGED, wxEVT_PG_SELECTED, wxEVT_PG_RIGHT_CLICK, 
wxEVT_COMMAND_TEXT_UPDATED, wxEVT_COMMAND_BUTTON_CLICKED, wxEVT_CHILD_FOCUS
* wxPGRegisterEditorClass with 
wxPropertyGridManager::SetPropertyEditor() and derived wxPGEditor and 
wxPGProperty classes
Thanks for your help!
Josh

On Thu, Feb 20, 2014 at 11:36 AM, Paul K <pau...@ya...> wrote:
> I didn't realize we don't have wxWebView binding. I'm very much
> interested in that as well.
>
>
wxWebView shouldn't be too hard to wrap, it looks like a single c++ header
file and a new lib to link to, wx30+ only.
> I asked previously about wxPropertyGrid, but I believe John said that
> it's going to be more work than seems from the API, so I found a
> different way to do what I wanted.
>
>
Yes, wxPropertyGrid is a huge project with lots of little helper classes.
Admittedly, most people need only a tiny part of it. I remember that there
was something funny about it though, something about #defines and pointers
that seemed like wrapping it might be awkward, but looking now I don't see
why I thought that.
John

I didn't realize we don't have wxWebView binding. I'm very much
interested in that as well.
I asked previously about wxPropertyGrid, but I believe John said that
it's going to be more work than seems from the API, so I found a
different way to do what I wanted.
Paul.
On Thu, Feb 20, 2014 at 6:26 AM, Joshua Jensen
<jj...@wo...> wrote:
> Hi.
>
> I am in need of bindings to wxPropertyGrid and wxWebView.
>
> Before looking into what it takes to make a proper wxLua binding, is
> anybody currently working on these?
>
> Thanks.
>
> Josh

Hi.
I am in need of bindings to wxPropertyGrid and wxWebView.
Before looking into what it takes to make a proper wxLua binding, is 
anybody currently working on these?
Thanks.
Josh

On Wed, Feb 19, 2014 at 1:27 AM, Paul K <pau...@ya...> wrote:
>
> Do we also get To8BitData(), as I may need it to save the data back to a
> file?
>
>
Yes, note that From8BitData() is static and To8BitData() is not.
Regards,
 John

Hi John,
> I'm no expert in UTF8, but isn't it possible that a malformed UTF8 sequence makes the rest of the file unusable in the sense that you can't really be sure how many bytes the 'bad' sequence is so you could be off by a few bytes for the rest of the file?
Not really, as you can simply skip all invalied 8-bit characters
(which is what I do to "fix" invalid sequences). Scintilla does better
as it can display them as well.
> From8BitData() is now in SVN trunk. I'm not sure that it will help as it uses the wxConvISO8859_1 converter, but it is different than the normal wxConvUTF8 converted used normally.
Do we also get To8BitData(), as I may need it to save the data back to a file?
I'll compile and give it a test some time tomorrow... Thank you!
Paul.

On Tue, Feb 18, 2014 at 2:12 PM, Paul K <pau...@ya...> wrote:
...
> What I am trying to do is to load a file into wxSTC (Scintilla
> component). I know that Scintilla can deal with invalid UTF-8
> characters as SciTE displays them as nice inverted rounded boxes with
> hex codes inside, but I can't get the same effect with wxSTC. If I try
> to load UTF-8 file with characters in, for example, 1252 encoding, the
> content fails to load into wxSTC (it shows as empty).
>
>
I'm no expert in UTF8, but isn't it possible that a malformed UTF8 sequence
makes the rest of the file unusable in the sense that you can't really be
sure how many bytes the 'bad' sequence is so you could be off by a few
bytes for the rest of the file?
What's interesting is that the content is loaded from a file just
> fine, so it seems like at least that part is handled correctly, but
> the text is not loaded into wxSTC until I find and fix invalid UTF-8
> characters (I use SetText method, but I've tried others with the same
> result). I thought that using From8BitData() may help me to pass all
> those characters intact to Scintilla, which will be able to display
> them, but I can't test as From8BitData() is not exposed in wxlua.
>
>
From8BitData() is now in SVN trunk. I'm not sure that it will help as it
uses the wxConvISO8859_1 converter, but it is different than the normal
wxConvUTF8 converted used normally.
Regards,
 John

Hi John,
I'm looking for a way to handle (possibly) invalid UTF-8 characters
and seem to be missing wxString::From8BitData() and
wxString::To8BitData() methods (according to this page:
http://docs.wxwidgets.org/trunk/overview_unicode.html#overview_unicode_supportout).
What I am trying to do is to load a file into wxSTC (Scintilla
component). I know that Scintilla can deal with invalid UTF-8
characters as SciTE displays them as nice inverted rounded boxes with
hex codes inside, but I can't get the same effect with wxSTC. If I try
to load UTF-8 file with characters in, for example, 1252 encoding, the
content fails to load into wxSTC (it shows as empty).
You can see this effect by running editor.wx.lua example. Just try to
load a file that has 232円 or 226円 character and the content is going
to be empty.
What's interesting is that the content is loaded from a file just
fine, so it seems like at least that part is handled correctly, but
the text is not loaded into wxSTC until I find and fix invalid UTF-8
characters (I use SetText method, but I've tried others with the same
result). I thought that using From8BitData() may help me to pass all
those characters intact to Scintilla, which will be able to display
them, but I can't test as From8BitData() is not exposed in wxlua.
I'm open to other ideas to make it work...
Paul.

Hi John,
> Yes, there are far more differences than I realized, you'll have to use --enable-compat28 for the near future.
That's okay; I already added it to some of my build scripts, just
wanted to let you know.
> I have also seen some problems with the wxLua app (editor.wx.lua) not exiting for some reason with 3.0, but not 2.9.x if I remember correctly.
I have seen this in my application as well, even with 2.9.5. I'd like
to get to the bottom of it, but so far I've been using os.exit() at
the end of my main script. For some reason, each of the platforms is
guilty in some way:
-- (1) to fix a crash on OSX when closing with debugging in progress.
-- (2) to fix a crash on Linux 32/64bit during GC cleanup in wxlua
-- after an external process has been started from the IDE.
-- (3) to fix exit on Windows when started as "bin\lua src\main.lua".
I just tested the last one using 2.9.5; if I don't have os.exit() at
the end, the script just hangs. Not sure why... In cases 1 and 2, I do
call :Detach() on the started process, but it still crashes after
MainLoop is done without os.exit().
Paul.
On Fri, Feb 7, 2014 at 8:44 PM, John Labenski <jla...@gm...> wrote:
> On Fri, Feb 7, 2014 at 6:48 PM, Paul K <pau...@ya...> wrote:
>>
>> Hi John,
>>
>> I came across few more compilation errors when compat28 flag is not used:
>>
>
> Yes, there are far more differences than I realized, you'll have to use
> --enable-compat28 for the near future. I have also seen some problems with
> the wxLua app (editor.wx.lua) not exiting for some reason with 3.0, but not
> 2.9.x if I remember correctly.
>
> I am also thinking that the switch to 3.0 without compat28 will probably
> pose problems for people since Lua won't give "compile time" errors for
> missing/changed functions. It might not be too hard to make some sort of
> diff file using the code from bindings.wx.lua to print the full list of
> functions for each version.
>
> John
>
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

On Fri, Feb 7, 2014 at 6:48 PM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I came across few more compilation errors when compat28 flag is not used:
>
>
Yes, there are far more differences than I realized, you'll have to use
--enable-compat28 for the near future. I have also seen some problems with
the wxLua app (editor.wx.lua) not exiting for some reason with 3.0, but not
2.9.x if I remember correctly.
I am also thinking that the switch to 3.0 without compat28 will probably
pose problems for people since Lua won't give "compile time" errors for
missing/changed functions. It might not be too hard to make some sort of
diff file using the code from bindings.wx.lua to print the full list of
functions for each version.
John

Hi John,
I came across few more compilation errors when compat28 flag is not used:
[ 17%] Building CXX object
modules/luamodule/CMakeFiles/wxLuaModule.dir/__/wxbind/src/wxcore_geometry.cpp.o
/home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:
In function 'int wxLua_wxMouseState_LeftDown(lua_State*)':
/home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:455:27:
error: 'class wxMouseState' has no member named 'LeftDown'
 bool returns = (self->LeftDown());
 ^
/home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:
In function 'int wxLua_wxMouseState_MiddleDown(lua_State*)':
/home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:487:27:
error: 'class wxMouseState' has no member named 'MiddleDown'
 bool returns = (self->MiddleDown());
 ^
/home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:
In function 'int wxLua_wxMouseState_RightDown(lua_State*)':
/home/paul/zbs/build/wxlua/wxLua/modules/wxbind/src/wxcore_defsutils.cpp:503:27:
error: 'class wxMouseState' has no member named 'RightDown'
 bool returns = (self->RightDown());
 ^
This is using the latest trunk of wxlua and wxwidgets (compiling on Linux).
The compilation proceeded successfully when I added --enable-compat28.
Paul.

On Thu, Jan 30, 2014 at 1:22 AM, John Labenski <jla...@gm...> wrote:
> On Tue, Jan 28, 2014 at 12:06 PM, Paul K <pau...@ya...> wrote:
>
>> Hi John,
>>
>> > It looks like there is nothing special with their URLDropTarget. I
>> think that simply using the wxLuaTextDropTarget would work. I have added a
>> few more methods to wxDropTarget, namely SetDataObject(), which is probably
>> the key to making it work.
>>
>>
Unfortunately I had to add a whole new class to handle it since the
wxURLDataObject doesn't drive from wxTextDataObject in MSW as it does in
the other ports. There is a very basic sample of its usage in
htmlwin.wx.lua.
Regards,
 John