Re: Calling/implementing child windows when using pyLBC - specifically then debug issues when events fire thereafter
- From: Jacob Kruger <jacobk@xxxxxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Mon, 19 Sep 2011 15:09:54 +0200
Ok, if I implement calling the sort of child module with it's execution
code in itsself - as opposed to being inside a specific function etc., then
it works fine, but then it comes back to that can't pass data/variables
directly between parent and child windows, since while you can tell it you
want to make use of a global variable in the pseudo child window, they
aren't actually initialised with values from pseudo parent window, and thus
setting a value to one of them, etc., in this case won't send the changed
value back to the pseudo parent.
Also tried specifically implementing LBC layout code within a class
implemented inside the module, since that would also allow me to make
function calls against it, etc., but that also seems to bring up VS.Net's
debugging of a crash of python.exe or something.
Seems if really want to try make use of this will need to in fact use some
or other external means of passing values backwards and forwards, like a
text file, or sqlite3, or something.
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
On Mon, 19 Sep 2011 14:18:25 +0200, Jacob Kruger
<jacobk@xxxxxxxxxxxxxxxxxxxx>
wrote:
> Trying to do something simple using LBC in python where I then
> call/implement my own fully customised child windows, which are in effect
> just normal .py files with their own implementation of LBC in python, but
> where the lbc Dialog is being implemented inside a function, so that I
can
> effectively, include multiple child windows in a single module and get
them
> to display them when I make function calls - partly since they could then
> easily enough return enumerable data structures back to parent window if
> wanted to.
>
> Either way, while they come up, and seem alright, once I then close them,
> pretty much the next event that tries to fire/get triggered in the
initial
> window calls up VS.Net to do a real time debugging on python.exe.
>
> Gonna try maybe only importing the 'child' modules at runtime, and let
them
> implement their use of LBC elemets in their own main loop then, but don't
> really see why that would be such an issue, and, idea would also be to
> maybe do something relatively similar if wanted to still implement
> something like a menu system on main window, and then literally use LBC
to
> render all other sort of child windows easily, but haven't tried this yet
> to see how that would work.
>
> Thoughts?
>
> Stay well
>
> Jacob Kruger
> Blind Biker
> Skype: BlindZA
> '...fate had broken his body, but not his spirit...'
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
--
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
