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

[Seth D. <se...@jt...>]

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.