wxlua-users Mailing List for wxLua

Hi Milind,
> I have a wxSyledTextCtrl control and if I set the SetWrapMode to wxSTC_WRAP_WORD and there are lines that actually wrap then the function EnsureCaretVisible does not scroll to the caret position. Is there any way to have wrapping and get this to work?
I remember running into the same issue. Try adding
styledTextCtrl:EnsureVisibleEnforcePolicy, as I remember it helping in
my case. It also helps if the position is inside a fold.
 local pos = #styledTextCtrl:GetText()
 styledTextCtrl:GotoPos(pos)
 styledTextCtrl:EnsureVisibleEnforcePolicy(styledTextCtrl:LineFromPosition(pos))
 --styledTextCtrl:EnsureCaretVisible()
 styledTextCtrl:SetFocus()
I suspect EnsureCaretVisible() may not be necessary in this case.
Paul.
On Thu, Jul 4, 2024 at 6:16 PM Milind Gupta <mil...@gm...> wrote:
>
> Hi Paul,
> I am trying to use the wxStyledTextCtrl and I see an issue and I was thinking you would know how to get around it.
>
> I have a wxSyledTextCtrl control and if I set the SetWrapMode to wxSTC_WRAP_WORD and there are lines that actually wrap then the function EnsureCaretVisible does not scroll to the caret position. Is there any way to have wrapping and get this to work?
>
> My code is attached.
> If the line:
> styledTextCtrl:SetWrapMode(wxstc.wxSTC_WRAP_WORD)
> is removed then there is no problem. But with this line the EnsureCaretVisible does not scroll all the way to the end.
>
> Do you know how to get around this problem?
>
> Thanks,
> Milind
>
>

Hi Paul,
 I am trying to use the wxStyledTextCtrl and I see an issue and I
was thinking you would know how to get around it.
I have a wxSyledTextCtrl control and if I set the SetWrapMode to
wxSTC_WRAP_WORD and there are lines that actually wrap then the function
EnsureCaretVisible does not scroll to the caret position. Is there any way
to have wrapping and get this to work?
My code is attached.
If the line:
styledTextCtrl:SetWrapMode(wxstc.wxSTC_WRAP_WORD)
is removed then there is no problem. But with this line the
EnsureCaretVisible does not scroll all the way to the end.
Do you know how to get around this problem?
Thanks,
Milind

> Now I am trying to see if there is any existing template function binding in any interface file so I can try to add that. Do you know of any that you looked at, or any idea of any particular thing to take care of to bind templates functions?
This I'm not sure about and am open to suggestions on how this can be
handled. I did implement CallAfter to support a callback, but not sure
how others can be implemented.
In terms of other questions, I don't think there are any specific
rules on which interface files have which classes; I've been mostly
following the established conventions. Let me know if I misunderstood
the question.
Paul.
On Sun, Oct 22, 2023 at 1:29 PM Milind Gupta <mil...@gm...> wrote:
>
> I see. I was calling it from the event object. Thanks for clarifying. For the other things any guidance on how it is decided which include file content goes where in wxlua?
>
> Thanks,
> Milind
>
> On 2023年10月22日 at 13:11, Paul K <pau...@gm...> wrote:
>>
>> Hi Milind,
>>
>> It works for me: `frame:CallAfter(function() os.exit() end)` is a
>> rough equivalent of
>> `frame:AddPendingEvent(wx.wxCommandEvent(wx.wxEVT_COMMAND_MENU_SELECTED,
>> ID.EXIT))`.
>>
>> It should be available for all wxFrame and other classes that inherit
>> from wxEvtHandler.
>>
>> Paul.
>>
>> On Sun, Oct 22, 2023 at 12:04 PM Milind Gupta <mil...@gm...> wrote:
>> >
>> > Hi Paul,
>> > I was trying to use the function Callafter as described here: https://docs.wxwidgets.org/3.0/classwx_evt_handler.html#a63c7351618fd77330d80a250b3719519
>> >
>> > I checked wxbase_base.i and I see that you have it defined there. But when I tried to call it and got the error of trying to call a nil value. So I thought it was not implemented.
>> > I had been trying to compare wxcore_event.i with event.h in wxwidgets/include/wx directory. Why is the event interface in wxbase? How do we determine where each include file in wxwidgets ends up in wxlua?
>> >
>> > Also since CallAfter was not there when I compiled the latest wxlua with the latest wxwidgets is there a compile flag to enable it?
>> >
>> > Thanks,
>> > Milind
>> >
>> >
>> >
>> > On 2023年10月21日 at 15:12, Paul K <pau...@gm...> wrote:
>> >>
>> >> Hi Milind,
>> >>
>> >> > I can follow some things. But now I opened the latest wxwidgets include file for events -event.h and this seems to have transformed a lot. Particularly there are some templates functions like CallAfter.
>> >>
>> >> I'm not sure where the event-related changes came from; have you
>> >> executed any-bind-sync.lua on your version?
>> >>
>> >> I'm not sure what may be needed for additional CallAfter support. I've
>> >> implemented the current one a while ago (it's in wxbase_base.i with an
>> >> override in wxbase_override.hpp).
>> >>
>> >> Is there anything in particular you're looking to add support for?
>> >> It's always better to start with a specific method/class that may be
>> >> missing and to add just it.
>> >>
>> >> Paul.
>> >>
>> >> On Wed, Oct 18, 2023 at 9:19 AM Milind Gupta <mil...@gm...> wrote:
>> >> >
>> >> > Thanks for all this information. I was going throught the interface files and to see how they are written I opened the wxwidgets version which the interface file said it was updated to. To see how things changed from the include file to the interface file.
>> >> > I can follow some things. But now I opened the latest wxwidgets include file for events -event.h and this seems to have transformed a lot. Particularly there are some templates functions like CallAfter. Now I am trying to see if there is any existing template function binding in any interface file so I can try to add that. Do you know of any that you looked at, or any idea of any particular thing to take care of to bind templates functions?
>> >> >
>> >> > Thanks,
>> >> > Milind
>> >> >
>> >> > On Tue, Oct 17, 2023, 11:41 PM Paul K <pau...@gm...> wrote:
>> >> >>
>> >> >> Hi Milind,
>> >> >>
>> >> >> > Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
>> >> >>
>> >> >> Not really, but I can suggest looking through some of the existing
>> >> >> bindings (including *_override.hpp files), as there is a variety of
>> >> >> binding from really simple to more complex ones that handle out
>> >> >> parameters and accept/return lua tables instead of lists of values.
>> >> >>
>> >> >> The bindings are quite forgiving and will accept the files that look
>> >> >> like header files; you may need to add `%wxchkver_3_2_1` statements
>> >> >> (as a line or block statement) to indicate when a particular API
>> >> >> change should be applied. The rest should be done by the genwxbind
>> >> >> script; in those cases when something non-standard (or more complex)
>> >> >> needs to be done, you can add an *_override.hpp file to provide the
>> >> >> necessary (manual) binding.
>> >> >>
>> >> >> > In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
>> >> >>
>> >> >> Correct; stc has been combined with the rest of the modules in modules/wxbind.
>> >> >>
>> >> >> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>> >> >>
>> >> >> Originally all binding updates have been done manually, which may
>> >> >> become quite tedious and difficult to maintain for large release
>> >> >> changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
>> >> >> some of that work. It uses wxwidgets interface files to pull changes
>> >> >> for specific versions and then compares those changes with the
>> >> >> existing bindings to figure out what needs to be updated and what
>> >> >> needs to be added/removed. You still need to pass it a specific
>> >> >> version number, so you can go from 3.2.0 to 3.2.1, but you can't go
>> >> >> from 3.1.0 to 3.2.0, as the script won't know where to get the changes
>> >> >> for intermediate releases.
>> >> >>
>> >> >> It replaces some of the manual work (and only for those classes that
>> >> >> are listed in the script), but still requires reviewing of the
>> >> >> results. It's supposed to only update interface files (*.i) and you
>> >> >> can then simply rerun the bindings generator (genwxbind script) to
>> >> >> apply the changes. Let me know if you have any other questions or run
>> >> >> into any issues with adding classes you're interested in.
>> >> >>
>> >> >> Paul.
>> >> >>
>> >> >> On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <mil...@gm...> wrote:
>> >> >> >
>> >> >> > Hi,
>> >> >> > A few questions about bindings.Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
>> >> >> > In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
>> >> >> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Milind
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > wxlua-users mailing list
>> >> >> > wxl...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> wxlua-users mailing list
>> >> >> wxl...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>> >> >
>> >> > _______________________________________________
>> >> > wxlua-users mailing list
>> >> > wxl...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>> >>
>> >>
>> >> _______________________________________________
>> >> wxlua-users mailing list
>> >> wxl...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>> >
>> > _______________________________________________
>> > wxlua-users mailing list
>> > wxl...@li...
>> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>>
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

I see. I was calling it from the event object. Thanks for clarifying. For
the other things any guidance on how it is decided which include file
content goes where in wxlua?
Thanks,
Milind
On 2023年10月22日 at 13:11, Paul K <pau...@gm...> wrote:
> Hi Milind,
>
> It works for me: `frame:CallAfter(function() os.exit() end)` is a
> rough equivalent of
> `frame:AddPendingEvent(wx.wxCommandEvent(wx.wxEVT_COMMAND_MENU_SELECTED,
> ID.EXIT))`.
>
> It should be available for all wxFrame and other classes that inherit
> from wxEvtHandler.
>
> Paul.
>
> On Sun, Oct 22, 2023 at 12:04 PM Milind Gupta <mil...@gm...>
> wrote:
> >
> > Hi Paul,
> > I was trying to use the function Callafter as described here:
> https://docs.wxwidgets.org/3.0/classwx_evt_handler.html#a63c7351618fd77330d80a250b3719519
> >
> > I checked wxbase_base.i and I see that you have it defined there. But
> when I tried to call it and got the error of trying to call a nil value. So
> I thought it was not implemented.
> > I had been trying to compare wxcore_event.i with event.h in
> wxwidgets/include/wx directory. Why is the event interface in wxbase? How
> do we determine where each include file in wxwidgets ends up in wxlua?
> >
> > Also since CallAfter was not there when I compiled the latest wxlua with
> the latest wxwidgets is there a compile flag to enable it?
> >
> > Thanks,
> > Milind
> >
> >
> >
> > On 2023年10月21日 at 15:12, Paul K <pau...@gm...> wrote:
> >>
> >> Hi Milind,
> >>
> >> > I can follow some things. But now I opened the latest wxwidgets
> include file for events -event.h and this seems to have transformed a lot.
> Particularly there are some templates functions like CallAfter.
> >>
> >> I'm not sure where the event-related changes came from; have you
> >> executed any-bind-sync.lua on your version?
> >>
> >> I'm not sure what may be needed for additional CallAfter support. I've
> >> implemented the current one a while ago (it's in wxbase_base.i with an
> >> override in wxbase_override.hpp).
> >>
> >> Is there anything in particular you're looking to add support for?
> >> It's always better to start with a specific method/class that may be
> >> missing and to add just it.
> >>
> >> Paul.
> >>
> >> On Wed, Oct 18, 2023 at 9:19 AM Milind Gupta <mil...@gm...>
> wrote:
> >> >
> >> > Thanks for all this information. I was going throught the interface
> files and to see how they are written I opened the wxwidgets version which
> the interface file said it was updated to. To see how things changed from
> the include file to the interface file.
> >> > I can follow some things. But now I opened the latest wxwidgets
> include file for events -event.h and this seems to have transformed a lot.
> Particularly there are some templates functions like CallAfter. Now I am
> trying to see if there is any existing template function binding in any
> interface file so I can try to add that. Do you know of any that you looked
> at, or any idea of any particular thing to take care of to bind templates
> functions?
> >> >
> >> > Thanks,
> >> > Milind
> >> >
> >> > On Tue, Oct 17, 2023, 11:41 PM Paul K <pau...@gm...> wrote:
> >> >>
> >> >> Hi Milind,
> >> >>
> >> >> > Apart from binding.html is there any other tutorial or cheat sheet
> how to translate wxWidgets include files to a interface file?
> >> >>
> >> >> Not really, but I can suggest looking through some of the existing
> >> >> bindings (including *_override.hpp files), as there is a variety of
> >> >> binding from really simple to more complex ones that handle out
> >> >> parameters and accept/return lua tables instead of lists of values.
> >> >>
> >> >> The bindings are quite forgiving and will accept the files that look
> >> >> like header files; you may need to add `%wxchkver_3_2_1` statements
> >> >> (as a line or block statement) to indicate when a particular API
> >> >> change should be applied. The rest should be done by the genwxbind
> >> >> script; in those cases when something non-standard (or more complex)
> >> >> needs to be done, you can add an *_override.hpp file to provide the
> >> >> necessary (manual) binding.
> >> >>
> >> >> > In the wxlua/bindings directory readme it says that the output
> bindings are placed at modules/wxbind and modules/wxbindstc. It seems
> wxbindstc is no more. I think stc binding rules place it in modules/wxbind.
> Is this updated to only generate at modules/wxbind?
> >> >>
> >> >> Correct; stc has been combined with the rest of the modules in
> modules/wxbind.
> >> >>
> >> >> > What is the purpose of the files: any-bind-sync.lua,
> stc-bind-sync.lua?
> >> >>
> >> >> Originally all binding updates have been done manually, which may
> >> >> become quite tedious and difficult to maintain for large release
> >> >> changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
> >> >> some of that work. It uses wxwidgets interface files to pull changes
> >> >> for specific versions and then compares those changes with the
> >> >> existing bindings to figure out what needs to be updated and what
> >> >> needs to be added/removed. You still need to pass it a specific
> >> >> version number, so you can go from 3.2.0 to 3.2.1, but you can't go
> >> >> from 3.1.0 to 3.2.0, as the script won't know where to get the
> changes
> >> >> for intermediate releases.
> >> >>
> >> >> It replaces some of the manual work (and only for those classes that
> >> >> are listed in the script), but still requires reviewing of the
> >> >> results. It's supposed to only update interface files (*.i) and you
> >> >> can then simply rerun the bindings generator (genwxbind script) to
> >> >> apply the changes. Let me know if you have any other questions or run
> >> >> into any issues with adding classes you're interested in.
> >> >>
> >> >> Paul.
> >> >>
> >> >> On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <
> mil...@gm...> wrote:
> >> >> >
> >> >> > Hi,
> >> >> > A few questions about bindings.Apart from binding.html is
> there any other tutorial or cheat sheet how to translate wxWidgets include
> files to a interface file?
> >> >> > In the wxlua/bindings directory readme it says that the
> output bindings are placed at modules/wxbind and modules/wxbindstc. It
> seems wxbindstc is no more. I think stc binding rules place it in
> modules/wxbind. Is this updated to only generate at modules/wxbind?
> >> >> > What is the purpose of the files: any-bind-sync.lua,
> stc-bind-sync.lua?
> >> >> >
> >> >> > Thanks,
> >> >> > Milind
> >> >> >
> >> >> > _______________________________________________
> >> >> > wxlua-users mailing list
> >> >> > wxl...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> wxlua-users mailing list
> >> >> wxl...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >> >
> >> > _______________________________________________
> >> > wxlua-users mailing list
> >> > wxl...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >>
> >>
> >> _______________________________________________
> >> wxlua-users mailing list
> >> wxl...@li...
> >> https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >
> > _______________________________________________
> > wxlua-users mailing list
> > wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Hi Milind,
It works for me: `frame:CallAfter(function() os.exit() end)` is a
rough equivalent of
`frame:AddPendingEvent(wx.wxCommandEvent(wx.wxEVT_COMMAND_MENU_SELECTED,
ID.EXIT))`.
It should be available for all wxFrame and other classes that inherit
from wxEvtHandler.
Paul.
On Sun, Oct 22, 2023 at 12:04 PM Milind Gupta <mil...@gm...> wrote:
>
> Hi Paul,
> I was trying to use the function Callafter as described here: https://docs.wxwidgets.org/3.0/classwx_evt_handler.html#a63c7351618fd77330d80a250b3719519
>
> I checked wxbase_base.i and I see that you have it defined there. But when I tried to call it and got the error of trying to call a nil value. So I thought it was not implemented.
> I had been trying to compare wxcore_event.i with event.h in wxwidgets/include/wx directory. Why is the event interface in wxbase? How do we determine where each include file in wxwidgets ends up in wxlua?
>
> Also since CallAfter was not there when I compiled the latest wxlua with the latest wxwidgets is there a compile flag to enable it?
>
> Thanks,
> Milind
>
>
>
> On 2023年10月21日 at 15:12, Paul K <pau...@gm...> wrote:
>>
>> Hi Milind,
>>
>> > I can follow some things. But now I opened the latest wxwidgets include file for events -event.h and this seems to have transformed a lot. Particularly there are some templates functions like CallAfter.
>>
>> I'm not sure where the event-related changes came from; have you
>> executed any-bind-sync.lua on your version?
>>
>> I'm not sure what may be needed for additional CallAfter support. I've
>> implemented the current one a while ago (it's in wxbase_base.i with an
>> override in wxbase_override.hpp).
>>
>> Is there anything in particular you're looking to add support for?
>> It's always better to start with a specific method/class that may be
>> missing and to add just it.
>>
>> Paul.
>>
>> On Wed, Oct 18, 2023 at 9:19 AM Milind Gupta <mil...@gm...> wrote:
>> >
>> > Thanks for all this information. I was going throught the interface files and to see how they are written I opened the wxwidgets version which the interface file said it was updated to. To see how things changed from the include file to the interface file.
>> > I can follow some things. But now I opened the latest wxwidgets include file for events -event.h and this seems to have transformed a lot. Particularly there are some templates functions like CallAfter. Now I am trying to see if there is any existing template function binding in any interface file so I can try to add that. Do you know of any that you looked at, or any idea of any particular thing to take care of to bind templates functions?
>> >
>> > Thanks,
>> > Milind
>> >
>> > On Tue, Oct 17, 2023, 11:41 PM Paul K <pau...@gm...> wrote:
>> >>
>> >> Hi Milind,
>> >>
>> >> > Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
>> >>
>> >> Not really, but I can suggest looking through some of the existing
>> >> bindings (including *_override.hpp files), as there is a variety of
>> >> binding from really simple to more complex ones that handle out
>> >> parameters and accept/return lua tables instead of lists of values.
>> >>
>> >> The bindings are quite forgiving and will accept the files that look
>> >> like header files; you may need to add `%wxchkver_3_2_1` statements
>> >> (as a line or block statement) to indicate when a particular API
>> >> change should be applied. The rest should be done by the genwxbind
>> >> script; in those cases when something non-standard (or more complex)
>> >> needs to be done, you can add an *_override.hpp file to provide the
>> >> necessary (manual) binding.
>> >>
>> >> > In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
>> >>
>> >> Correct; stc has been combined with the rest of the modules in modules/wxbind.
>> >>
>> >> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>> >>
>> >> Originally all binding updates have been done manually, which may
>> >> become quite tedious and difficult to maintain for large release
>> >> changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
>> >> some of that work. It uses wxwidgets interface files to pull changes
>> >> for specific versions and then compares those changes with the
>> >> existing bindings to figure out what needs to be updated and what
>> >> needs to be added/removed. You still need to pass it a specific
>> >> version number, so you can go from 3.2.0 to 3.2.1, but you can't go
>> >> from 3.1.0 to 3.2.0, as the script won't know where to get the changes
>> >> for intermediate releases.
>> >>
>> >> It replaces some of the manual work (and only for those classes that
>> >> are listed in the script), but still requires reviewing of the
>> >> results. It's supposed to only update interface files (*.i) and you
>> >> can then simply rerun the bindings generator (genwxbind script) to
>> >> apply the changes. Let me know if you have any other questions or run
>> >> into any issues with adding classes you're interested in.
>> >>
>> >> Paul.
>> >>
>> >> On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <mil...@gm...> wrote:
>> >> >
>> >> > Hi,
>> >> > A few questions about bindings.Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
>> >> > In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
>> >> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>> >> >
>> >> > Thanks,
>> >> > Milind
>> >> >
>> >> > _______________________________________________
>> >> > wxlua-users mailing list
>> >> > wxl...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>> >>
>> >>
>> >> _______________________________________________
>> >> wxlua-users mailing list
>> >> wxl...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>> >
>> > _______________________________________________
>> > wxlua-users mailing list
>> > wxl...@li...
>> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>>
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi Paul,
 I was trying to use the function Callafter as described here:
https://docs.wxwidgets.org/3.0/classwx_evt_handler.html#a63c7351618fd77330d80a250b3719519
I checked wxbase_base.i and I see that you have it defined there. But when
I tried to call it and got the error of trying to call a nil value. So I
thought it was not implemented.
I had been trying to compare wxcore_event.i with event.h in
wxwidgets/include/wx directory. Why is the event interface in wxbase? How
do we determine where each include file in wxwidgets ends up in wxlua?
Also since CallAfter was not there when I compiled the latest wxlua with
the latest wxwidgets is there a compile flag to enable it?
Thanks,
Milind
On 2023年10月21日 at 15:12, Paul K <pau...@gm...> wrote:
> Hi Milind,
>
> > I can follow some things. But now I opened the latest wxwidgets include
> file for events -event.h and this seems to have transformed a lot.
> Particularly there are some templates functions like CallAfter.
>
> I'm not sure where the event-related changes came from; have you
> executed any-bind-sync.lua on your version?
>
> I'm not sure what may be needed for additional CallAfter support. I've
> implemented the current one a while ago (it's in wxbase_base.i with an
> override in wxbase_override.hpp).
>
> Is there anything in particular you're looking to add support for?
> It's always better to start with a specific method/class that may be
> missing and to add just it.
>
> Paul.
>
> On Wed, Oct 18, 2023 at 9:19 AM Milind Gupta <mil...@gm...>
> wrote:
> >
> > Thanks for all this information. I was going throught the interface
> files and to see how they are written I opened the wxwidgets version which
> the interface file said it was updated to. To see how things changed from
> the include file to the interface file.
> > I can follow some things. But now I opened the latest wxwidgets
> include file for events -event.h and this seems to have transformed a lot.
> Particularly there are some templates functions like CallAfter. Now I am
> trying to see if there is any existing template function binding in any
> interface file so I can try to add that. Do you know of any that you looked
> at, or any idea of any particular thing to take care of to bind templates
> functions?
> >
> > Thanks,
> > Milind
> >
> > On Tue, Oct 17, 2023, 11:41 PM Paul K <pau...@gm...> wrote:
> >>
> >> Hi Milind,
> >>
> >> > Apart from binding.html is there any other tutorial or cheat sheet
> how to translate wxWidgets include files to a interface file?
> >>
> >> Not really, but I can suggest looking through some of the existing
> >> bindings (including *_override.hpp files), as there is a variety of
> >> binding from really simple to more complex ones that handle out
> >> parameters and accept/return lua tables instead of lists of values.
> >>
> >> The bindings are quite forgiving and will accept the files that look
> >> like header files; you may need to add `%wxchkver_3_2_1` statements
> >> (as a line or block statement) to indicate when a particular API
> >> change should be applied. The rest should be done by the genwxbind
> >> script; in those cases when something non-standard (or more complex)
> >> needs to be done, you can add an *_override.hpp file to provide the
> >> necessary (manual) binding.
> >>
> >> > In the wxlua/bindings directory readme it says that the output
> bindings are placed at modules/wxbind and modules/wxbindstc. It seems
> wxbindstc is no more. I think stc binding rules place it in modules/wxbind.
> Is this updated to only generate at modules/wxbind?
> >>
> >> Correct; stc has been combined with the rest of the modules in
> modules/wxbind.
> >>
> >> > What is the purpose of the files: any-bind-sync.lua,
> stc-bind-sync.lua?
> >>
> >> Originally all binding updates have been done manually, which may
> >> become quite tedious and difficult to maintain for large release
> >> changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
> >> some of that work. It uses wxwidgets interface files to pull changes
> >> for specific versions and then compares those changes with the
> >> existing bindings to figure out what needs to be updated and what
> >> needs to be added/removed. You still need to pass it a specific
> >> version number, so you can go from 3.2.0 to 3.2.1, but you can't go
> >> from 3.1.0 to 3.2.0, as the script won't know where to get the changes
> >> for intermediate releases.
> >>
> >> It replaces some of the manual work (and only for those classes that
> >> are listed in the script), but still requires reviewing of the
> >> results. It's supposed to only update interface files (*.i) and you
> >> can then simply rerun the bindings generator (genwxbind script) to
> >> apply the changes. Let me know if you have any other questions or run
> >> into any issues with adding classes you're interested in.
> >>
> >> Paul.
> >>
> >> On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <mil...@gm...>
> wrote:
> >> >
> >> > Hi,
> >> > A few questions about bindings.Apart from binding.html is
> there any other tutorial or cheat sheet how to translate wxWidgets include
> files to a interface file?
> >> > In the wxlua/bindings directory readme it says that the
> output bindings are placed at modules/wxbind and modules/wxbindstc. It
> seems wxbindstc is no more. I think stc binding rules place it in
> modules/wxbind. Is this updated to only generate at modules/wxbind?
> >> > What is the purpose of the files: any-bind-sync.lua,
> stc-bind-sync.lua?
> >> >
> >> > Thanks,
> >> > Milind
> >> >
> >> > _______________________________________________
> >> > wxlua-users mailing list
> >> > wxl...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >>
> >>
> >> _______________________________________________
> >> wxlua-users mailing list
> >> wxl...@li...
> >> https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >
> > _______________________________________________
> > wxlua-users mailing list
> > wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Hi Milind,
> I can follow some things. But now I opened the latest wxwidgets include file for events -event.h and this seems to have transformed a lot. Particularly there are some templates functions like CallAfter.
I'm not sure where the event-related changes came from; have you
executed any-bind-sync.lua on your version?
I'm not sure what may be needed for additional CallAfter support. I've
implemented the current one a while ago (it's in wxbase_base.i with an
override in wxbase_override.hpp).
Is there anything in particular you're looking to add support for?
It's always better to start with a specific method/class that may be
missing and to add just it.
Paul.
On Wed, Oct 18, 2023 at 9:19 AM Milind Gupta <mil...@gm...> wrote:
>
> Thanks for all this information. I was going throught the interface files and to see how they are written I opened the wxwidgets version which the interface file said it was updated to. To see how things changed from the include file to the interface file.
> I can follow some things. But now I opened the latest wxwidgets include file for events -event.h and this seems to have transformed a lot. Particularly there are some templates functions like CallAfter. Now I am trying to see if there is any existing template function binding in any interface file so I can try to add that. Do you know of any that you looked at, or any idea of any particular thing to take care of to bind templates functions?
>
> Thanks,
> Milind
>
> On Tue, Oct 17, 2023, 11:41 PM Paul K <pau...@gm...> wrote:
>>
>> Hi Milind,
>>
>> > Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
>>
>> Not really, but I can suggest looking through some of the existing
>> bindings (including *_override.hpp files), as there is a variety of
>> binding from really simple to more complex ones that handle out
>> parameters and accept/return lua tables instead of lists of values.
>>
>> The bindings are quite forgiving and will accept the files that look
>> like header files; you may need to add `%wxchkver_3_2_1` statements
>> (as a line or block statement) to indicate when a particular API
>> change should be applied. The rest should be done by the genwxbind
>> script; in those cases when something non-standard (or more complex)
>> needs to be done, you can add an *_override.hpp file to provide the
>> necessary (manual) binding.
>>
>> > In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
>>
>> Correct; stc has been combined with the rest of the modules in modules/wxbind.
>>
>> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>>
>> Originally all binding updates have been done manually, which may
>> become quite tedious and difficult to maintain for large release
>> changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
>> some of that work. It uses wxwidgets interface files to pull changes
>> for specific versions and then compares those changes with the
>> existing bindings to figure out what needs to be updated and what
>> needs to be added/removed. You still need to pass it a specific
>> version number, so you can go from 3.2.0 to 3.2.1, but you can't go
>> from 3.1.0 to 3.2.0, as the script won't know where to get the changes
>> for intermediate releases.
>>
>> It replaces some of the manual work (and only for those classes that
>> are listed in the script), but still requires reviewing of the
>> results. It's supposed to only update interface files (*.i) and you
>> can then simply rerun the bindings generator (genwxbind script) to
>> apply the changes. Let me know if you have any other questions or run
>> into any issues with adding classes you're interested in.
>>
>> Paul.
>>
>> On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <mil...@gm...> wrote:
>> >
>> > Hi,
>> > A few questions about bindings.Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
>> > In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
>> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>> >
>> > Thanks,
>> > Milind
>> >
>> > _______________________________________________
>> > wxlua-users mailing list
>> > wxl...@li...
>> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>>
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Thanks for all this information. I was going throught the interface files
and to see how they are written I opened the wxwidgets version which the
interface file said it was updated to. To see how things changed from the
include file to the interface file.
 I can follow some things. But now I opened the latest wxwidgets
include file for events -event.h and this seems to have transformed a lot.
Particularly there are some templates functions like CallAfter. Now I am
trying to see if there is any existing template function binding in any
interface file so I can try to add that. Do you know of any that you looked
at, or any idea of any particular thing to take care of to bind templates
functions?
Thanks,
Milind
On Tue, Oct 17, 2023, 11:41 PM Paul K <pau...@gm...> wrote:
> Hi Milind,
>
> > Apart from binding.html is there any other tutorial or cheat sheet how
> to translate wxWidgets include files to a interface file?
>
> Not really, but I can suggest looking through some of the existing
> bindings (including *_override.hpp files), as there is a variety of
> binding from really simple to more complex ones that handle out
> parameters and accept/return lua tables instead of lists of values.
>
> The bindings are quite forgiving and will accept the files that look
> like header files; you may need to add `%wxchkver_3_2_1` statements
> (as a line or block statement) to indicate when a particular API
> change should be applied. The rest should be done by the genwxbind
> script; in those cases when something non-standard (or more complex)
> needs to be done, you can add an *_override.hpp file to provide the
> necessary (manual) binding.
>
> > In the wxlua/bindings directory readme it says that the output bindings
> are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is
> no more. I think stc binding rules place it in modules/wxbind. Is this
> updated to only generate at modules/wxbind?
>
> Correct; stc has been combined with the rest of the modules in
> modules/wxbind.
>
> > What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>
> Originally all binding updates have been done manually, which may
> become quite tedious and difficult to maintain for large release
> changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
> some of that work. It uses wxwidgets interface files to pull changes
> for specific versions and then compares those changes with the
> existing bindings to figure out what needs to be updated and what
> needs to be added/removed. You still need to pass it a specific
> version number, so you can go from 3.2.0 to 3.2.1, but you can't go
> from 3.1.0 to 3.2.0, as the script won't know where to get the changes
> for intermediate releases.
>
> It replaces some of the manual work (and only for those classes that
> are listed in the script), but still requires reviewing of the
> results. It's supposed to only update interface files (*.i) and you
> can then simply rerun the bindings generator (genwxbind script) to
> apply the changes. Let me know if you have any other questions or run
> into any issues with adding classes you're interested in.
>
> Paul.
>
> On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <mil...@gm...>
> wrote:
> >
> > Hi,
> > A few questions about bindings.Apart from binding.html is there
> any other tutorial or cheat sheet how to translate wxWidgets include files
> to a interface file?
> > In the wxlua/bindings directory readme it says that the output
> bindings are placed at modules/wxbind and modules/wxbindstc. It seems
> wxbindstc is no more. I think stc binding rules place it in modules/wxbind.
> Is this updated to only generate at modules/wxbind?
> > What is the purpose of the files: any-bind-sync.lua,
> stc-bind-sync.lua?
> >
> > Thanks,
> > Milind
> >
> > _______________________________________________
> > wxlua-users mailing list
> > wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Hi Milind,
> Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
Not really, but I can suggest looking through some of the existing
bindings (including *_override.hpp files), as there is a variety of
binding from really simple to more complex ones that handle out
parameters and accept/return lua tables instead of lists of values.
The bindings are quite forgiving and will accept the files that look
like header files; you may need to add `%wxchkver_3_2_1` statements
(as a line or block statement) to indicate when a particular API
change should be applied. The rest should be done by the genwxbind
script; in those cases when something non-standard (or more complex)
needs to be done, you can add an *_override.hpp file to provide the
necessary (manual) binding.
> In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
Correct; stc has been combined with the rest of the modules in modules/wxbind.
> What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
Originally all binding updates have been done manually, which may
become quite tedious and difficult to maintain for large release
changes. I wrote any-bind-sync.lua and stc-bind-sync.lua to help with
some of that work. It uses wxwidgets interface files to pull changes
for specific versions and then compares those changes with the
existing bindings to figure out what needs to be updated and what
needs to be added/removed. You still need to pass it a specific
version number, so you can go from 3.2.0 to 3.2.1, but you can't go
from 3.1.0 to 3.2.0, as the script won't know where to get the changes
for intermediate releases.
It replaces some of the manual work (and only for those classes that
are listed in the script), but still requires reviewing of the
results. It's supposed to only update interface files (*.i) and you
can then simply rerun the bindings generator (genwxbind script) to
apply the changes. Let me know if you have any other questions or run
into any issues with adding classes you're interested in.
Paul.
On Tue, Oct 17, 2023 at 12:34 AM Milind Gupta <mil...@gm...> wrote:
>
> Hi,
> A few questions about bindings.Apart from binding.html is there any other tutorial or cheat sheet how to translate wxWidgets include files to a interface file?
> In the wxlua/bindings directory readme it says that the output bindings are placed at modules/wxbind and modules/wxbindstc. It seems wxbindstc is no more. I think stc binding rules place it in modules/wxbind. Is this updated to only generate at modules/wxbind?
> What is the purpose of the files: any-bind-sync.lua, stc-bind-sync.lua?
>
> Thanks,
> Milind
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi,
 A few questions about bindings.Apart from binding.html is there any
other tutorial or cheat sheet how to translate wxWidgets include files to a
interface file?
 In the wxlua/bindings directory readme it says that the output
bindings are placed at modules/wxbind and modules/wxbindstc. It seems
wxbindstc is no more. I think stc binding rules place it in modules/wxbind.
Is this updated to only generate at modules/wxbind?
 What is the purpose of the files: any-bind-sync.lua,
stc-bind-sync.lua?
Thanks,
Milind

> Yes it work now fine.
Thanks Klaas. I published and tagged a new release (v3.2.0.2) with
these changes.
Paul.
On Wed, Nov 2, 2022 at 8:45 AM klaas.holwerda <ng...@kl...> wrote:
>
> Hi Paul,
>
> Yes it work now fine.
>
> Thanks,
>
> Klaas
>
> On 02/11/2022 08:44, Paul K wrote:
> > Hi Klaas,
> >
> >> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
> >> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
> >> Maybe that is all to do to fix it.
>
>
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi Paul,
Yes it work now fine.
Thanks,
Klaas
On 02/11/2022 08:44, Paul K wrote:
> Hi Klaas,
>
>> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
>> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
>> Maybe that is all to do to fix it.

Hi Klaas,
> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
> Maybe that is all to do to fix it.
Thank you for the additional information and the suggested patch. Can
you check the current master branch, which includes the proposed
changes, and let me know if that works for you? Thank you.
Paul.
On Tue, Nov 1, 2022 at 10:25 AM klaas.holwerda <ng...@kl...> wrote:
>
> Hi Paul,
>
> That made no difference the problem stayed, that is against the latest release of wxWidgets 3.2.1, so I think it would be good to have it compiled against that version without problems.
>
> Make in the right *.i file this change here, resolves the problem, after regenerating the bindings.
>
> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
>
> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
>
> class wxRichTextLineList : public wxList
>
> {
>
> // Use the wxList methods, see also wxNode
>
> };
>
> #endif
>
> #endif
>
>
>
> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
>
> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
>
> wxRichTextLineList& GetLines();
>
> #endif
>
> #endif
>
> Maybe that is all to do to fix it.
>
> Regards,
>
> Klaas
>
> On 27/10/2022 03:50, Paul K wrote:
>
> Hi Klaas,
>
> With the latest wxWidgets, I had an issue with wxRichTextLineList.
> Using the defines down here in several places, I did succeed to compile.
> Do not know how to integrate it into *.i files, so hope you can do that.
>
> Thank you for the feedback. I'm actually updating documentation for
> the next release (v3.2.0.0) where I expect this issue to be resolved.
> I have tested this to-be-released version against the current master
> branch of wxwidgets.
>
> Can you get the current version from the repository and let me know if
> any modifications are still needed to get it compiled? You can just
> download the archive here:
> https://github.com/pkulchenko/wxlua/archive/refs/heads/master.zip
>
> Paul
>
> On Wed, Oct 26, 2022 at 12:00 PM klaas.holwerda <ng...@kl...> wrote:
>
> Hi Paul,
>
> I gave it a try.
> What do you use to compile on Windows normally?
> I generated with Cmake the VC project files, and although a bunch of warnings, it still works fine in the end.
> That is to say if I did not combine debug and release in one go.
>
> Maybe I will start to improve them, but how to work with github is unknow to me, used to subversion on sourceforge.
> Is there a patch system, or does it work different??
>
> With the latest wxWidgets, I had an issue with wxRichTextLineList.
> Using the defines down here in several places, I did succeed to compile.
> Do not know how to integrate it into *.i files, so hope you can do that.
>
> Much appreciated your work on wxLua!
>
> Regards,
>
> Klaas
>
> #if wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
>
> // ---------------------------------------------------------------------------
>
> // Bind class wxRichTextLineList
>
> // ---------------------------------------------------------------------------
>
> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
>
> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
>
> <<code>>
>
> #endif
>
> #endif
>
> #endif // wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
>
>
> On 13/09/2020 08:30, Paul K wrote:
>
> Hi wxlua users,
>
> I'm glad to announce the release of v3.1.0.0 of wxlua:
> https://github.com/pkulchenko/wxlua. It adds support for Lua 5.4,
> implements several new classes (wxDataViewCtrl, wxTranslations),
> includes a large number of improvements/fixes, and has been tested on
> the most recent version of wxwidgets (3.1.4) and its current master
> branch.
>
> The complete list of the changes in this version (and previous 9
> releases) is available here:
> https://github.com/pkulchenko/wxlua/blob/master/wxLua/docs/changelog.md.
> Note that there was an incompatibility introduced in this version that
> changes the order of parameters for `wxFileName.GetTimes` method.
>
> I don't have any precompiled binaries (and don't plan to provide
> them), but am exploring adding github actions to compile them on
> Windows/macOS/Linux, so if anyone has experience with those and can
> contribute working scripts, open a PR or an issue to collaborate. I
> also don't have Lua 5.3 and Lua 5.4 code included in the wxlua source
> tree, but will consider including it if it's needed to simplify the
> binary generation.
>
> Let me know if you run into any issues with it or have any other
> feedback. Thank you for all the support and contributions to the
> project.
>
> Paul.
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi Paul,
That made no difference the problem stayed, that is against the latest release of wxWidgets 3.2.1, 
so I think it would be good to have it compiled against that version without problems.
Make in the right *.i file this change here, resolves the problem, after regenerating the bindings.
#if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
#if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
         class wxRichTextLineList : public wxList
         {
                 // Use the wxList methods, see also wxNode
         };
#endif
#endif
#if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
#if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
   wxRichTextLineList& GetLines();
#endif
#endif
Maybe that is all to do to fix it.
Regards,
Klaas
On 27/10/2022 03:50, Paul K wrote:
> Hi Klaas,
>
>> With the latest wxWidgets, I had an issue with wxRichTextLineList.
>> Using the defines down here in several places, I did succeed to compile.
>> Do not know how to integrate it into *.i files, so hope you can do that.
> Thank you for the feedback. I'm actually updating documentation for
> the next release (v3.2.0.0) where I expect this issue to be resolved.
> I have tested this to-be-released version against the current master
> branch of wxwidgets.
>
> Can you get the current version from the repository and let me know if
> any modifications are still needed to get it compiled? You can just
> download the archive here:
> https://github.com/pkulchenko/wxlua/archive/refs/heads/master.zip
>
> Paul
>
> On Wed, Oct 26, 2022 at 12:00 PM klaas.holwerda<ng...@kl...> wrote:
>> Hi Paul,
>>
>> I gave it a try.
>> What do you use to compile on Windows normally?
>> I generated with Cmake the VC project files, and although a bunch of warnings, it still works fine in the end.
>> That is to say if I did not combine debug and release in one go.
>>
>> Maybe I will start to improve them, but how to work with github is unknow to me, used to subversion on sourceforge.
>> Is there a patch system, or does it work different??
>>
>> With the latest wxWidgets, I had an issue with wxRichTextLineList.
>> Using the defines down here in several places, I did succeed to compile.
>> Do not know how to integrate it into *.i files, so hope you can do that.
>>
>> Much appreciated your work on wxLua!
>>
>> Regards,
>>
>> Klaas
>>
>> #if wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
>>
>> // ---------------------------------------------------------------------------
>>
>> // Bind class wxRichTextLineList
>>
>> // ---------------------------------------------------------------------------
>>
>> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
>>
>> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
>>
>> <<code>>
>>
>> #endif
>>
>> #endif
>>
>> #endif // wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
>>
>>
>> On 13/09/2020 08:30, Paul K wrote:
>>
>> Hi wxlua users,
>>
>> I'm glad to announce the release of v3.1.0.0 of wxlua:
>> https://github.com/pkulchenko/wxlua. It adds support for Lua 5.4,
>> implements several new classes (wxDataViewCtrl, wxTranslations),
>> includes a large number of improvements/fixes, and has been tested on
>> the most recent version of wxwidgets (3.1.4) and its current master
>> branch.
>>
>> The complete list of the changes in this version (and previous 9
>> releases) is available here:
>> https://github.com/pkulchenko/wxlua/blob/master/wxLua/docs/changelog.md.
>> Note that there was an incompatibility introduced in this version that
>> changes the order of parameters for `wxFileName.GetTimes` method.
>>
>> I don't have any precompiled binaries (and don't plan to provide
>> them), but am exploring adding github actions to compile them on
>> Windows/macOS/Linux, so if anyone has experience with those and can
>> contribute working scripts, open a PR or an issue to collaborate. I
>> also don't have Lua 5.3 and Lua 5.4 code included in the wxlua source
>> tree, but will consider including it if it's needed to simplify the
>> binary generation.
>>
>> Let me know if you run into any issues with it or have any other
>> feedback. Thank you for all the support and contributions to the
>> project.
>>
>> Paul.
>>
>>
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>>
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi Klaas,
> With the latest wxWidgets, I had an issue with wxRichTextLineList.
> Using the defines down here in several places, I did succeed to compile.
> Do not know how to integrate it into *.i files, so hope you can do that.
Thank you for the feedback. I'm actually updating documentation for
the next release (v3.2.0.0) where I expect this issue to be resolved.
I have tested this to-be-released version against the current master
branch of wxwidgets.
Can you get the current version from the repository and let me know if
any modifications are still needed to get it compiled? You can just
download the archive here:
https://github.com/pkulchenko/wxlua/archive/refs/heads/master.zip
Paul
On Wed, Oct 26, 2022 at 12:00 PM klaas.holwerda <ng...@kl...> wrote:
>
> Hi Paul,
>
> I gave it a try.
> What do you use to compile on Windows normally?
> I generated with Cmake the VC project files, and although a bunch of warnings, it still works fine in the end.
> That is to say if I did not combine debug and release in one go.
>
> Maybe I will start to improve them, but how to work with github is unknow to me, used to subversion on sourceforge.
> Is there a patch system, or does it work different??
>
> With the latest wxWidgets, I had an issue with wxRichTextLineList.
> Using the defines down here in several places, I did succeed to compile.
> Do not know how to integrate it into *.i files, so hope you can do that.
>
> Much appreciated your work on wxLua!
>
> Regards,
>
> Klaas
>
> #if wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
>
> // ---------------------------------------------------------------------------
>
> // Bind class wxRichTextLineList
>
> // ---------------------------------------------------------------------------
>
> #if wxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
>
> #if wxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
>
> <<code>>
>
> #endif
>
> #endif
>
> #endif // wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
>
>
> On 13/09/2020 08:30, Paul K wrote:
>
> Hi wxlua users,
>
> I'm glad to announce the release of v3.1.0.0 of wxlua:
> https://github.com/pkulchenko/wxlua. It adds support for Lua 5.4,
> implements several new classes (wxDataViewCtrl, wxTranslations),
> includes a large number of improvements/fixes, and has been tested on
> the most recent version of wxwidgets (3.1.4) and its current master
> branch.
>
> The complete list of the changes in this version (and previous 9
> releases) is available here:
> https://github.com/pkulchenko/wxlua/blob/master/wxLua/docs/changelog.md.
> Note that there was an incompatibility introduced in this version that
> changes the order of parameters for `wxFileName.GetTimes` method.
>
> I don't have any precompiled binaries (and don't plan to provide
> them), but am exploring adding github actions to compile them on
> Windows/macOS/Linux, so if anyone has experience with those and can
> contribute working scripts, open a PR or an issue to collaborate. I
> also don't have Lua 5.3 and Lua 5.4 code included in the wxlua source
> tree, but will consider including it if it's needed to simplify the
> binary generation.
>
> Let me know if you run into any issues with it or have any other
> feedback. Thank you for all the support and contributions to the
> project.
>
> Paul.
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi Paul,
I gave it a try.
What do you use to compile on Windows normally?
I generated with Cmake the VC project files, and although a bunch of warnings, it still works fine 
in the end.
That is to say if I did not combine debug and release in one go.
Maybe I will start to improve them, but how to work with github is unknow to me, used to subversion 
on sourceforge.
Is there a patch system, or does it work different??
With the latest wxWidgets, I had an issue with wxRichTextLineList.
Using the defines down here in several places, I did succeed to compile.
Do not know how to integrate it into *.i files, so hope you can do that.
Much appreciated your work on wxLua!
Regards,
Klaas
#ifwxLUA_USE_wxRichText&& wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
// ---------------------------------------------------------------------------
// Bind class wxRichTextLineList
// ---------------------------------------------------------------------------
#ifwxRICHTEXT_USE_PARTIAL_TEXT_EXTENTS
#ifwxRICHTEXT_USE_OPTIMIZED_LINE_DRAWING
<<code>>
#endif
#endif
#endif// wxLUA_USE_wxRichText && wxCHECK_VERSION(3,0,0) && wxUSE_RICHTEXT
On 13/09/2020 08:30, Paul K wrote:
> Hi wxlua users,
>
> I'm glad to announce the release of v3.1.0.0 of wxlua:
> https://github.com/pkulchenko/wxlua. It adds support for Lua 5.4,
> implements several new classes (wxDataViewCtrl, wxTranslations),
> includes a large number of improvements/fixes, and has been tested on
> the most recent version of wxwidgets (3.1.4) and its current master
> branch.
>
> The complete list of the changes in this version (and previous 9
> releases) is available here:
> https://github.com/pkulchenko/wxlua/blob/master/wxLua/docs/changelog.md.
> Note that there was an incompatibility introduced in this version that
> changes the order of parameters for `wxFileName.GetTimes` method.
>
> I don't have any precompiled binaries (and don't plan to provide
> them), but am exploring adding github actions to compile them on
> Windows/macOS/Linux, so if anyone has experience with those and can
> contribute working scripts, open a PR or an issue to collaborate. I
> also don't have Lua 5.3 and Lua 5.4 code included in the wxlua source
> tree, but will consider including it if it's needed to simplify the
> binary generation.
>
> Let me know if you run into any issues with it or have any other
> feedback. Thank you for all the support and contributions to the
> project.
>
> Paul.
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi wxlua users,
I'm glad to announce the release of v3.1.0.0 of wxlua:
https://github.com/pkulchenko/wxlua. It adds support for Lua 5.4,
implements several new classes (wxDataViewCtrl, wxTranslations),
includes a large number of improvements/fixes, and has been tested on
the most recent version of wxwidgets (3.1.4) and its current master
branch.
The complete list of the changes in this version (and previous 9
releases) is available here:
https://github.com/pkulchenko/wxlua/blob/master/wxLua/docs/changelog.md.
Note that there was an incompatibility introduced in this version that
changes the order of parameters for `wxFileName.GetTimes` method.
I don't have any precompiled binaries (and don't plan to provide
them), but am exploring adding github actions to compile them on
Windows/macOS/Linux, so if anyone has experience with those and can
contribute working scripts, open a PR or an issue to collaborate. I
also don't have Lua 5.3 and Lua 5.4 code included in the wxlua source
tree, but will consider including it if it's needed to simplify the
binary generation.
Let me know if you run into any issues with it or have any other
feedback. Thank you for all the support and contributions to the
project.
Paul.

Windows handles (HWND) are assigned by Windows when the window or control
is created. No program can set the HWND of a window or control.
The HWND is how Windows identifies each window or control, so *each window
or control must have a unique HWND*. Just as each house or business must
have a unique address to ensure the mail gets to the right place.
By the way, the best way to get an answer to a question is to post the
question on sourceforge. Many people will be not very happy if you are
sending them unsolicited help requests. Posting of sourceforge means you
can carry on a conversation more easily than through email as well.
On Thu, Mar 28, 2019 at 11:55 AM Procházka Lukáš Ing. <LP...@po...> wrote:
> Hello,
>
> I have a third party app which provides the WinAPI HWND (written in C) to
> Lua as a number or as a string, e.g.:
>
> C: HWND hwnd = 0x12345678
> Lua: local hwnd_n = 305419896 -- "number"
> local hwnd_s = "0x12345678" -- "string"
>
> wxLua: How do I obtain/create a Lua 'wxWindow' (or whatever 'wx' object)
> which would "work" with HWND of value of 'hwnd'?
>
> Best regards,
>
> Lukas
>
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Hello,
I have a third party app which provides the WinAPI HWND (written in C) to Lua as a number or as a string, e.g.:
C: HWND hwnd = 0x12345678
Lua: local hwnd_n = 305419896 -- "number"
 local hwnd_s = "0x12345678" -- "string"
wxLua: How do I obtain/create a Lua 'wxWindow' (or whatever 'wx' object) which would "work" with HWND of value of 'hwnd'?
Best regards,
Lukas

Yes, Mike.
I am going to look for the info and get in contact again with you.
When I say "The third column ...give you the key" I mean that there you can
know what class are in wxLua.
I am also a non C-programmer. I am also reading info for programming in
Lua.
See you soon.
*HERNAN CANO MARTINEZ*
Analista de Sistemas
Cel: 300-782.48.44 (sólo llamadas)
WhatsApp: 316-601.12.67 (sólo WhatsApp)
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Hernan,
Thank you for your reply. Yes, I have those links already and they are 
pretty hard to understand with little to no code examples, which is 
truthfully
how I learn programming. I was hoping for more actual tutorials or 
expanded, easy to read, documentation. Not sure what you mean by "This 
means: when you
need to use a wxWidgets class, you must look for it from the 
wxLuaRef.html page and see if it was incorporated. The third column 
called "Wrapped by wxLua"
give you the key."
What key?
Your son's project sounds interesting and I am sorry he passed. I would 
be very interested in your Lide Framework.
Mike
On 2019年03月26日 13:01, Hernan Cano wrote:
> Hi, Mike.
> 
> http://wxlua.sourceforge.net/
> 
> http://wxlua.sourceforge.net/docs/wxlua.html
> 
> http://wxlua.sourceforge.net/docs/wxluaref.html
> 
> With respect to a "no documentation for wxLua and wxWidgets", I
> consider all you need to know is:
> 
> wxLua is a clon of Lua v5.1 specifically compiled to take advantage of
> wxWidgets. This means that all the documentation of wxLua (functions
> to use in wxLua, the reference) is really the documentation of
> wxWidgets.
> 
> Then... in the third link I wrote you in this message [[ wxLuaRef ]]
> you can find the very API that was really incorporated (from
> wxWidgets) in wxLua. This means: when you need to use a wxWidgets
> class, you must look for it from the wxLuaRef.html page and see if it
> was incorporated. The third column called "Wrapped by wxLua" give you
> the key.
> 
> I can share more info with you about this. I would like to guide you
> in understanding wxLua and wxWidgets.
> 
> We can keep in touch.
> 
> HERNAN CANO MARTINEZ
> Analista de Sistemas
> 
> My son made a very intensive study of this same library and he
> developed a "framework" (he called so) for developing "better" in Lua
> using wxWidgets. I can share the "Lide framework" with you and who
> could ask for it. My son went to the sky on past january-30-2019, and
> he puts some info in GitHub and other pages as TheDary. I'll look for
> the info.
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi, Mike.
http://wxlua.sourceforge.net/
http://wxlua.sourceforge.net/docs/wxlua.html
http://wxlua.sourceforge.net/docs/wxluaref.html
With respect to a "no documentation for wxLua and wxWidgets", I consider
all you need to know is:
wxLua is a clon of Lua v5.1 specifically compiled to take advantage of
wxWidgets. This means that all the documentation of wxLua (functions to use
in wxLua, the reference) is really the documentation of wxWidgets.
Then... in the third link I wrote you in this message [[ wxLuaRef ]] you
can find the very API that was really incorporated (from wxWidgets) in
wxLua. This means: when you need to use a wxWidgets class, you must look
for it from the wxLuaRef.html page and see if it was incorporated. The
third column called "Wrapped by wxLua" give you the key.
I can share more info with you about this. I would like to guide you in
understanding wxLua and wxWidgets.
We can keep in touch.
*HERNAN CANO MARTINEZ*
Analista de Sistemas
My son made a very intensive study of this same library and he developed a
"framework" (he called so) for developing "better" in Lua using wxWidgets.
I can share the "Lide framework" with you and who could ask for it. My son
went to the sky on past january-30-2019, and he puts some info in GitHub
and other pages as TheDary. I'll look for the info.

While this is all very old, I am very new to Lua programming and 
specifically wxWidgets/wxLua.
I have everything in place and working, as well as wxFormBuilder and am 
using it (yet more to learn).
I am used to OOP and languages like Visual Basic, Basic, C, Php, HTML, 
CSS, MySQL and more, so Lua
should not really be too hard for me. However, since there is little to 
no documentation for wxLua and
wxWidgets, I am pretty lost. The docs that are available, as has been 
mentioned on other forums, could
literally give you a headache.
I have tried youtube for videos, but most regarding wxFormBuilder are 
for C++ or Python. Due to my needs
I am using Lua 5.1 (yes, I know 5.3 is available but I need 5.1 for 
crypto libraries and wxLua/wxWidgets)
and just need some help. If there are any tutorials or other easier to 
read docs, books, manuals, etc
that would be great.
Specifically, I am trying to save/load and encrypt/decrypt data using 
Lua and sha-256, AES or Blowfish.
I am also trying to simply code the various widgets (buttons, text 
controls, etc) in Lua and having a hard
time. Something as mundane as a Login and registration form that is 
usually very easy to do with a MySQL database
is giving me real grief in Lua.
I have gone through all the wxWidget samples and gleaned a small amount 
of learning from them, but I am not
grasping the overall concept. I have watched Lua tutorials on YouTube 
and it seems overly easy and very basic-like,
but that does not seem to be the case with wxLua and wxWidgets. I DO 
NOT program in C++ and have never been
able to grasp it.
I appreciate any guidance to tech support forums or learning materials.
Thank you.
Mike

Wow! that's complicated!
May I suggest using pre-built wx.so (BTW, no installation needed) from ZBS
<http://studio.zerobrane.com/> or its build script
<https://github.com/pkulchenko/ZeroBraneStudio/blob/master/build/build-linux.sh>
?
Best regards, Ildar.
пт, 26 янв. 2018 г. в 5:25, <wxl...@sp...>:
>
> For Windows, there's a precompiled binary that works out of the box.
> But six month ago, I wanted to release a Linux version of one of my wxLua
> project.
> wxLua is too a tiny project to enter a well maintained package repository,
> so I had to rebuild from source.
> It took me a whole day, from 6 to 22, without even that much pause
> inbetween.
> While I won't doubt more clever folk could do it more easily, for the
> record I felt like sharing how I eventually managed:
>
>
> How to compile wxLua for Linux, as of 27/05/2017:
> Tested under a mostly fresh Linux Mint 17.1 Rebecca
>
> Get some tools:
> Compiler:
> sudo apt-get install gcc
> sudo apt-get install g++
> Source control:
> sudo apt-get install git
> sudo apt-get install svn
> Text editor:
> notepadqq is the closest clone of notepad++ (which is my favorite Windows
> editor):
> sudo add-apt-repository ppa:notepadqq-team/notepadqq
> sudo apt-get update
> sudo apt-get install notepadqq
> Some diffing tool:
> sudo apt-get install meld
>
>
> Get the build dependencies:
> To build lua:
> sudo apt-get install libreadline-dev
> sudo apt-get install libncurses5-dev
> To build wxWidgets
> sudo apt-get install libgtk2.0-dev
> And maybe (but best not to even try "media"):
> sudo apt-get install gstreamer1.0
> sudo apt-get install libgstreamer1.0-dev
> sudo apt-get install libgstreamer-plugins-base1.0-dev
> Prolly not needed, but somebody mentioned them:
> libgconf2-dev
> libgconfmm2.6-devel
>
>
> wxLua already contains source of Lua 5.1 and Lua 5.2,
> but if you want to get Lua source from a more official source:
> download .tar.gz from https://www.lua.org/ftp/
> untargz, and: make linux
> To test Lua:
> cd ./src/lua
> print(_VERSION) -- or whatever Lua command
> os.exit() -- or plain CTRL+C
>
>
> Get and build wxWidgets 3.1.0
> svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk
> wxWidgets-src
> As of now, it's revision 78524, so, the same as:
> svn checkout -r 78524 http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk
> wxWidgets-src
> These other source also exist but I didn't use them
> svn checkout
> http://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRANCH
> wxWidgets-2.8
> git clone https://github.com/wxWidgets/wxWidgets.git
> It's best to build in a subfolder rather than in root:
> cd wxWidgets-src
> mkdir buildgtk
> cd buildgtk
> Build (well, configure) with:
> ../configure --with-gtk --disable-shared --enable-compat28
> --enable-stc --enable-richtext --enable-clipboard --with-libpng=builtin
> --with-zlib=builtin --with-expat=builtin
> To list all possible options:
> ../configure --help
> Do not forget --enable-compat28 that is important for wxLua, or else it
> can't find some function
> Do not forget --with-libpng=builtin or it'll fail on newer Ubuntu that
> don't ship with libpng12.so but libpng16-16.so
> Do not use --enable-monolithic that cause weird issue later when linking
> with wxLua (ex: https://forums.wxwidgets.org/viewtopic.php?t=33364 )
> Do not use --enable-mediactrl, not only it has many dependencies
> (gstreamer), but even they're all installed, there are issues at a later
> stage
> Build (actually build) with:
> sudo make install
> sudo ldconfig
> You can check version with:
> wx-config --version
>
>
> Get and build wxLua:
> svn checkout
> https://wxlua.svn.sourceforge.net/svnroot/wxlua/trunk/wxLua wxLua-src
> As of now, it's revision 252, so, the same as:
> svn checkout -r 252 https://svn.code.sf.net/p/wxlua/svn/trunk/wxLua
> wxLua-src
> There is also a more recent, which I didn't dare to try:
> git clone https://github.com/pkulchenko/wxlua.git
> Make a sym link from /modules/lua-5.1/ into /modules/lua/
> cd modules
> ln -s lua-5.1 lua
> cd ..
> Plain copy the include of lua to wxLua cause it can't find them
> from /modules/lua/src/ to /modules/wxlua so:
> cp modules/lua/src/*.h modules/wxlua/
> In /wxLua-src/build/Makefile_wx-config.in
> Remove media from line 54:
> WXLIBS_NAMES = stc,gl,media,aui,xrc,qa,html,adv,core,xml,net,base
> changed to:
> WXLIBS_NAMES = stc,gl,aui,xrc,qa,html,adv,core,xml,net,base
> Comment the first APPEXTRALIBS and modify the second to remove STC_LIB
> and WXXRC_LIB:
> APPEXTRALIBS := -L$(WXLIB_DIR) $(WXLIB_DIR)/lib$(WXLUA_LIB).a
> $(LUA_LIBS)
> Note: you can see that they are missing by using in that makefile*.in
> stuff like
> $(info WXLIB_DIR=$(WXLIB_DIR))
> $(info WXLUA_LIB=$(WXLUA_LIB))
> $(info STC_LIB=$(STC_LIB))
> $(info WXXRC_LIB=$(WXXRC_LIB))
> $(info LUA_LIBS=$(LUA_LIBS))
> Start compiling (from wxLua-src)
> make -f Makefile.wx-config
> If fails to finds its own libwxlua_*.a
> Well, plain copy them where it looks for them:
> sudo cp lib/*.a /usr/local/lib/
> Retry
> make -f Makefile.wx-config
> It fails.
> Compile wxluafreeze_app specifically, as it's all that really matters:
> make -f Makefile.wx-config wxluafreeze_app
> It fails to find all the .o it needs, with lots of undefined reference to
> wxLuaBinding_wx*_init()
> But it gives us the g++ commandline to build it!
> So, modify it to point it to where they are:
> cd apps/wxluafreeze/
> g++ -o wxLuaFreeze *.o ../../modules/wxbind/src/*.o
> ../../modules/wxlua/debugger/*.o ../../modules/wxlua/debug/*.o
> -L/usr/local/lib -pthread /usr/local/lib/libwx_gtk2u_stc-3.1.a
> /usr/local/lib/libwx_gtk2u_gl-3.1.a /usr/local/lib/libwx_gtk2u_aui-3.1.a
> /usr/local/lib/libwx_gtk2u_xrc-3.1.a /usr/local/lib/libwx_gtk2u_qa-3.1.a
> /usr/local/lib/libwx_baseu_net-3.1.a /usr/local/lib/libwx_gtk2u_html-3.1.a
> /usr/local/lib/libwx_gtk2u_adv-3.1.a /usr/local/lib/libwx_gtk2u_core-3.1.a
> /usr/local/lib/libwx_baseu_xml-3.1.a /usr/local/lib/libwx_baseu-3.1.a
> -lwxscintilla-3.1 -lGL -lGLU -pthread -lgthread-2.0 -lX11 -lXxf86vm -lSM
> -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
> -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig
> -lgobject-2.0 -lglib-2.0 -lfreetype -lpng -lexpat -lwxregexu-3.1
> -lwxtiff-3.1 -lwxjpeg-3.1 -lz -ldl -lm -ldl -Wl,--rpath
> -Wl,/home/bob/wxLua/wxLua-src/lib -L/usr/local/lib
> /usr/local/lib/libwxlua_gtk2u_wxlua-3.1.a ../../lib/liblua.a
> /usr/local/lib/libwxpng-3.1.a
> Hopefully at this point you have just succesfully compiled wxLuaFreeze
> Get the wxLuaFreeze from /wxLua-src/apps/wxlua
> Try it alone
> ./wxLuaFreeze
> Try it with a script:
> ./wxLuaFreeze KPL_vXX.wx.lua
>
> But then when you try with a script appended at the end of wxLuaFreeze
> nothing happens
> To fix that, edit wxluafreeze.cpp to use some wxString::From8BitData(..)
> when creating a wxString from the const char*
>
> Also, newer Ubuntu use libpng16-16 instead of libpng12.so, so to fix that:
> add --with-libpng=builtin to wxWidgets ./configure
> add /usr/local/lib/libwxpng-3.1.a to the g++ compile of wxLuaFreeze
>
>
> When cleaning up, please note that parts of wxWidgets and wxLua are
> installed in /usr/local/lib/
> which cannot be written by regular user.
> To get a root explorer use something like:
> sudo nemo
>
> To verify the shared library used by an executable: ldd ./wxLuaFreeze
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
-- 
Ildar Mulyukov,
child of God
email: ild...@gm...
GoogleTalk: ild...@gm...
blog: http://johan-notes.blogspot.com/

For Windows, there's a precompiled binary that works out of the box.But six month ago, I wanted to release a Linux version of one of my wxLua project.wxLua is too a tiny project to enter a well maintained package repository, so I had to rebuild from source.It took me a whole day, from 6 to 22, without even that much pause inbetween.While I won't doubt more clever folk could do it more easily, for the record I felt like sharing how I eventually managed:
How to compile wxLua for Linux, as of 27/05/2017:Tested under a mostly fresh Linux Mint 17.1 Rebecca
Get some tools:
Compiler:
  sudo apt-get install gcc
  sudo apt-get install g++
Source control:
  sudo apt-get install git
  sudo apt-get install svn
Text editor:
notepadqq is the closest clone of notepad++ (which is my favorite Windows editor):
  sudo add-apt-repository ppa:notepadqq-team/notepadqq
  sudo apt-get update
  sudo apt-get install notepadqq
Some diffing tool:
  sudo apt-get install meld
Get the build dependencies:
To build lua:
  sudo apt-get install libreadline-dev
  sudo apt-get install libncurses5-dev
To build wxWidgets
  sudo apt-get install libgtk2.0-dev
And maybe (but best not to even try "media"):
  sudo apt-get install gstreamer1.0
  sudo apt-get install libgstreamer1.0-dev
  sudo apt-get install libgstreamer-plugins-base1.0-dev
Prolly not needed, but somebody mentioned them:
  libgconf2-dev
  libgconfmm2.6-devel 
wxLua already contains source of Lua 5.1 and Lua 5.2,
but if you want to get Lua source from a more official source:
  download .tar.gz from https://www.lua.org/ftp/
  untargz, and: make linux
To test Lua:
  cd ./src/lua
  print(_VERSION) -- or whatever Lua command
  os.exit() -- or plain CTRL+C
Get and build wxWidgets 3.1.0
  svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets-src
  As of now, it's revision 78524, so, the same as:
  svn checkout -r 78524 http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets-src
These other source also exist but I didn't use them
  svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRANCH wxWidgets-2.8
  git clone https://github.com/wxWidgets/wxWidgets.git
It's best to build in a subfolder rather than in root:
  cd wxWidgets-src
  mkdir buildgtk
  cd buildgtk
Build (well, configure) with:
  ../configure --with-gtk --disable-shared --enable-compat28 --enable-stc --enable-richtext --enable-clipboard --with-libpng=builtin --with-zlib=builtin --with-expat=builtin
To list all possible options:
  ../configure --help
Do not forget --enable-compat28 that is important for wxLua, or else it can't find some function
Do not forget --with-libpng=builtin or it'll fail on newer Ubuntu that don't ship with libpng12.so but libpng16-16.so
Do not use --enable-monolithic that cause weird issue later when linking with wxLua (ex: https://forums.wxwidgets.org/viewtopic.php?t=33364 )
Do not use --enable-mediactrl, not only it has many dependencies (gstreamer), but even they're all installed, there are issues at a later stage
Build (actually build) with:
  sudo make install
  sudo ldconfig
You can check version with:
  wx-config --version
Get and build wxLua:
  svn checkout https://wxlua.svn.sourceforge.net/svnroot/wxlua/trunk/wxLua wxLua-src
As of now, it's revision 252, so, the same as:
  svn checkout -r 252 https://svn.code.sf.net/p/wxlua/svn/trunk/wxLua wxLua-src
There is also a more recent, which I didn't dare to try:
  git clone https://github.com/pkulchenko/wxlua.git
Make a sym link from /modules/lua-5.1/ into /modules/lua/
  cd modules
  ln -s lua-5.1 lua
  cd ..
Plain copy the include of lua to wxLua cause it can't find them
from /modules/lua/src/ to /modules/wxlua so:
  cp modules/lua/src/*.h modules/wxlua/
In /wxLua-src/build/Makefile_wx-config.in
  Remove media from line 54:
    WXLIBS_NAMES = stc,gl,media,aui,xrc,qa,html,adv,core,xml,net,base
    changed to:
    WXLIBS_NAMES = stc,gl,aui,xrc,qa,html,adv,core,xml,net,base
  Comment the first APPEXTRALIBS and modify the second to remove STC_LIB and WXXRC_LIB:
    APPEXTRALIBS := -L$(WXLIB_DIR) $(WXLIB_DIR)/lib$(WXLUA_LIB).a $(LUA_LIBS)
Note: you can see that they are missing by using in that makefile*.in stuff like
  $(info WXLIB_DIR=$(WXLIB_DIR))
  $(info WXLUA_LIB=$(WXLUA_LIB))
  $(info STC_LIB=$(STC_LIB))
  $(info WXXRC_LIB=$(WXXRC_LIB))
  $(info LUA_LIBS=$(LUA_LIBS))
Start compiling (from wxLua-src)
  make -f Makefile.wx-config
If fails to finds its own libwxlua_*.a
Well, plain copy them where it looks for them:
  sudo cp lib/*.a /usr/local/lib/
Retry
  make -f Makefile.wx-config
It fails.
Compile wxluafreeze_app specifically, as it's all that really matters:
  make -f Makefile.wx-config wxluafreeze_app
It fails to find all the .o it needs, with lots of undefined reference to wxLuaBinding_wx*_init()
But it gives us the g++ commandline to build it!
So, modify it to point it to where they are:
  cd apps/wxluafreeze/
  g++ -o wxLuaFreeze *.o ../../modules/wxbind/src/*.o ../../modules/wxlua/debugger/*.o ../../modules/wxlua/debug/*.o -L/usr/local/lib -pthread  /usr/local/lib/libwx_gtk2u_stc-3.1.a /usr/local/lib/libwx_gtk2u_gl-3.1.a /usr/local/lib/libwx_gtk2u_aui-3.1.a /usr/local/lib/libwx_gtk2u_xrc-3.1.a /usr/local/lib/libwx_gtk2u_qa-3.1.a /usr/local/lib/libwx_baseu_net-3.1.a /usr/local/lib/libwx_gtk2u_html-3.1.a /usr/local/lib/libwx_gtk2u_adv-3.1.a /usr/local/lib/libwx_gtk2u_core-3.1.a /usr/local/lib/libwx_baseu_xml-3.1.a /usr/local/lib/libwx_baseu-3.1.a -lwxscintilla-3.1 -lGL -lGLU -pthread -lgthread-2.0 -lX11 -lXxf86vm -lSM -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0 -lglib-2.0 -lfreetype -lpng -lexpat -lwxregexu-3.1 -lwxtiff-3.1 -lwxjpeg-3.1 -lz -ldl -lm -ldl -Wl,--rpath -Wl,/home/bob/wxLua/wxLua-src/lib -L/usr/local/lib /usr/local/lib/libwxlua_gtk2u_wxlua-3.1.a ../../lib/liblua.a /usr/local/lib/libwxpng-3.1.a
Hopefully at this point you have just succesfully compiled wxLuaFreeze
Get the wxLuaFreeze from /wxLua-src/apps/wxlua
Try it alone
  ./wxLuaFreeze
Try it with a script:
  ./wxLuaFreeze KPL_vXX.wx.lua
But then when you try with a script appended at the end of wxLuaFreeze nothing happens
To fix that, edit wxluafreeze.cpp to use some wxString::From8BitData(..) when creating a wxString from the const char*
Also, newer Ubuntu use libpng16-16 instead of libpng12.so, so to fix that:
add --with-libpng=builtin to wxWidgets ./configure
add /usr/local/lib/libwxpng-3.1.a to the g++ compile of wxLuaFreeze
When cleaning up, please note that parts of wxWidgets and wxLua are installed in /usr/local/lib/
which cannot be written by regular user.
To get a root explorer use something like:
  sudo nemo
To verify the shared library used by an executable: ldd ./wxLuaFreeze