wxlua-users Mailing List for wxLua

On 6/2/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
> I gather that the binding for the properties is now purely a run time behaviour
> and that the name cannot be documented any more.

Yes, I have still to write some extra functions to look at the
bindings from within lua, but I think that it should be possible to
get the property list from either C++ or lua.

> I have been extracting the information from the documentation to allow my editor
> to suggest the proper name for both properties and methods. I will use only
> method if the properties are not documented any more.

See above.

> Is the resolution of properties expensive in time after it has been resolved?

Not really. The function to run is not found the first time, example
wxSize::GetWidth so "Width" is not found. A string is allocated, the
first 3 chars are set to 'G' 'e' 't' and the property name "Width"
copied into the rest of the string, then the function is looked up a
second time to see if that exists.  It works the same for SetXXX
functions.

So, two function lookups instead of one. However, currently the
lookups linearly iterate through them. I think it should be easy
enough to turn this into a binary search which will make things much
faster. The property notation will be at most 2x slower, but probably
much lower. Previously, the function lookup searched for a property
first and when that failed it looked for a function, so the difference
now is that function calls are given precedence.

> Thank you
>
> Andre
>
> PS: By the way my code is now working again
> (needs more testing always does)

I've committed the changes, could you try again, thanks.
    John Labenski

On 6/2/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
> local findType = wx.wxComboBox(toolBar, ID_ELEMENT_TYPE,  '',
> wx.wxDefaultPosition, wx.wxDefaultSize,  {}, wx.wxCB_READONLY)
>
> finType:SetSelection(0) does not work
>
> error:
> expected a number for parameter 3, but got 'no value'

Oh, this is a little more serious. Previously the function
wxComboBox::SetSelection( int to, int from) was called SetMark (for
selecting text in the combobox), but since I removed the %rename it
hides the base class function SetSelection(int n) whis why you got an
error on param 3 (where it's +1 since param 1 is the "self").

I've made function calls check the base class, wxControlWithItems in
this case, to see if it has a function with the same name. The check
is done only the first time a function is called with the result
cached by storing a pointer to base class method for faster lookup.

> Andre
>
> PS: The new binding is much better then the old one.
> Thanks for this significant improvement.

Thanks. I really appreciate your input.
    John Labenski

On 6/2/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
> wx.wxFileName('aa'):FileExists()  -- makes the program exit
>
> tracing the code it seems to go into an infinite recursion
> also
>
> f=wx.wxFileName('aa')
> f:FileExists()
>
> result in the same problem so this seems to be a different problem
> then the wxdir
> also replacing
>
> f:FileExists()
> by the invalid
> f.FileExists()
>
> makes the program crash instead of reporting an error

Ok, all fixed now. This was a bug in differentiating between a static
and non-static overloaded function with the same name.

Thanks,
    John Labenski

ps. I'm trying to address each problem one by one, so I haven't
committed anything yet.