Re: [Boa Constr] Problems with latest CVS version

[Riaan B. <riaan@e.co.za>]

Hi Gordon, get the latest from CVS to address some of these issues,

Gordon Williams wrote:
> 
> Hi,
> 
> I downloaded Boa yesterday June 18th and I am having a couple of problems
> with errors being created.
> 
> I'm using W2000, python 2.0, wxPython 2.2.5, if that makes any difference.
> 
> 1)    Boa copies some stuff to my wxPython directory bcrtl but this was
> disallowed.  I think it is because they are read-only files.  I changed the
> name of the existing bcrtl directory and then the new stuff was copied
> properly.

I'm not sure how to handle this installing issue (especially on Linux)
I also could not reproduce this by making the files read only.

> 
> 2)  When the designer panel is open and I click on a panel I get the
> following error:
> 
> 10:48:49: ClassLinkPropEdit: :
> <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py, 829>>
> 10:48:49: <C wxButton instance at None> :
> <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py, 829>>
> 10:48:49: not found : <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py,
> 829>>

This has always been there (it was just a print to stdout before)
It is actually partially fixed by 2.3.0 :)

If you staying with 2.2.5, feel free to remove the offending print;
PropertyEditors.py, line 829

> 
> I think that there may be other widgets that also produce this error.

Not that I know of...

> 
> Question:
> Is there a way that I can pass a list to a wxChoice widget (eg. choices=
> mychoices).  I tried this with mychoice both as a module variable (boa
> complained about unkown variable) and as a class variable (defined above def
> _init_utils(self): at the start of the class).  Now all hell has broken
> loose and my source code looks like:

Yeah ugly :(

I cannot reproduce generating repeating code like this so if you can 
still do this with the lastest sources, send me the instructions on how.

Having references to variables outside what is defined in the Designer
is not supported yet. It's a tricky problem.
Just having access to globals does not win you much. Any static data
can be stored in the code. But it would be nice.
If you intend to change the values of globals before constructing
the frame, this is not an approach I want to encourage.

Also there is no natural way to put a variable name into e.g. a 
string property editor or a colour property editor.
Most property editors will therefor need another mode where
variables can be entered.

I've been considering the following, it's similar to what you guessed
should happen, so it's a good sign:
Attributes defined in __init__() above the call to _init_ctrls()
will be available to the Designer.

This still leaves the question of nice property editor integration,
but I will think about this more as I also really want this feature.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net