On Tue, 2004-10-26 at 16:19 +0800, Austin wrote:[color=blue]
> Every time i use wxRadioBox, it will show the box.
> I just want the options show on the panel. What could i do?[/color]
Don't use a wx.RadioBox. The box is a feature of that control. Instead
just use wx.RadioButtons and lay them out yourself in a wx.BoxSizer.
Do I have to go to 2.4 in order to start using wx.Control, versus wxControl
?
"Cliff Wells" <clifford.wells @comcast.net> wrote in message
news:mailman.55 03.1098793300.5 135.python-list@python.org ...[color=blue]
> On Tue, 2004-10-26 at 16:19 +0800, Austin wrote:[color=green]
>> Every time i use wxRadioBox, it will show the box.
>> I just want the options show on the panel. What could i do?[/color]
>
> Don't use a wx.RadioBox. The box is a feature of that control. Instead
> just use wx.RadioButtons and lay them out yourself in a wx.BoxSizer.
>
> Regards,
> Cliff
>
> --
> Cliff Wells <clifford.wells @comcast.net>
>[/color]
On Wed, 2004-10-27 at 03:34 +0000, StvB wrote:[color=blue]
> Do I have to go to 2.4 in order to start using wx.Control, versus wxControl
> ?[/color]
Yes. But frankly, if you are going to upgrade, why not go to 2.5? In
2.4 the wx namespace is a hack. In 2.5 it's the real thing. Plus there
are plenty of other enhancements.
Cliff Wells <clifford.wells @comcast.net> writes:
[color=blue]
> On Wed, 2004-10-27 at 03:34 +0000, StvB wrote:[color=green]
>> Do I have to go to 2.4 in order to start using wx.Control, versus wxControl
>> ?[/color]
>
> Yes. But frankly, if you are going to upgrade, why not go to 2.5? In
> 2.4 the wx namespace is a hack. In 2.5 it's the real thing. Plus there
> are plenty of other enhancements.[/color]
One reason is that the website states that 2.4 is the latest stable
series, while 2.5 is the latest development series.
WRT the hack, the wxwidgets people abandoned the changes there...
On Tue, 2004-11-02 at 16:42 -0200, Jorge Godoy wrote:[color=blue]
> Cliff Wells <clifford.wells @comcast.net> writes:
>[color=green]
> > On Wed, 2004-10-27 at 03:34 +0000, StvB wrote:[color=darkred]
> >> Do I have to go to 2.4 in order to start using wx.Control, versus wxControl
> >> ?[/color]
> >
> > Yes. But frankly, if you are going to upgrade, why not go to 2.5? In
> > 2.4 the wx namespace is a hack. In 2.5 it's the real thing. Plus there
> > are plenty of other enhancements.[/color]
>
> One reason is that the website states that 2.4 is the latest stable
> series, while 2.5 is the latest development series.[/color]
Right, but I've been using wx for several years and I can assure you
that the development branch is where you want to be. It is no less
stable and tends to be far better functionality-wise. The only possible
instability is in the API and frankly you'll only notice if you move
from 2.4 to to 2.5.
[color=blue]
> WRT the hack, the wxwidgets people abandoned the changes there...[/color]
But not the wxPython people, which is what we care about here ;)
Cliff Wells <clifford.wells @comcast.net> writes:
[color=blue]
> Right, but I've been using wx for several years and I can assure you
> that the development branch is where you want to be. It is no less[/color]
I've been using it for 2 years now. And I assure you the stable branch
is where I want to be. :-) The development branch causes me trouble
with Windows 98 machines, used by some of our costumers. I've posted
about it two or three times on the wxPython ML.
[color=blue]
> stable and tends to be far better functionality-wise. The only possible
> instability is in the API and frankly you'll only notice if you move
> from 2.4 to to 2.5.[/color]
I agree with you that there are a lot of new functionalities and
facilities that are very interesting. Unfortunately, they don't work on
each and every system we need to support, so...
[color=blue][color=green]
>> WRT the hack, the wxwidgets people abandoned the changes there...[/color]
>
> But not the wxPython people, which is what we care about here ;)[/color]
I hope so. I found the interface much cleaner, but I thought Robin had
some "I lost time" feeling when he posted saying that wxWidgets people
hadn't done the change as expected.
Comment