wxlua-users Mailing List for wxLua

Bugs item #3493936, was opened at 2012年02月25日 02:29
Message generated for change (Tracker Item Submitted) made by jerryjacobs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3493936&group_id=140042
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry Jacobs (jerryjacobs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mac OS X CMake build fails on -fPIC
Initial Comment:
Scanning dependencies of target lua
[ 33%] Building C object modules/lua/CMakeFiles/lua.dir/src/lua.c.o
Linking C executable lua
i686-apple-darwin11-llvm-gcc-4.2: ;-fPIC: No such file or directory
make[2]: *** [modules/lua/lua] Error 1
make[1]: *** [modules/lua/CMakeFiles/lua.dir/all] Error 2
make: *** [all] Error 2
I tried to remove all -fPIC junk from the source tree but could find a way to make it link !
----------------------------------------------------------------------
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3493936&group_id=140042

Finally it came down to how I was adding the column to the list control:
This worked:
 listCtrl:InsertColumn(0, "Test")
which I picked from bindings
compared to what I was doing before was:
 local col = wx.wxListItem()
col:SetId(0)
listCtrl:InsertColumn(0,col)
I don't understand though why though 1 overloaded InserColumn works only in
Windows and not on Linux.
Thanks for leading me in the right direction.
Regards,
Milind
On Tue, Feb 21, 2012 at 1:09 PM, Milind Gupta <mil...@gm...>wrote:
> I tried bindings.wx.lua and that shows the listing fine on the main
> window. I then changed listCtrl in my example from wxListCtrl to wxListView
> and I still did not see anything so I need to look into the differences
> between bindings and the minimal listing I sent earlier. If you have any
> suggestions do let me know.
>
> Thanks,
> Milind
>
>
> On Tue, Feb 21, 2012 at 12:41 PM, John Labenski <jla...@gm...>wrote:
>
>> On Tue, Feb 21, 2012 at 2:26 PM, Milind Gupta <mil...@gm...>
>> wrote:
>> > Hi John,
>> > Thanks for the reply. I created a minimal example (attached
>> and
>> > pasted). This example works fine in windows but doesn't show anything in
>> > Linux. Also another thing I noticed in my original program is that when
>> the
>> > GUI is shown the list Controls in which I have added a lot of elements
>> show
>> > scroll bars also! But no elements are visible.
>>
>> This sounds odd, something very strange is going on. Can you select
>> these hidden items? Is it a matter of having the text the same color
>> as the background? Maybe as a theme setting?
>>
>> When you run the samples/bindings.wx.lua program does it work? You
>> should see a wxListControl (actually a wxListView, but they're the
>> same, the wxListView is derived and has a couple extra methods added)
>> with about 20 items and if you click them you get a new list.
>>
>> I don't have access to a Linux machine right now, but I know that the
>> bindings.wx.lua sample works in RedHat 6, Mandriva 2011, and Fedora 13
>> and 15. I see that it adds items exactly as you do as well.
>>
>> Regards,
>> John
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just 99ドル.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>
>

I tried bindings.wx.lua and that shows the listing fine on the main window.
I then changed listCtrl in my example from wxListCtrl to wxListView and I
still did not see anything so I need to look into the differences between
bindings and the minimal listing I sent earlier. If you have any
suggestions do let me know.
Thanks,
Milind
On Tue, Feb 21, 2012 at 12:41 PM, John Labenski <jla...@gm...> wrote:
> On Tue, Feb 21, 2012 at 2:26 PM, Milind Gupta <mil...@gm...>
> wrote:
> > Hi John,
> > Thanks for the reply. I created a minimal example (attached and
> > pasted). This example works fine in windows but doesn't show anything in
> > Linux. Also another thing I noticed in my original program is that when
> the
> > GUI is shown the list Controls in which I have added a lot of elements
> show
> > scroll bars also! But no elements are visible.
>
> This sounds odd, something very strange is going on. Can you select
> these hidden items? Is it a matter of having the text the same color
> as the background? Maybe as a theme setting?
>
> When you run the samples/bindings.wx.lua program does it work? You
> should see a wxListControl (actually a wxListView, but they're the
> same, the wxListView is derived and has a couple extra methods added)
> with about 20 items and if you click them you get a new list.
>
> I don't have access to a Linux machine right now, but I know that the
> bindings.wx.lua sample works in RedHat 6, Mandriva 2011, and Fedora 13
> and 15. I see that it adds items exactly as you do as well.
>
> Regards,
> John
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just 99ドル.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

On Tue, Feb 21, 2012 at 2:26 PM, Milind Gupta <mil...@gm...> wrote:
> Hi John,
>      Thanks for the reply. I created a minimal example (attached and
> pasted). This example works fine in windows but doesn't show anything in
> Linux. Also another thing I noticed in my original program is that when the
> GUI is shown the list Controls in which I have added a lot of elements show
> scroll bars also! But no elements are visible.
This sounds odd, something very strange is going on. Can you select
these hidden items? Is it a matter of having the text the same color
as the background? Maybe as a theme setting?
When you run the samples/bindings.wx.lua program does it work? You
should see a wxListControl (actually a wxListView, but they're the
same, the wxListView is derived and has a couple extra methods added)
with about 20 items and if you click them you get a new list.
I don't have access to a Linux machine right now, but I know that the
bindings.wx.lua sample works in RedHat 6, Mandriva 2011, and Fedora 13
and 15. I see that it adds items exactly as you do as well.
Regards,
 John

Hi John,
 Thanks for the reply. I created a minimal example (attached and
pasted). This example works fine in windows but doesn't show anything in
Linux. Also another thing I noticed in my original program is that when the
GUI is shown the list Controls in which I have added a lot of elements show
scroll bars also! But no elements are visible.
------------------------------------------------------------------------------------------------------------------------------
-- Load the wxLua module, does nothing if running from wxLua, wxLuaFreeze,
or wxLuaEdit
package.cpath =
package.cpath..";./?.dll;./?.so;../lib/?.so;../lib/vc_dll/?.dll;../lib/bcc_dll/?.dll;../lib/mingw_dll/?.dll;"
require("wx")
frame = nil
-- Create a function to encapulate the code, not necessary, but it makes it
-- easier to debug in some cases.
function main()
 -- create the wxFrame window
 frame = wx.wxFrame( wx.NULL, -- no parent for toplevel
windows
 wx.wxID_ANY, -- don't need a wxWindow ID
 "wxLua Minimal Demo", -- caption on the frame
 wx.wxDefaultPosition, -- let system place the frame
 wx.wxSize(450, 450), -- set the size of the frame
 wx.wxDEFAULT_FRAME_STYLE ) -- use default frame
styles
 local sizer = wx.wxBoxSizer(wx.wxHORIZONTAL)
local listCtrl = wx.wxListCtrl(frame, wx.wxID_ANY, wx.wxDefaultPosition,
wx.wxDefaultSize,bit.bor(wx.wxLC_REPORT,wx.wxLC_NO_HEADER))
-- Add Item
local col = wx.wxListItem()
col:SetId(0)
listCtrl:InsertColumn(0,col)
local newItem = wx.wxListItem()
newItem:SetId(0)
newItem:SetText("Test Item")
listCtrl:InsertItem(newItem)
sizer:Add(listCtrl, 1,
bit.bor(wx.wxALL,wx.wxEXPAND,wx.wxALIGN_CENTER_HORIZONTAL,wx.wxALIGN_CENTER_VERTICAL),
1)
frame:SetSizer(sizer)
sizer:SetSizeHints(frame)
frame:Layout()
 -- show the frame window
 frame:Show(true)
end
main()
-- Call wx.wxGetApp():MainLoop() last to start the wxWidgets event loop,
-- otherwise the wxLua program will exit immediately.
-- Does nothing if running from wxLua, wxLuaFreeze, or wxLuaEdit since the
-- MainLoop is already running or will be started by the C++ program.
wx.wxGetApp():MainLoop()
On Tue, Feb 21, 2012 at 1:42 AM, John Labenski <jla...@gm...> wrote:
> On Tue, Feb 21, 2012 at 3:44 AM, Milind Gupta <mil...@gm...>
> wrote:
> > After digging a bit deeper I find that the items are added to the control
> > since subsequent calls to InsertItem does detect them but they are not
> > visible in the GUI. I tried setting the text foreground color also to
> black
>
> Do you call Freeze() on it before adding the items and forget to call
> Thaw()?
>
> I see that you are skipping every other item since you call
> GetNextItem() twice, but only check the value of it once and more
> dangerously, don't check that you haven't fallen off the end of the
> list after the second call.
>
> You could simply just add a few items where you know they'll be and
> see if that works.
>
> Regards,
> John
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just 99ドル.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

On Tue, Feb 21, 2012 at 3:44 AM, Milind Gupta <mil...@gm...> wrote:
> After digging a bit deeper I find that the items are added to the control
> since subsequent calls to InsertItem does detect them but they are not
> visible in the GUI. I tried setting the text foreground color also to black
Do you call Freeze() on it before adding the items and forget to call Thaw()?
I see that you are skipping every other item since you call
GetNextItem() twice, but only check the value of it once and more
dangerously, don't check that you haven't fallen off the end of the
list after the second call.
You could simply just add a few items where you know they'll be and
see if that works.
Regards,
 John

After digging a bit deeper I find that the items are added to the control
since subsequent calls to InsertItem does detect them but they are not
visible in the GUI. I tried setting the text foreground color also to black
but still nothing. The List Control is created like:
SelList = wx.wxListCtrl(parent, wx.wxID_ANY, wx.wxDefaultPosition,
wx.wxDefaultSize,bit.bor(wx.wxLC_REPORT,wx.wxLC_NO_HEADER))
On Tue, Feb 21, 2012 at 12:30 AM, Milind Gupta <mil...@gm...>wrote:
> Hi,
> I wrote the following code to insert "item" which is a string into
> a wxListCtrl which is ListBox. But at the end no item is added to the List
> Control. It works fine on windows though. Basically it places the new item
> so the list remains sorted and then places the item. At the first run
> itemNum is taken as 0 but there is no element placed. Any ideas why it
> doesn't work in Linux?
>
> Thanks
>
> InsertItem = function(ListBox,Item)
> -- Check if the Item exists in the list control
> local itemNum = -1
> while ListBox:GetNextItem(itemNum) ~= -1 do
> local prevItemNum = itemNum
> itemNum = ListBox:GetNextItem(itemNum)
> local itemText = ListBox:GetItemText(itemNum)
> if itemText == Item then
> return true
> end
> if itemText > Item then
> itemNum = prevItemNum
> break
> end
> end
> -- itemNum contains the item before which to place item
> if itemNum == -1 then
> itemNum = 0
> else
> itemNum = itemNum + 1
> end
> local newItem = wx.wxListItem()
> newItem:SetId(itemNum)
> newItem:SetText(Item)
> ListBox:InsertItem(newItem)
> return true
> end
>

Hi,
 I wrote the following code to insert "item" which is a string into a
wxListCtrl which is ListBox. But at the end no item is added to the List
Control. It works fine on windows though. Basically it places the new item
so the list remains sorted and then places the item. At the first run
itemNum is taken as 0 but there is no element placed. Any ideas why it
doesn't work in Linux?
Thanks
InsertItem = function(ListBox,Item)
-- Check if the Item exists in the list control
local itemNum = -1
while ListBox:GetNextItem(itemNum) ~= -1 do
local prevItemNum = itemNum
itemNum = ListBox:GetNextItem(itemNum)
local itemText = ListBox:GetItemText(itemNum)
if itemText == Item then
return true
end
if itemText > Item then
itemNum = prevItemNum
break
end
end
-- itemNum contains the item before which to place item
if itemNum == -1 then
itemNum = 0
else
itemNum = itemNum + 1
end
local newItem = wx.wxListItem()
newItem:SetId(itemNum)
newItem:SetText(Item)
ListBox:InsertItem(newItem)
return true
end

>> On Thu, Feb 16, 2012 at 12:06 PM, Mike Richards <mri...@gm...>
>>>
>>> function test() is declared in the current scope, and globally as
>>> filterform.test
>>>
>>> After fiddling around for a bit, it looks like wx.wxEvtHandler:Connect
>>> saves upvalues, but not the current function environment (scope), which was
>>> set in the call to module(...)
Mike you're right, I was wrong in my first reply. The environment is
not saved and the global table is always set as the environment of the
Lua event callback function. I haven't thought about this for awhile,
but I can't think of any reason not to save it right now, however that
code dates from over 5 years ago so I don't remember if it was tried
it and it didn't work or what...
Here's what's actually done before your Lua event handler function is
called, where m_luafunc_ref is the reference to the Lua callback
function that's put on the stack.
http://wxlua.svn.sourceforge.net/viewvc/wxlua/trunk/wxLua/modules/wxlua/src/wxlcallb.cpp?revision=36&view=markup
191 	if (wxlState.wxluaR_GetRef(m_luafunc_ref, &wxlua_lreg_refs_key))
192 	{
193 	 wxlState.lua_PushValue(LUA_GLOBALSINDEX);
194 	 if (wxlState.lua_SetFenv(-2) != 0)
195 	 {
196 	 // Don't track the wxEvent since we don't own it and tracking it
197 	 // causes clashes in the object registry table since many can be
198 	 // created and deleted and the mem address is resused by C++.
199 	 wxlState.wxluaT_PushUserDataType(event, event_wxl_type, false);
200 	 wxlState.LuaPCall(1, 0); // one input no returns
>>> When the event function is called, the function environment is reset to
>>> the global scope, so if you want to reference things you declared in the
>>> module scope in the event callback, you have a couple of options:
>>> 1. Declare everything as local, which to me is just good practice.
>>> 2. Use a fully qualified name (e.g. filterform.test())
>>> 3. Wrap all your calls to wx.wxEvtHandler:Connect like this:
>>>
>>> function Connect(evthandler, id, func)
>>>   local environment = getfenv(1)
>>>   evthandler:Connect(id,
>>>     function(event)
>>>       setfenv(1, environment)
>>>       func(event)
>>>     end
>>>   )
>>> end
>>>
>>> [...]
>>>
>>> local button = wx.Button([...])
>>> Connect(button, wx.wxEVT_COMMAND_BUTTON_CLICKED, function(event) end)
>>>
>>> John -- It seems like wx.wxEvtHandler:Connect should do this anyways . .
>>> . that is, save the current function environment, and then apply it before
>>> calling the callback.
I'll have to check a little bit more into 5.2 since get/setfenv are
gone, but it looks like all you do is get/set the _ENV variable to get
the same behavior. For the callback function, we'd set it as an
upvalue to the callback function.
http://www.corsix.org/content/look-lua-52-work3
If it's really that simple then yes, we can save the environment and
not worry about breaking anything in 5.2, though under the hood it
will be implemented differently. If I'm wrong and it can't be made to
work in 5.2, then it should be left as is.
I'm thinking a little out loud here... the pros of the global +
upvalues (current state) is that you always get the same environment
so there's no surprises, which is also a downside when you're in a
module since you're not in what you thought was the global table. The
downside of saving the environment of each Connect() callback is an
extra reference to a Lua table.
I'll look into it.
Regards,
 John

Thanks,
Milind
On Thu, Feb 16, 2012 at 1:53 PM, Mike Richards <mri...@gm...> wrote:
> Milind,
> You could also accomplish the same with a little less typing if you want:
>
> module(...)
> local _M = _M -- save the module table
>
> then in your event handler function it's just setfenv(1, _M)
>
> Mike
>
> On 2/16/2012 4:42 PM, Milind Gupta wrote:
>
> Hi Mike,
> I agree a good practice is to declare things local, only for things
> we want to access from outside unrestricted its easier not to declare them
> local. So anyway what I ended up doing is having the first statement in my
> event handler function as setfenv(1,package.loaded[modname]) where modname
> is the name of the module passed by lua to the module. Since require loads
> the module function there so it just picks it up from there.
>
> Thanks,
> Milind
>
> On Thu, Feb 16, 2012 at 12:06 PM, Mike Richards <mri...@gm...>wrote:
>
>> John and Milind,
>>
>> function test() is declared in the current scope, and globally as
>> filterform.test
>>
>> After fiddling around for a bit, it looks like wx.wxEvtHandler:Connect
>> saves upvalues, but not the current function environment (scope), which was
>> set in the call to module(...)
>> When the event function is called, the function environment is reset to
>> the global scope, so if you want to reference things you declared in the
>> module scope in the event callback, you have a couple of options:
>> 1. Declare everything as local, which to me is just good practice.
>> 2. Use a fully qualified name (e.g. filterform.test())
>> 3. Wrap all your calls to wx.wxEvtHandler:Connect like this:
>>
>> function Connect(evthandler, id, func)
>> local environment = getfenv(1)
>> evthandler:Connect(id,
>> function(event)
>> setfenv(1, environment)
>> func(event)
>> end
>> )
>> end
>>
>> [...]
>>
>> local button = wx.Button([...])
>> Connect(button, wx.wxEVT_COMMAND_BUTTON_CLICKED, function(event) end)
>>
>> John -- It seems like wx.wxEvtHandler:Connect should do this anyways . .
>> . that is, save the current function environment, and then apply it before
>> calling the callback.
>>
>> Mike
>>
>>
>> On 2/16/2012 3:14 AM, Milind Gupta wrote:
>>
>> Hello John,
>> Sorry for the carelessness. Here is a full set with
>> minimal.lua which is the main file to run and the module function is called
>> by the Help->About call back. That is true making test a local function
>> makes it work although I am not totally clear why but if you press the
>> other button 'Clear Task' it will give an error complaining about filter
>> which again is not declared local. Actually declaring local anything in a
>> module only makes it private. Whether it is declared local or not it always
>> resides in the module environment. So even if test or filter are not
>> declared local they should be identified in the module environment. Here is
>> the Programming in Lua Modules and Packages chapter that clarifies it:
>>
>> http://www.inf.puc-rio.br/~roberto/pil2/chapter15.pdf
>>
>> At least that is how I understood it. So I think it should work without
>> being declared local. In your previous email you said that the environment
>> is saved as an upvalue with the execution of Connect. I am not sure how
>> that would be done since the module itself does not know what environment
>> to Global it will be in. Like if you see in minimal I placed it in the
>> environment newPackage and all my functions tables declared in the module
>> i.e. test, filter, etc. are in the table newPackage in the global
>> environment but the module code has no way of knowing that.
>> One last point is that unless its an event callback function normal
>> functions in the module run just fine whether test is local or not. As an
>> example I just added the test() call as the first line in
>> filterFormActivate which is a non event function so when the Help-> About
>> callback calls filterFormActivate, test() just runs fine even though it is
>> not local but now if you press the Select Task button it will say it could
>> not find test().
>>
>>
>> Milind
>>
>>
>> On Wed, Feb 15, 2012 at 3:14 AM, Milind Gupta <milind.gupta@...><milind.gupta@...>wrote:
>> > Hello John,
>> >
>> > thanks for the reply. Here is an example code that does not
>> work
>>
>> Please try to provide enough code to make it run out of the box... I
>> had to add back GUI.initFrameH and rem out the usage of MainSizer to
>> make it even possible to run without error.
>>
>> > (Pasted below and attached the file as well). A function from the
>> main wxlua
>> > application calls filterFormActivate which sets up a simple frame with 2
>> > buttons and one static text and associates the button click to
>> SelTaskPress.
>>
>> I made the help menu callback function of the minimal.wx.lua sample
>> call filterform.filterFormActivate(frame).
>>
>> > But when the button is clicked the test() statement gives an error.
>> If that
>> > is removed then it cannot recognize the frame varaiable in the
>> > wx.wxFrame(frame line after test().
>>
>> Please always include these errors in the future to help diagnose the
>> problem.
>>
>> In order to solve your problem I made test() a local function so that
>> it will be an upvalue of the Connect() function that calls it. Note
>> that the 'frame' that is used in the SelTaskPress() function is the
>> frame from the minimal.wx.lua and not the frame from
>> filterFormActivate().
>>
>> To be honest, I have not done too much with modules and require in Lua
>> since I'm not sure I fully understand its behavior.
>>
>> I just came across this which clears some things up for me. Note the
>> sentence "This means that any global functions are not visible by
>> default, which is why we had to create a local alias to print." This
>> is probably also why making test() local above fixed it. See also
>> package.seeall which might be useful to you.
>> http://www.luafaq.org/#T1.37
>>
>> Hope this helps,
>> John
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>
>>
>>
>> _______________________________________________
>> wxlua-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
>
> _______________________________________________
> wxlua-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

Milind,
You could also accomplish the same with a little less typing if you want:
module(...)
local _M = _M -- save the module table
then in your event handler function it's just setfenv(1, _M)
Mike
On 2/16/2012 4:42 PM, Milind Gupta wrote:
> Hi Mike,
> I agree a good practice is to declare things local, only for 
> things we want to access from outside unrestricted its easier not to 
> declare them local. So anyway what I ended up doing is having the 
> first statement in my event handler function as 
> setfenv(1,package.loaded[modname]) where modname is the name of the 
> module passed by lua to the module. Since require loads the module 
> function there so it just picks it up from there.
>
> Thanks,
> Milind
>
> On Thu, Feb 16, 2012 at 12:06 PM, Mike Richards <mri...@gm... 
> <mailto:mri...@gm...>> wrote:
>
> John and Milind,
>
> function test() is declared in the current scope, and globally as
> filterform.test
>
> After fiddling around for a bit, it looks like
> wx.wxEvtHandler:Connect saves upvalues, but not the current
> function environment (scope), which was set in the call to module(...)
> When the event function is called, the function environment is
> reset to the global scope, so if you want to reference things you
> declared in the module scope in the event callback, you have a
> couple of options:
> 1. Declare everything as local, which to me is just good practice.
> 2. Use a fully qualified name (e.g. filterform.test())
> 3. Wrap all your calls to wx.wxEvtHandler:Connect like this:
>
> function Connect(evthandler, id, func)
> local environment = getfenv(1)
> evthandler:Connect(id,
> function(event)
> setfenv(1, environment)
> func(event)
> end
> )
> end
>
> [...]
>
> local button = wx.Button([...])
> Connect(button, wx.wxEVT_COMMAND_BUTTON_CLICKED, function(event) end)
>
> John -- It seems like wx.wxEvtHandler:Connect should do this
> anyways . . . that is, save the current function environment, and
> then apply it before calling the callback.
>
> Mike
>
>
> On 2/16/2012 3:14 AM, Milind Gupta wrote:
>> Hello John,
>> Sorry for the carelessness. Here is a full set with
>> minimal.lua which is the main file to run and the module function
>> is called by the Help->About call back. That is true making test
>> a local function makes it work although I am not totally clear
>> why but if you press the other button 'Clear Task' it will give
>> an error complaining about filter which again is not declared
>> local. Actually declaring local anything in a module only makes
>> it private. Whether it is declared local or not it always resides
>> in the module environment. So even if test or filter are not
>> declared local they should be identified in the module
>> environment. Here is the Programming in Lua Modules and Packages
>> chapter that clarifies it:
>>
>> http://www.inf.puc-rio.br/~roberto/pil2/chapter15.pdf
>> <http://www.inf.puc-rio.br/%7Eroberto/pil2/chapter15.pdf>
>>
>> At least that is how I understood it. So I think it should work
>> without being declared local. In your previous email you said
>> that the environment is saved as an upvalue with the execution of
>> Connect. I am not sure how that would be done since the module
>> itself does not know what environment to Global it will be in.
>> Like if you see in minimal I placed it in the environment
>> newPackage and all my functions tables declared in the module
>> i.e. test, filter, etc. are in the table newPackage in the global
>> environment but the module code has no way of knowing that.
>> One last point is that unless its an event callback function
>> normal functions in the module run just fine whether test is
>> local or not. As an example I just added the test() call as the
>> first line in filterFormActivate which is a non event function so
>> when the Help-> About callback calls filterFormActivate, test()
>> just runs fine even though it is not local but now if you press
>> the Select Task button it will say it could not find test().
>>
>> Milind
>>
>>
>> On Wed, Feb 15, 2012 at 3:14 AM, Milind Gupta <milind.gupta@...>
>> <mailto:milind.gupta@...> wrote:
>> > Hello John,
>> >
>> > thanks for the reply. Here is an example code that
>> does not work
>>
>> Please try to provide enough code to make it run out of the box... I
>> had to add back GUI.initFrameH and rem out the usage of MainSizer to
>> make it even possible to run without error.
>>
>> > (Pasted below and attached the file as well). A function from
>> the main wxlua
>> > application calls filterFormActivate which sets up a simple
>> frame with 2
>> > buttons and one static text and associates the button click to
>> SelTaskPress.
>>
>> I made the help menu callback function of the minimal.wx.lua sample
>> call filterform.filterFormActivate(frame).
>>
>> > But when the button is clicked the test() statement gives an
>> error. If that
>> > is removed then it cannot recognize the frame varaiable in the
>> > wx.wxFrame(frame line after test().
>>
>> Please always include these errors in the future to help diagnose
>> the problem.
>>
>> In order to solve your problem I made test() a local function so that
>> it will be an upvalue of the Connect() function that calls it. Note
>> that the 'frame' that is used in the SelTaskPress() function is the
>> frame from the minimal.wx.lua and not the frame from
>> filterFormActivate().
>>
>> To be honest, I have not done too much with modules and require
>> in Lua
>> since I'm not sure I fully understand its behavior.
>>
>> I just came across this which clears some things up for me. Note the
>> sentence "This means that any global functions are not visible by
>> default, which is why we had to create a local alias to print." This
>> is probably also why making test() local above fixed it. See also
>> package.seeall which might be useful to you.
>> http://www.luafaq.org/#T1.37
>>
>> Hope this helps,
>> John
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization& Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>
>>
>> _______________________________________________
>> wxlua-users mailing list
>> wxl...@li... <mailto:wxl...@li...>
>> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> <mailto:wxl...@li...>
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
>
>
> ------------------------------------------------------------------------------
> Virtualization& Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi Mike,
 I agree a good practice is to declare things local, only for things
we want to access from outside unrestricted its easier not to declare them
local. So anyway what I ended up doing is having the first statement in my
event handler function as setfenv(1,package.loaded[modname]) where modname
is the name of the module passed by lua to the module. Since require loads
the module function there so it just picks it up from there.
Thanks,
Milind
On Thu, Feb 16, 2012 at 12:06 PM, Mike Richards <mri...@gm...> wrote:
> John and Milind,
>
> function test() is declared in the current scope, and globally as
> filterform.test
>
> After fiddling around for a bit, it looks like wx.wxEvtHandler:Connect
> saves upvalues, but not the current function environment (scope), which was
> set in the call to module(...)
> When the event function is called, the function environment is reset to
> the global scope, so if you want to reference things you declared in the
> module scope in the event callback, you have a couple of options:
> 1. Declare everything as local, which to me is just good practice.
> 2. Use a fully qualified name (e.g. filterform.test())
> 3. Wrap all your calls to wx.wxEvtHandler:Connect like this:
>
> function Connect(evthandler, id, func)
> local environment = getfenv(1)
> evthandler:Connect(id,
> function(event)
> setfenv(1, environment)
> func(event)
> end
> )
> end
>
> [...]
>
> local button = wx.Button([...])
> Connect(button, wx.wxEVT_COMMAND_BUTTON_CLICKED, function(event) end)
>
> John -- It seems like wx.wxEvtHandler:Connect should do this anyways . . .
> that is, save the current function environment, and then apply it before
> calling the callback.
>
> Mike
>
>
> On 2/16/2012 3:14 AM, Milind Gupta wrote:
>
> Hello John,
> Sorry for the carelessness. Here is a full set with minimal.lua
> which is the main file to run and the module function is called by the
> Help->About call back. That is true making test a local function makes it
> work although I am not totally clear why but if you press the other button
> 'Clear Task' it will give an error complaining about filter which again is
> not declared local. Actually declaring local anything in a module only
> makes it private. Whether it is declared local or not it always resides in
> the module environment. So even if test or filter are not declared local
> they should be identified in the module environment. Here is the
> Programming in Lua Modules and Packages chapter that clarifies it:
>
> http://www.inf.puc-rio.br/~roberto/pil2/chapter15.pdf
>
> At least that is how I understood it. So I think it should work without
> being declared local. In your previous email you said that the environment
> is saved as an upvalue with the execution of Connect. I am not sure how
> that would be done since the module itself does not know what environment
> to Global it will be in. Like if you see in minimal I placed it in the
> environment newPackage and all my functions tables declared in the module
> i.e. test, filter, etc. are in the table newPackage in the global
> environment but the module code has no way of knowing that.
> One last point is that unless its an event callback function normal
> functions in the module run just fine whether test is local or not. As an
> example I just added the test() call as the first line in
> filterFormActivate which is a non event function so when the Help-> About
> callback calls filterFormActivate, test() just runs fine even though it is
> not local but now if you press the Select Task button it will say it could
> not find test().
>
>
> Milind
>
>
> On Wed, Feb 15, 2012 at 3:14 AM, Milind Gupta <milind.gupta@...><milind.gupta@...>wrote:
> > Hello John,
> >
> > thanks for the reply. Here is an example code that does not
> work
>
> Please try to provide enough code to make it run out of the box... I
> had to add back GUI.initFrameH and rem out the usage of MainSizer to
> make it even possible to run without error.
>
> > (Pasted below and attached the file as well). A function from the main
> wxlua
> > application calls filterFormActivate which sets up a simple frame with 2
> > buttons and one static text and associates the button click to
> SelTaskPress.
>
> I made the help menu callback function of the minimal.wx.lua sample
> call filterform.filterFormActivate(frame).
>
> > But when the button is clicked the test() statement gives an error. If
> that
> > is removed then it cannot recognize the frame varaiable in the
> > wx.wxFrame(frame line after test().
>
> Please always include these errors in the future to help diagnose the
> problem.
>
> In order to solve your problem I made test() a local function so that
> it will be an upvalue of the Connect() function that calls it. Note
> that the 'frame' that is used in the SelTaskPress() function is the
> frame from the minimal.wx.lua and not the frame from
> filterFormActivate().
>
> To be honest, I have not done too much with modules and require in Lua
> since I'm not sure I fully understand its behavior.
>
> I just came across this which clears some things up for me. Note the
> sentence "This means that any global functions are not visible by
> default, which is why we had to create a local alias to print." This
> is probably also why making test() local above fixed it. See also
> package.seeall which might be useful to you.
> http://www.luafaq.org/#T1.37
>
> Hope this helps,
> John
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
>
> _______________________________________________
> wxlua-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

John and Milind,
function test() is declared in the current scope, and globally as 
filterform.test
After fiddling around for a bit, it looks like wx.wxEvtHandler:Connect 
saves upvalues, but not the current function environment (scope), which 
was set in the call to module(...)
When the event function is called, the function environment is reset to 
the global scope, so if you want to reference things you declared in the 
module scope in the event callback, you have a couple of options:
1. Declare everything as local, which to me is just good practice.
2. Use a fully qualified name (e.g. filterform.test())
3. Wrap all your calls to wx.wxEvtHandler:Connect like this:
function Connect(evthandler, id, func)
 local environment = getfenv(1)
 evthandler:Connect(id,
 function(event)
 setfenv(1, environment)
 func(event)
 end
 )
end
[...]
local button = wx.Button([...])
Connect(button, wx.wxEVT_COMMAND_BUTTON_CLICKED, function(event) end)
John -- It seems like wx.wxEvtHandler:Connect should do this anyways . . 
. that is, save the current function environment, and then apply it 
before calling the callback.
Mike
On 2/16/2012 3:14 AM, Milind Gupta wrote:
> Hello John,
> Sorry for the carelessness. Here is a full set with 
> minimal.lua which is the main file to run and the module function is 
> called by the Help->About call back. That is true making test a local 
> function makes it work although I am not totally clear why but if you 
> press the other button 'Clear Task' it will give an error complaining 
> about filter which again is not declared local. Actually declaring 
> local anything in a module only makes it private. Whether it is 
> declared local or not it always resides in the module environment. So 
> even if test or filter are not declared local they should be 
> identified in the module environment. Here is the Programming in Lua 
> Modules and Packages chapter that clarifies it:
>
> http://www.inf.puc-rio.br/~roberto/pil2/chapter15.pdf 
> <http://www.inf.puc-rio.br/%7Eroberto/pil2/chapter15.pdf>
>
> At least that is how I understood it. So I think it should work 
> without being declared local. In your previous email you said that the 
> environment is saved as an upvalue with the execution of Connect. I am 
> not sure how that would be done since the module itself does not know 
> what environment to Global it will be in. Like if you see in minimal 
> I placed it in the environment newPackage and all my functions tables 
> declared in the module i.e. test, filter, etc. are in the table 
> newPackage in the global environment but the module code has no way of 
> knowing that.
> One last point is that unless its an event callback function 
> normal functions in the module run just fine whether test is local or 
> not. As an example I just added the test() call as the first line in 
> filterFormActivate which is a non event function so when the Help-> 
> About callback calls filterFormActivate, test() just runs fine even 
> though it is not local but now if you press the Select Task button it 
> will say it could not find test().
>
> Milind
>
>
> On Wed, Feb 15, 2012 at 3:14 AM, Milind Gupta <milind.gupta@...> wrote:
> > Hello John,
> >
> > thanks for the reply. Here is an example code that does 
> not work
>
> Please try to provide enough code to make it run out of the box... I
> had to add back GUI.initFrameH and rem out the usage of MainSizer to
> make it even possible to run without error.
>
> > (Pasted below and attached the file as well). A function from the 
> main wxlua
> > application calls filterFormActivate which sets up a simple frame with 2
> > buttons and one static text and associates the button click to 
> SelTaskPress.
>
> I made the help menu callback function of the minimal.wx.lua sample
> call filterform.filterFormActivate(frame).
>
> > But when the button is clicked the test() statement gives an error. 
> If that
> > is removed then it cannot recognize the frame varaiable in the
> > wx.wxFrame(frame line after test().
>
> Please always include these errors in the future to help diagnose the 
> problem.
>
> In order to solve your problem I made test() a local function so that
> it will be an upvalue of the Connect() function that calls it. Note
> that the 'frame' that is used in the SelTaskPress() function is the
> frame from the minimal.wx.lua and not the frame from
> filterFormActivate().
>
> To be honest, I have not done too much with modules and require in Lua
> since I'm not sure I fully understand its behavior.
>
> I just came across this which clears some things up for me. Note the
> sentence "This means that any global functions are not visible by
> default, which is why we had to create a local alias to print." This
> is probably also why making test() local above fixed it. See also
> package.seeall which might be useful to you.
> http://www.luafaq.org/#T1.37
>
> Hope this helps,
> John
>
>
>
> ------------------------------------------------------------------------------
> Virtualization& Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

On Wed, Feb 15, 2012 at 3:14 AM, Milind Gupta <mil...@gm...> wrote:
> Hello John,
>
> thanks for the reply. Here is an example code that does not work
Please try to provide enough code to make it run out of the box... I
had to add back GUI.initFrameH and rem out the usage of MainSizer to
make it even possible to run without error.
> (Pasted below and attached the file as well). A function from the main wxlua
> application calls filterFormActivate which sets up a simple frame with 2
> buttons and one static text and associates the button click to SelTaskPress.
I made the help menu callback function of the minimal.wx.lua sample
call filterform.filterFormActivate(frame).
> But when the button is clicked the test() statement gives an error. If that
> is removed then it cannot recognize the frame varaiable in the
> wx.wxFrame(frame line after test().
Please always include these errors in the future to help diagnose the problem.
In order to solve your problem I made test() a local function so that
it will be an upvalue of the Connect() function that calls it. Note
that the 'frame' that is used in the SelTaskPress() function is the
frame from the minimal.wx.lua and not the frame from
filterFormActivate().
To be honest, I have not done too much with modules and require in Lua
since I'm not sure I fully understand its behavior.
I just came across this which clears some things up for me. Note the
sentence "This means that any global functions are not visible by
default, which is why we had to create a local alias to print." This
is probably also why making test() local above fixed it. See also
package.seeall which might be useful to you.
http://www.luafaq.org/#T1.37
Hope this helps,
 John

On Tue, Feb 14, 2012 at 10:09 PM, Milind Gupta <mil...@gm...> wrote:
> Hi,
>    I wonder if this is a known issue or something intentional. I have
> made a module that creates a frame with some buttons and associates an event
> handling function for the button click, the function resides in the module
> itself. The frame also is visible in the module. Now when the event handler
> is called the event handler function is executed in the global environment
> rather than the module environment hence it is not able to see the variables
> and functions of the module.
>    Does this mean event handler functions cannot be in a module?
It should be able to work and the environment is saved when the
event:Connect() is handled. Upvalues work for sure.
Do you have some simple example code of this for me to try.
Regards,
 John

Hi,
 I wonder if this is a known issue or something intentional. I have
made a module that creates a frame with some buttons and associates an
event handling function for the button click, the function resides in the
module itself. The frame also is visible in the module. Now when the event
handler is called the event handler function is executed in the global
environment rather than the module environment hence it is not able to see
the variables and functions of the module.
 Does this mean event handler functions cannot be in a module?
Thanks,
Milind

On Mon, Jan 2, 2012 at 5:51 AM, fra III <ilt...@fa...> wrote:
> Hello All,
> when i run a lua script using wxLua, either mine that some of the
> examples in distribution, closing application do not exit automatically
> from the Lua interpreter, i.e. after closing main window i have to use
> ctrl-C to stop all. This happens either in terminal that using Scite
> editor.
> Is this normal?
No and I don't see that behaviour here in Fedora or MSW. If you simply run it as
$ wxLua minimal.wx.lua
then it should immediately exit when the minimal's wxFrame is closed.
Does it still happen when you run that sample?
> Also when i require wx the Lua function print is no working anymore
> (seems there is another recent post about this).
This was an unfortunate choice by me and the next version will not do
that when run using require.
A simple fix is to add this code that replaces the wxLua print
function back with the Lua print function.
print_wx = print -- save old print in case you want it...
print = print_lua
> I'm on Ubuntu 10.04 with wxwidget 2.8.12 from repository and
> wxLua from recent (?) git.
wxLua uses SVN now and has never used Git, so I don't know what
version you've got.
http://sourceforge.net/scm/?type=svn&group_id=140042
> Many thanks,
> apologies if stupid question (i'm not a programmer!),
> and Happy New Year (if it's matter for You).
Sorry about the delay and no problem about asking.
Regards,
 John