On 1 Jun 2005 at 9:58, Andrew McDonald wrote:
> The first file, tnfox_python_test.PNG, is the result of simply
> starting and stopping the script. Stopping the script using Alt-C,
> since the windows position is such that the top of the window is not
Yeah that happens here too. I keep meaning to fix it.
> The second file, tnfox_python_test_2.PNG, protocols the starting and
> then clicking once in the list box which resulted in a forced closure
> of the program.
I'm not sure what you mean by forced closure.
You also didn't say what version of TnFOX you were using. I haven't
tested the python bindings since version 0.85.
> I wouldn't at all mind attacking this problem myself but could use
> some guidance regarding the compilation of the python module.
Well, as you probably noticed in the docs, the python bindings are
incomplete. The primary cause for this is the pyste tool whose
AllFromHeader() function doesn't entirely work. Now, this said, I
understand that it works much better now than it used to, so I was
thinking of implementing that finally for v0.86.
If the AllFromHeader() issue were fixed, there would still remain
quite a few bugs (you can see the free() issues yourself) the most
important of which is the dangling FXObject problem whereby you must
currently destroy FXObject's children in *precisely* the order you
created them before deleting their parent or all hell breaks loose.
There is almost certainly a solution here in metaclasses, but it
wasn't going to be something I tackle soon.
This all might seem daunting, but the overwhelming amount of work has
actually been already done! It took me two months of full time coding
to implement those bindings and there is something like two weeks at
most remaining. I merely wanted to get a good idea of how it worked
so I knew its limitations during design of Tn.
Now I'm willing to go fix AllFromHeader() right now actually, but
past that I'm not willing to go fix pyste or the dangling FXObject
children problem at this time. If you are willing to put in at most
around two weeks of developer time to iron out all the bugs, then let
me know and I could start tomorrow.