boa-constructor-users

Re: [Boa Constr] Program Icon

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

Hello Javier,

"Leazen ." wrote:
> 
> I am sorry if this is a stupid question but I can't set the icon (the one at
> the NW corner) of the windows from the IDE though I found a property called
> "icon". I guess I just don't know how to use it.

The property editor for the Icon has not been written yet, sorry.
It should be a simple extension of a normal bitmap property editor.

> 
> Could some one please tell me how to set this property?

add this line in your __init__ method:

self.SetIcon(wxIcon('path/to/icon.ico', wxBITMAP_TYPE_ICO))

> 
> Oh, and can I have the icon in PNG or must it be a .ico?

Must be an .ico file. 
That's why it can't just be set by a normal bitmap property editor.

> 
> Thanks,
>         Javier
>

Re: [Boa Constr] Boa 1.0 alpha Toolbar icons and upgrade of source from previous CVS

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

Hello Lynndon,

"Harnell, Lynndon" wrote:
> 
> Hi there
> 
> The new Boa seems great with a lot of improvements.
> 
> I have noticed however that when inserting toolbar images in PNG format, the
> image displays in the Frame Designer window, but is blank when running the
> program. bmp's work OK, but you lose the transparency properties which is a
> pain.

Are you calling wxInitAllImageHandlers() in your code?

> 
> Also I have tried to run a program constructed with the previous CVS
> version, and get an error message "Namerror: 'wxStaticTextCtrl' is not
> defined". Log file is attached.

This is because wxStaticTextCtrl is not installed on the Palette by 
default. It can be turned on, along with all the other examples
and plugins if you switch on pluginsEnabled under Preferences-General.

>  <<log.txt>>
> Is there an easy way of modifying the code rather than re-building the
> entire frame?

It is not necessary in this case, but yes, you can go through the 
generated source and remove (maybe change) the references to this 
control. At any stage you may open the Designer, if it gives an
error, it should be a clue as to some lingering reference.
If it opens up but gives a warning, you may cancel the session
and fix what the warning was about. At no stage should Boa corrupt 
your code as it rolls back gracefully on errors.

I have not actively used this strategy, but I tried it out a few times
just now and it seems to work well :)

Riaan.

Re: [Boa Constr] ZOA.zexp can't be imported?

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

Hello Hans-Peter,

Hans-Peter Jansen wrote:
> 
> On Tuesday, 5. March 2002 19:48, Riaan Booysen wrote:
> > Hi Brian,
> >
> > Brian Wisti wrote:
> > > Hi all,
> > >
> > > I just installed Boa 0.1.0 yesterday, and I must say that I am _very_
> > > impressed.  This is one awesome development environment, and I can't
> > > wait to see it develop further!
> >
> > Thanks!
> > Which areas would you like to see developing further?
> 
> Let me jump into this question. By now, I'm using boa on a daily basis:
> 
> One of my most missing functions is moving a group of selected objects
> by an numeric offset.

Currently you can move around a group of selected objects in 1 pixel
increments by holding down control and using the cursor keys.
There is a bug with wxAcceleratorTables on wxGTK which breaks this
for you, but it works on Windows.
Try rebinding the keys under Preferences-Key bindings-Designer-Move*

You may also set the Designer grid to a lower granularity for
moving multiple selected objects with higher precision.
See Preferences-General-Designer-dsGridSize.

> 
> BTW: Right now, after selecting multiple objects and deselecting them
> in a designer session, the handles of single selected objects are drawn
> in background color thereafter. See attached screen shot. The first
> control is selected. Disturbing...

This is probably a repaint problem. Try to determine if the tags 
are actually the wrong colour or if they are just not updated properly.

> Source formatting: Breaking long lines into a more editor friendly
> format (say 100 columns).

It's on the todo (properly handling multiple lines)
For me the priority is not that high as I see the generated code almost
as a resource, something you *usually* don't maintain manually.

> 
> I18n: the possibility to wrap all strings in i18n().

Maybe support for the gettext.py convention of using _(string) 
would be simplest (I think this has been suggested before)

However there is a more general issue involved; Giving property editors
more state, and how to manage it through the Inspector.
Already property editors support the additional state of being linked
to special frame attributes.

A more specific solution would be to add a new specialised property 
editor dialog for strings with a checkbox for when the string should
be _(gettext) wrapped. It could even possibly add the gettext import
statement and _ binding when it's checked.

> 
> Riaan, if you can give me some hints & thoughts, where to start,
> I'm going to look into them...
> 
> > HTH,
> > Riaan.
> 
> Cheers,
>   Hans-Peter
> 

Riaan.

Re: [Boa Constr] Bug in menus with Boa v. 0.1.0 with Python 2.2 and wxWindows 2.3.2 on Windows

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

Hello Phillip, 

Yes, unfortunately this is a well known bug.

Phillip David wrote:
<bug snipped> 

> I figured I would try out the latest CVS snapshot to compare against
> 0.1.0, but discovered that the CVS on SourceForge appears to predate the
> 0.1.0 release.

Yes, but not for long I hope.

> 
> Is this the appropriate place to report such bugs?  Was this one already
> known?

Feel free to discuss bugs on the mailing list, but if the web 
interface is up and runnning, first post a report.

> 
> In any event, I'm really enjoying using python, wxPython, wxWindows, and
> Boa-Constructor.  For me, all of this is fairly new, but it really looks
> powerful and useful.

Welcome and enjoy!

> 
> Thanks.
> Phillip
> 

Riaan.

Re: [Boa Constr] wxGrid: A few querys

[Robin D. <ro...@al...>]

>
> Question 1)
> ===========
>
> We have made a demo app that has a panel and on that a wxNotebook and two
> buttons.  One button adds a page and creates a grid on it, the other
deletes
> the selcted page and thus removes the grid with it.
>
> The problem I have with the above senario is memory.  I can create as many
> pages as I wish and thus as many grids but when I delete/remove the pages
> the grids are still floating around in memory even though they're not
> displayed and after a time the application acts like a sponge and my
system
> gets slower and slower.

The C++ Window objects are normally deleted when their parent is
closed/deleted.  Tn the case of wxNotebook calling DeletePage will also
delete the C++ window object while RemovePage will not.  Usually when the
C++ object is deleted the Python object will be too, unless of course if you
are holding extra references to it or there is a circular reference
somewhere.

Try reducing your app to a as small as possible sample that has the same
problem and perhaps you will discover the cause of the problem along the
way.  If not then you have something to share with others so they can help
you track it down.

>
> Question 2)
> ===========
>
> Is it possible to print a wxGrid to a standard printer?  If so some demo
> code would be appreciated so I can perform this function.

I don't think I've seen anything to generically go straight from a grid to
the printer, but perhaps you could dump your grid data to HTML using table
tags and use the wxHtmlEasyPrinting class to print it.

If this won't cut it for you then perhaps you should ask on the
wxPython-users list to see if anybody has some ready made code for you,
since these really aren't Boa questions.

--
Robin Dunn
Software Craftsman
ro...@Al...       Java give you jitters?
http://wxPython.org      Relax with wxPython!

[Boa Constr] wxGrid: A few querys

[Tim B. <td...@mc...>]

Hello all,

The following questions will probably, to some of you, be simple and
straight forward.

Unfortunately this is a very new area to me and my collegues and we could do
with some help.

Question 1)
===========

We have made a demo app that has a panel and on that a wxNotebook and two
buttons.  One button adds a page and creates a grid on it, the other deletes
the selcted page and thus removes the grid with it.

The problem I have with the above senario is memory.  I can create as many
pages as I wish and thus as many grids but when I delete/remove the pages
the grids are still floating around in memory even though they're not
displayed and after a time the application acts like a sponge and my system
gets slower and slower.

I have tried deleting the pointer I've got using the 'del' command but this
doesn't seem to work so I looked at the wxGrid deconstructor.  Unfortunately
although I have used deconstructors very breifly in C++ I lack the knowledge
or the syntax to do this in python.  Therefore, help!?

Question 2)
===========

Is it possible to print a wxGrid to a standard printer?  If so some demo
code would be appreciated so I can perform this function.


I would be really grateful for help in this matter as we have tried
everything I can no longer continue to develope our app.

Regards

Tim Bailey
td...@mc...;td-...@bl...

Re: [Boa Constr] Boa 1.0 alpha Toolbar icons and upgrade of source from previous C VS

[Hans-Peter J. <hp...@ur...>]

On Thursday, 7. March 2002 00:40, Harnell, Lynndon wrote:
> Hi there
>
> The new Boa seems great with a lot of improvements.
>
> I have noticed however that when inserting toolbar images in PNG format,
> the image displays in the Frame Designer window, but is blank when running
> the program. bmp's work OK, but you lose the transparency properties which
> is a pain.

At least within wxGTK, this is fine here.

Did you call wxInitAllImageHandlers() in OnInit of your wxApp instance?

> Also I have tried to run a program constructed with the previous CVS
> version, and get an error message "Namerror: 'wxStaticTextCtrl' is not
> defined". Log file is attached.
>  <<log.txt>>
> Is there an easy way of modifying the code rather than re-building the
> entire frame?
>
> Cheers
>
> Lynndon Harnell
> Lyn...@up...

Cheers,
  Hans-Peter

[Boa Constr] Boa 1.0 alpha Toolbar icons and upgrade of source from previous C VS

[Harnell, L. <Lyn...@up...>]

Hi there

The new Boa seems great with a lot of improvements.

I have noticed however that when inserting toolbar images in PNG format, the
image displays in the Frame Designer window, but is blank when running the
program. bmp's work OK, but you lose the transparency properties which is a
pain.

Also I have tried to run a program constructed with the previous CVS
version, and get an error message "Namerror: 'wxStaticTextCtrl' is not
defined". Log file is attached.
 <<log.txt>> 
Is there an easy way of modifying the code rather than re-building the
entire frame?

Cheers

Lynndon Harnell
Lyn...@up... 

[Boa Constr] Program Icon

[Leazen . <le...@ho...>]

I am sorry if this is a stupid question but I can't set the icon (the one at 
the NW corner) of the windows from the IDE though I found a property called 
"icon". I guess I just don't know how to use it.

Could some one please tell me how to set this property?

Oh, and can I have the icon in PNG or must it be a .ico?


Thanks,
        Javier


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

Re: [Boa Constr] ZOA.zexp can't be imported?

[Hans-Peter J. <hp...@ur...>]

On Tuesday, 5. March 2002 19:48, Riaan Booysen wrote:
> Hi Brian,
>
> Brian Wisti wrote:
> > Hi all,
> >
> > I just installed Boa 0.1.0 yesterday, and I must say that I am _very_
> > impressed.  This is one awesome development environment, and I can't
> > wait to see it develop further!
>
> Thanks!
> Which areas would you like to see developing further?

Let me jump into this question. By now, I'm using boa on a daily basis:

One of my most missing functions is moving a group of selected objects
by an numeric offset. 

BTW: Right now, after selecting multiple objects and deselecting them
in a designer session, the handles of single selected objects are drawn 
in background color thereafter. See attached screen shot. The first
control is selected. Disturbing... 

Source formatting: Breaking long lines into a more editor friendly
format (say 100 columns).

I18n: the possibility to wrap all strings in i18n(). 

Riaan, if you can give me some hints & thoughts, where to start, 
I'm going to look into them...

> HTH,
> Riaan.

Cheers,
  Hans-Peter

[Boa Constr] Bug in menus with Boa v. 0.1.0 with Python 2.2 and wxWindows 2.3.2 on Windows

[Phillip D. <ph...@so...>]

I just found this list when I was looking for somewhere to send this 
bug.  The rest of sourceforge is down, but the mail lists are apparently 
still up.  I apologize if I'm reporting a known bug here, but since I 
have no way to access the archives, here goes.

When I tried to add a menu to a new project, I received an error 
(passing a MenuDTC item where a CollectionDTC item was expected).  I was 
able to trace it down to the file Companions/UtilCompanions.py.  It 
appears that the class MenuDTC should inherit from CollectionDTC as it 
attempts to invoke methods from that class.  It currently inherits from 
MenuConstr and UtilityDTC, but not from CollectionDTC.  I tried three 
things before I hit on what seemed like the correct solution.  First, I 
tried making UtilityDTC inherit from CollectionDTC.  I had to move it 
physically in its file, and I just wasn't satisfied that this was a good 
solution.  So I tried changing MenuDTC to inherit from CollectionDTC 
instead of from UtilityDTC.  However, I was then missing the methods 
defined in UtilityDTC.  So I made the attempt to inherit from both 
UtilityDTC and CollectionDTC.  When I added CollectionDTC to the end of 
the list of classes it inherits from, suddenly the error messages I had 
been receiving when attempting to add menus went away, and the menus had 
an item property that could be set to a collection.  This works the same 
way as my Python 2.1/Linux version already worked.

I figured I would try out the latest CVS snapshot to compare against 
0.1.0, but discovered that the CVS on SourceForge appears to predate the 
0.1.0 release.

Is this the appropriate place to report such bugs?  Was this one already 
known?

In any event, I'm really enjoying using python, wxPython, wxWindows, and 
Boa-Constructor.  For me, all of this is fairly new, but it really looks 
powerful and useful.

Thanks.
Phillip

Re: [Boa Constr] ZOA.zexp can't be imported?

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

Hello Brian,

Brian Wisti wrote:
> I do have one question, though.  Two, maybe.
> 
> How can I work within Zope Versions from Boa?  Selecting one of my
> Versions in the Explorer View just shows a mostly empty window
> (containing only the '..' link) in the right hand pane.

There is no support for versions currently. As it complicates things
a bit I've postponed adding support fo them.

> 
> The second question:  Are there any documentation resources for using
> Boa's Zope interface?

You should read: Docs/boa/apphelp/Zope.html
but it is incomplete and a bit out of date (Boa does not use FTP
anymore!)

The Explorer interface to Zope in Boa tries to be simple and 
consistent. As it mirrors Zope functionality, usually the Zope docs 
should apply.

Specific support have to be added for every Product you 
want to use through the Explorer interface. Unhandled products/objects 
are simply displayed as an icon with a question mark.
See the Zope Palette page for all the supported Products.

> 
> I'm going to go back to my coffee and Zope now.  Thanks for your time
> and energy!

Best of luck to you!

Riaan.

Re: [Boa Constr] ZOA.zexp can't be imported?

[Brian W. <br...@co...>]

Hi Riaan,

Thank you for the warm welcome!

> Thanks!
> Which areas would you like to see developing further? 

At this point,  I am concentrating on Zope development, so anything 
that enhances the Zope interface would be more than welcome.  More 
documentation is always nice, but I imagine that a lot of things can 
change between now and a 1.0 version. I'm still exploring Boa, so I 
don't know enough to be able to tell what's lacking or what needs 
improvement.

> Yes this is what you should do. I not sure why your import failed, but
> traceback mentions Products. Did you try to import it into the
> Products folder? If so, this is wrong. It's not a Product, it's a
> simple folder object containing other folders and python scripts. You
> must import it in your Zope root folder.

Ok, I'm _really_ embarassed right now.  Robert Boulanger tried to 
help me out off-list, but it turned out that my mistake was a simple 
one.  I'm new to Zope (I'm new to everything, aren't I?), and was 
attempting to import zoa.zexp into the Product Management folder.  
That produced nothing but trouble, as I'm sure you can imagine.  As 
soon as I imported into the root folder instead, everything worked 
like a charm.

I do have one question, though.  Two, maybe.  

How can I work within Zope Versions from Boa?  Selecting one of my 
Versions in the Explorer View just shows a mostly empty window 
(containing only the '..' link) in the right hand pane.

The second question:  Are there any documentation resources for using 
Boa's Zope interface?

I'm going to go back to my coffee and Zope now.  Thanks for your time 
and energy!

Later,
Brian

--
Brian Wisti 
br...@co...
http://www.coolnamehere.com/

Re: [Boa Constr] ZOA.zexp can't be imported?

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

Hi Brian,

Brian Wisti wrote:
> 
> Hi all,
> 
> I just installed Boa 0.1.0 yesterday, and I must say that I am _very_
> impressed.  This is one awesome development environment, and I can't
> wait to see it develop further!

Thanks!
Which areas would you like to see developing further? 

> 
> There is, however, one tiny problem.  I'm trying to set Boa up for
> working with my Zope pages, and wasn't able to get past the "import
> ZOA" error message.  Eventually the words connected together in my
> head, and I placed the zoa.zexp file into Zope's import directory.
> The thing is, import doesn't want to work.  I'll copy and paste the
> respective error message here.

Yes this is what you should do. I not sure why your import failed,
but traceback mentions Products. Did you try to import it into the 
Products folder? If so, this is wrong. It's not a Product, it's a 
simple folder object containing other folders and python scripts. 
You must import it in your Zope root folder.

BTW, the Zope side support used to be just the one Python script 
called ZOA that you read about in the archives, this was refactored 
into the folders and scripts described above. 
It used to be automatically installed, but I have not yet updated 
the code to handle multiple Zope object installs. So it is an
import for now.

HTH, 
Riaan.

[Boa Constr] ZOA.zexp can't be imported?

[Brian W. <br...@co...>]

Hi all,

I just installed Boa 0.1.0 yesterday, and I must say that I am _very_ 
impressed.  This is one awesome development environment, and I can't 
wait to see it develop further!

There is, however, one tiny problem.  I'm trying to set Boa up for 
working with my Zope pages, and wasn't able to get past the "import 
ZOA" error message.  Eventually the words connected together in my 
head, and I placed the zoa.zexp file into Zope's import directory.  
The thing is, import doesn't want to work.  I'll copy and paste the 
respective error message here.

-----
The object zoa does not support this operation


Traceback (innermost last):
  File D:\COOLNA~1\lib\python\ZPublisher\Publish.py, line 223, in 
publish_module
  File D:\COOLNA~1\lib\python\ZPublisher\Publish.py, line 187, in 
publish
  File D:\COOLNA~1\lib\python\Zope\__init__.py, line 226, in 
zpublisher_exception_hook
    (Object: Products)
  File D:\COOLNA~1\lib\python\ZPublisher\Publish.py, line 171, in 
publish
  File D:\COOLNA~1\lib\python\ZPublisher\mapply.py, line 160, in 
mapply
    (Object: manage_importObject)
  File D:\COOLNA~1\lib\python\ZPublisher\Publish.py, line 112, in 
call_object
    (Object: manage_importObject)
  File D:\COOLNA~1\lib\python\OFS\ObjectManager.py, line 586, in 
manage_importObject
    (Object: Products)
  File D:\COOLNA~1\lib\python\OFS\CopySupport.py, line 444, in 
_verifyObjectPaste
    (Object: Products)
Copy Error: (see above)
-----

I was able to find some references to ZOA and Zope while digging 
around in the mailing list archives, with the most straightforward 
advice being to copy the contents of ZopeLib/ZOA.py into a new Python 
Script object within Zope.  Okay, new problem.  I can't find 
ZopeLib/ZOA.py!  zoa.zexp is still sitting there smirking at me, but 
the python file is nowhere to be found.

Hopefully somebody can help me with the second problem, at least.  
The first might take a little longer to sort out, though, so I'll 
just share my config information and cross my fingers.

OS: Windows 2000
Zope: (Zope 2.4.3 (binary release, python 2.1, win32-x86), python 
2.1.0, win32)
Boa: v0.1.0-alpha

Boa is installed from the windows .EXE download file (but I did 
download the source bundle last night in my futile quest for zoa.py)

If anybody can offer me some patient hand-holding through this, I 
will be most grateful!  Meanwhile, keep up the good work on this 
fantastic app!

Thanks,
Brian Wisti--
Brian Wisti 
br...@co...
http://www.coolnamehere.com/

Re: [Boa Constr] boa app runtime config problem

[Hans-Peter J. <hp...@ur...>]

On Monday, 25. February 2002 18:29, Riaan Booysen wrote:
> Hi Hans-Peter,
>
> (You may ignore this little lecture, as I wrote it before I found the
>  bug in Boa. I'm not going to delete it as someone might still learn
>  something from it. You are using special frame attributes correctly
>  except for the one warning printed along with the error, see below)

Fine with me. One starting with boa cannot read it enough times ;-)

> The important thing to understand with "frame attributes" it that
> there are two behaviours, design-time and run-time:
>
> For design-time, you have to assign a "simple values" like ints or
> strings. Run-time values can be any Python expression evaluating to
> a simple type.
>
> The first time the attribute is assigned will be used at design-time,
> the last time it's assigned will be used at run-time.
>
> You are getting a printed message
>
> > 00:53:13:  config.Config()
> > 00:53:13: name 'config' is not defined
>
> because the line:
> >         self.cfg = config.Config()
>
> is being read as a design-time special frame attribute. You have 2
> choices; either use a local variable between __init__ and
> self._init_ctrls:
>
> e.g.
>           cfg = config.Config()
>
> and then after self._init_ctrls
>
>           self.cfg = cfg
>
> or you can define a design-time None value:
>
>          self.cfg = None
>          self.cfg = config.Config()
>
> You are getting the KeyError : MainSplit because of a bug in Boa.
> Behind the scenes there is a difference between normal property
> values and properties which link up to other controls by name.
> Linking properties (like SplitHorizontally) currently do not handle
> special frame attributes, I'll fix this as soon as possible.

Cool. I'm eagerly awaiting cvs updated:) Please give us a note...

> Hans-Peter Jansen wrote:
> > No matter how I instanciate my config class, I get this key error.
> > Any ideas?
>
> Bug in boa as explained above, as a workaround, leave the 3rd argument
> to SplitHorizontally a simple integer and manually call
>
> self.mainSplitter.SetSashPosition(self.MainSplit)
>
> after self._init_ctrls()

Yup. That's what I'm doing now and it's working well. In fact, I've 
delayed screen layouting into OnIdle for some unknown reason. This 
caused the screen funnies... 
 
> > Also, I would like to pass my config instance to my subclasses in the
> > constructor. The docs say, this is a nono, because it's neither a
> > simple nor a wxPython type.
>
> I'm assuming you are talking about the custom classes feature.
> Correct. You can't, sorry. Not because of what the type the value is,
> but because then the constructor's signature would be different
> from the wxPython base class, which is the nono.
>
> > I workaround this with a Config method in the subclass, but again:
> > Parameter, which modify appearance have to be handled manually and
> > disturb screen appearance on start up (gets drawn with design time
> > values, but modified quickly thereafter)
>
> Yes that is a drawback.
> Can't you wait and only show the frame after everything has been
> initialised properly

Well, yes. You're right. I begin to understand, what constraints boa
have to handle behind the scenes.

One of the most annoying habbits of boa (under wxGTK) are focus related
(I believe). After working on some menu/toolbar attributs, I have to 
close it, and select some other widget before posting, otherwise boa
crashes (the patch for the menu bug is applied).

If you need a more detailed investigation, I can make a gdb bt for you,
but I tend to believe, it wont help much, does it?

Cheers,
  Hans-Peter

Re: [Boa Constr] boa app runtime config problem

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

Hi Hans-Peter,

(You may ignore this little lecture, as I wrote it before I found the
 bug in Boa. I'm not going to delete it as someone might still learn 
 something from it. You are using special frame attributes correctly 
 except for the one warning printed along with the error, see below)

The important thing to understand with "frame attributes" it that 
there are two behaviours, design-time and run-time:

For design-time, you have to assign a "simple values" like ints or 
strings. Run-time values can be any Python expression evaluating to
a simple type.

The first time the attribute is assigned will be used at design-time,
the last time it's assigned will be used at run-time.

You are getting a printed message 

> 00:53:13:  config.Config()
> 00:53:13: name 'config' is not defined

because the line:

>         self.cfg = config.Config()

is being read as a design-time special frame attribute. You have 2 
choices; either use a local variable between __init__ and 
self._init_ctrls:

e.g.
          cfg = config.Config()

and then after self._init_ctrls

          self.cfg = cfg

or you can define a design-time None value:

         self.cfg = None
         self.cfg = config.Config()

You are getting the KeyError : MainSplit because of a bug in Boa.
Behind the scenes there is a difference between normal property 
values and properties which link up to other controls by name.
Linking properties (like SplitHorizontally) currently do not handle 
special frame attributes, I'll fix this as soon as possible.

Hans-Peter Jansen wrote:
> No matter how I instanciate my config class, I get this key error.
> Any ideas?

Bug in boa as explained above, as a workaround, leave the 3rd argument
to SplitHorizontally a simple integer and manually call 

self.mainSplitter.SetSashPosition(self.MainSplit)

after self._init_ctrls()

> 
> Also, I would like to pass my config instance to my subclasses in the
> constructor. The docs say, this is a nono, because it's neither a
> simple nor a wxPython type.

I'm assuming you are talking about the custom classes feature.
Correct. You can't, sorry. Not because of what the type the value is,
but because then the constructor's signature would be different
from the wxPython base class, which is the nono.

> 
> I workaround this with a Config method in the subclass, but again:
> Parameter, which modify appearance have to be handled manually and
> disturb screen appearance on start up (gets drawn with design time
> values, but modified quickly thereafter)

Yes that is a drawback.
Can't you wait and only show the frame after everything has been
initialised properly?

> 
> Any help on this topic is greatly appreciated.
> 
> Cheers,
>   Hans-Peter
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> https://lists.sourceforge.net/lists/listinfo/boa-constructor-users

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

[Boa Constr] boa app runtime config problem

[Hans-Peter J. <hp...@ur...>]

Hi Riaan et al.,

following the docs on "Special frame attributs", I try to
control my layouts this way (on the main frame):

[...]
import config
[...]

class MainUI(wxFrame):
    _custom_classes = {'wxScrolledWindow': ['FaxView', 'wxScrolledWindow'],
                                           'wxPanel': ['FaxList', 'wxPanel']}
    [...]

    def _init_ctrls(self, prnt):
	[...]
        self.mainSplitter.SplitHorizontally(self.listSplitter, 
		self.viewSplitter, self.MainSplit)
	[...]

    def __init__(self, parent):
        self.initdone = false
        self.minPaneSize = 0	# fine
        self.SashSize = 5	# fine
	self.MainSplit = 180	# design time value
        self.cfg = config.Config()
        self.cfg.load()
	self.MainSplit = self.cfg.MainSplit # run time value
        self._init_ctrls(parent)
	[...]

but this results in KeyError: MainSplit during Designer launch:
00:53:13:  config.Config()                                                                
00:53:13: name 'config' is not defined                                                    
00:53:14:     KeyError: MainSplitTraceback (most recent call last):                       
00:53:14:     KeyError: MainSplit  File "Controllers.py", line 778, in OnDesigner         
00:53:14:     self.showDesigner()
                                                        
00:53:14:       File "Controllers.py", line 830, in showDesigner                          
00:53:14:     designer.refreshCtrl()
                                                     
00:53:14:       File "Views/Designer.py", line 351, in refreshCtrl                        
00:53:14:     self.finaliseDepLinks(depLnks)
                                             
00:53:14:       File "Views/InspectableViews.py", line 329, in finaliseDepLinks           
00:53:14:     self.applyDepsForCtrl(ctrlName, depLinks)
                                  
00:53:14:       File "Views/InspectableViews.py", line 303, in applyDepsForCtrl           
00:53:14:     refs.append(self.objects[Utils.ctrlNameFromSrcRef(param)][1])
              
00:53:14:     KeyError: MainSplit                                                         

No matter how I instanciate my config class, I get this key error. 
Any ideas?

Also, I would like to pass my config instance to my subclasses in the
constructor. The docs say, this is a nono, because it's neither a 
simple nor a wxPython type. 

I workaround this with a Config method in the subclass, but again:
Parameter, which modify appearance have to be handled manually and
disturb screen appearance on start up (gets drawn with design time
values, but modified quickly thereafter)

Any help on this topic is greatly appreciated.

Cheers,
  Hans-Peter

[Boa Constr] (no subject)

[<leb...@ya...>]

 
 

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Re: [Boa Constr] Bug or configuration problem

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

Hi Joerg,

Joerg Hackenberg wrote:
> 
> Dear all,
> 
> I am running Python 2.1, wxPython 2.3.2 and Boa 0.1.0-alpha from
> SourceForge download page.
> 
> I have found that there is a missing mouse event in the Evts section of
> the Inspector when run on a wxListCtrl.
> 
> There is no entry for a RIGHT_DOWN event. Is this by purpose? The event
> is existing in wxPython and I Connect it manually to the event handler
> at the moment.
> 
> Is this a configuration problem or a bug in the inspector code?

Bug in the Boa event definition code. Thanks for the catch.

In the Companions.EventCollections.EventCategories dictionary, add
                EVT_RIGHT_DOWN,
to the 'MouseEvent' tuple (I added it at line 173)

> 
> Joerg
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> https://lists.sourceforge.net/lists/listinfo/boa-constructor-users

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

[Boa Constr] Bug or configuration problem

[Joerg H. <hac...@lf...>]

Dear all,

I am running Python 2.1, wxPython 2.3.2 and Boa 0.1.0-alpha from
SourceForge download page.

I have found that there is a missing mouse event in the Evts section of
the Inspector when run on a wxListCtrl.

There is no entry for a RIGHT_DOWN event. Is this by purpose? The event
is existing in wxPython and I Connect it manually to the event handler
at the moment.

Is this a configuration problem or a bug in the inspector code?

Joerg

Re: [Boa Constr] [tiny patch] one liner to limit Palette size

[Hans-Peter J. <hp...@ur...>]

On Tuesday, 5. February 2002 18:43, Riaan Booysen wrote:
> Hi Hans-Peter,
>
> Hans-Peter Jansen wrote:
> > Hi Riaan et al.,
> >
> > my first tiny modification to Boa is limiting the size of Palette to not
> > waste valuable screen space, but it's uniformity/ergonomic tradeoff.
>
> Sorry, I don't really like it ;)

I wouldn't have liked it, if I were you ;-)

> Because you are not the first person to be unsatisfied with the window
> layout, I've now added options to Boa so that you can save/load or
> restore default top level window dimensions. This aught to keep
> everyone happy.

which is obviously the best approach. 

> > Thus I would vote to just include the patchfile under Contributions.
> > If nobody objects, I will also upload it in the sf patch section.
> >
> > Cheers,
> >   Hans-Peter
> >

Cheers,
  Hans-Peter

Re: [Boa Constr] first impressions of Boa 0.1.0

[Hans-Peter J. <hp...@ur...>]

On Tuesday, 5. February 2002 18:42, Riaan Booysen wrote:
> Hello Hans-Peter,
>
[...]
> >
> > Next, I configured boa to my needs. I discovered, that boa uses DOS
> > linebreaks :-( Fortunately I found the autoReindent option, which fixed
> > this for me :-)
>
> I plan to address this with the next release.

Nice..

> > To fulfil my basic basic code form needs, I would like to see an option
> > to use tabs for indention. I found some corresponding STC options, but
> > they don't affect code generation and lead to indention errors, when
> > activated  :-(
>
> I'll look into this.
>
> > Some random findings:
> >  - X clipboard doesn't work in the editor (at least). :-(((
>
> I use wxPython's wxClipboard, it works for me. Did you try from
> the right-click menu in the Designer, or did you try some special
> keystroke?

All of them... I often select some strings somewhere (xterms, vi sessions).
The most X-like behavior have wxTextCtrls: if you select text there with
the mouse, it gets propagated to the X clipboard. Sellections in the editor
gets never there, but are available after Ctrl-C in other edit sessions or
wxTextCtrls. This is disturbing: to quote some examples (see font problem, 
below), I've to use some other tool :-( Really bad is: in the html help 
window, text isn't selectable, and you can only copy the whole help page.

> >  - when editing a string in Designer->Inspector, <Return> doesn't stop
> > that, and posting will loose it's modified content. I need to select
> > another prop to get the former prop modified.
>
> <Return> is supposed to post, but I'm still having problems with
> wxAcceleratorTable under wxGTK :(
>
> >  - Setting font properties in Designer works as expected, but font face
> > gets lost on runtime.
>
> Does the generated source dissapear, or does it not have an effect at
> runtime?

The latter:

self.staticText1 = wxStaticText(id = wxID_WXFRAME1STATICTEXT1, label = 
'Erster Test', name = 'staticText1', parent = self, pos = wxPoint(16, 24), 
size = wxSize(102, 27), style = 2)
self.staticText1.SetFont(wxFont(20, wxSWISS, wxNORMAL, wxNORMAL, false, 
'aachen bt'))

Robin, does using different fonts require a special init? (like images)

> >  - posting buttons doesn't allways work. Closing frame helps.
>
> How do you post a button?
> Only the whole session is posted or canceled.

Sorry for beeing too vague, read: posting designer sessions ... 
closing designer window helps.

> >  - grayout (aka. blueout) results in ramdom char coloring (looks very
> > strange)
>
> This should be off by default on wxGTK.
>
> >  - Modifying MajorDimension in RadioBoxes results in crash on post.
>
> I'll look into it.
>
> >  - Setting wxRA_SPECIFY_ROWS on them is ignored.
>
> Remember when setting constructor properties, the control (or the Frame)
> have to be recreated before the changes take effect (as constructors
> are only called at creation)
>
> > Some future thoughts:
> >  - STC background coloring of 'danger' and 'good' zones (It took me a
> > couple of times to find the proper place where self.timer1.Start(500)
> > didn't get lost after designer sessions)
>
> This is noted in a few place in the help files, please read thru them.
> Quick rule: Leave _init_* methods alone!

I red them. I wouldn't had come so far without. It's just an idea.

> >  - Real i18n support
>
> Yip, I am planning some, for now see Examples/il8n.py

I have, and that was the reason for writing this.

AFAICS, it takes some initialisation stuff, and enclosing strings with 
i18n(). I would vote for a new wxI18nApp model.

> >  - Some grid helpers (generic database interface)
> >
> > Last thing points you in the direction, I have to go now for my next
> > project, and I'm willing to give boa a try for that.
> >
> > I would love to see the boa CVS activity rising.
>
> Don't worry it's usually not this quiet, hopefully I'll get round to
> updating CVS this week, after that fixes and changes should go in
> regularly.

Cheers,
  Hans-Peter

Re: [Boa Constr] TypeError

[Jordan K. <jkr...@da...>]

> > TypeError: unbound method properties() must be called with
> >            CollectionDTC instance as first argument(got MenuDTC instance
instead)

> This is a bug in Boa that causes errors under Python 2.2.
>
> I hope to release a version 0.1.1 of Boa in a week or two.

There's a fix listed on sourceforge for this problem (which I've been using
lately so that I can play with Boa):

http://sourceforge.net/tracker/index.php?func=detail&aid=510589&group_id=190
9&atid=301909

J.

Re: [Boa Constr] TypeError

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

Hello,

alienoid wrote:
> 
> Hello everyone.
> I'm a newbie in boa. I use v0.1.0-alpha under Win 2K and when I try to
> put wxMenu to Data View I get:
> 
> TypeError: unbound method properties() must be called with
>            CollectionDTC instance as first argument(got MenuDTC instance instead)
> 
> Can anybody help me to understand what it means.

This is a bug in Boa that causes errors under Python 2.2.

I hope to release a version 0.1.1 of Boa in a week or two.

> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> https://lists.sourceforge.net/lists/listinfo/boa-constructor-users

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