Ron & Steve:
Here's an initial shot at a format for documenting a widget. As I remember
the wxWidgets 2.8 pdf documentation was 2500+ pages, so we need to not get
overly ambitious. I have no idea if all of the Member Functions that are
listed in the wxWidgets HTML docs are actually wrapped.
In the example below, it is assumed that $self is the parent frame created
elsewhere in the app.
Comments/additions? Everyone's coding style will probably vary.
James
wxRadioBox (A wxControl)
--------------------------------------
Usage
---------
my @boxes = qw(One Two Three Four Five);
my $cols = 3;
$self->{radiobox} = Wx::RadioBox->new($self, wxID_ANY,
"RadioBox", wxDefaultPosition, wxDefaultSize,
\@boxes, $cols, wxRA_SPECIFY_COLS);
$self->{selection} = $self->{radiobox}->GetStringSelection;
Styles
---------
wxRA_SPECIFY_ROWS, wxRA_SPECIFY_COLS
Events
----------
EVT_RADIOBOX
Member Functions
--------------------------
Enable, FindString, GetColumnCount, GetItemFromPoint,
GetItemHelpText, GetItemToolTip, GetRowCount, IsItemEnabled,
IsItemShown, SetItemHelpText, SetItemToolTip, SetSelection,
Show, GetCount, GetString, SetString, GetSelection, GetStringSelection
Notes
--------
Item numbers start at 0.
The first item in the @boxes list is the default selection.
On Mon, Jan 18, 2016 at 10:19 AM, Steve Cookson - gmail <
steveco.1...@gmail.com> wrote:
> Hi Ron,
>
> Thanks for this.
>
> On 17/01/16 12:53, Ron Grunwald wrote:
>
>
> 1. Introduction to GUI programming and wxPerl
> 2. The wxPerl widgets (currently worked on in the design doc.)
> 3. Geometry management in wxPerl (to be worked on next in the design
> doc.)
> 4. Event handling in wxPerl
> 5. Advanced Topics
>
>
> Is Geometry Management the same as layout? If so I had to do a double
> take to work out what it meant.
>
> Maybe we should also have something about platforms and installation,
> which is always a joy! It could be an appendix if you wanted, so that the
> flow of the chapters was not disrupted.
>
> Regards
>
> Steve.
>
