Re: [Boa Constr] wxMenu.Append nolonger has "checkable" parameter

[John B. <jbe...@ya...>]

Well, this situation isn't really particularly
unusual.  wxWindows (and thus wxPython) has a fairly
high rate of change in the function signature
department for a product of it's level of maturity. 
Some people see this as instability and grizzle
accordingly, but I see it as just reflecting the fact
that the dev team (and the users) are still brimming
with ideas and willing to bear the cost of
implementing them.  This is a large part of what makes
wxPython so much better than Tkinter!  Admittedly,
life would probably be a little easier if their
'stable releases' were a little more frequent.

If your current concern is just to get boa running
(without the enhancements) with your current wxMac
distribution you probably don't need to do much more
than change the name of the name of the property in
the three files it occurs in
(Companions.UtilCompanions, Editor and methodparse).

Regards,
John Bell

--- Seth Delackner <se...@jt...> wrote:
> On Thu, 2002-05-09 at 22:57, Bell John wrote:
> > This isn't quite the case.  Looking at the source
> (see
> > src/defs.i for wxItemKind) the 'checkable'
> property
> > has been replaced by the property 'kind' which can
> > take on a wider range of values.  I haven't
> checked
> > yet if this has actually been updated in the docs,
> but
> > it certainly hasn't been in the changes.txt file -
> > sigh.  Hence I don't know what the new 'kinds' are
> > for.  It just so happens that the values for a
> > checkable item in both the old and new syntax
> happen
> > to be 1.  To answer your question re the CVS
> version,
> > no it still conforms to the 2.3.2 model.
> 
> Yes, it is compatible as long as you aren't using
> named parameters.  If
> you use named parameters (as Boa constructor does),
> then the "checkable"
> being changed to "kind" breaks it.  As far as I can
> see, the simplest
> fix is to just put the "checkable" parameter as an
> unnamed first
> parameter:
> 	checkable = false
> 	parent.Append(checkable, helpString = '...', ...)
> 
> Or just parent.Append(false, ...).  Both solutions
> are less readable and
> uglier than the current state of things, but they
> should at least work.
> 
> Or Boa could just stop passing named parameters for
> that method, as a
> preemptive measure to avoid getting broken in the
> future if other names
> change because they at least made the unnamed
> calling signature stay
> compatible.
> 
> 
>
_______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for
> download mirrors. We supply
> the hardware. You get the recognition. Email Us:
> ban...@so...
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
>
https://lists.sourceforge.net/lists/listinfo/boa-constructor-users


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Mother's Day is May 12th!
http://shopping.yahoo.com