wxperl-users — For wxPerl users

[wxperl-users] wxPerl tutorial at the German Perl Workshop

[Jouke V. <jo...@pv...>]

As you might have heard already I will be giving a half-day tutorial on
wxPerl at the German Perl Workshop. The registration for this event has
just opened, so if you're interested....

Besides the second article on wxPerl for Perl.com is to be finished this
weekend, and will probably be published within some days after that
(care to review Mattia?).

I'm currently writing a book on "GUI Programming with Perl" for Manning,
to be published somewhere in 2002. The main part of the examples in that
book will be written in wxPerl....

I just wanted you all to know....

There is also a slight chance I will give a wxPerl tutorial at TPC next
year....

-- 
*-----------------------------------------------*
|Jouke Visser            |jo...@pv...      |
|Perl GUI Geek           |http://www.pvoice.org |
*-----------------------------------------------*
PS: Notice new mailaddress!!

Re: [wxperl-users] Wx::FlexGridSizer content change

[Mattia B. <mb...@ds...>]

> hello
> 
> i have a FlexGridSizer with 2 columns and 2 rows.
> there is a StaticText inside the FlexGridSizer...
> 
> on some points of my program i have to change the label of the StaticText...
> after i doing this i recalculate the size:
> 
> $size = StaticText->GetSize;
> FlexGridSizer->SetItemMinSize(id, $size->GetWidth, $size->GetHeight);
> 
> then i do a:
> FlexGridSizer->Layout
> 
> now my sizer has changed to the correct size, but sometimes a part of the
> StaticText label isn't visible (just a part of it), it comes out if i resize
> the window or if i minimize and maximize it.
> 
> has someone an idea why this happens?
> is there a better way to relayout a sizer after changing the content?
No; I can't reproduce this there; if you could send a (small) snippet
of code demonstrating the problem, I will have a look at it

> ps: windows && wxPerl 0.07 (but think shouldn't bee a problem)
No it isn't, but it is always a good thing to know OS/version

Regards
Mattia

[wxperl-users] Wx::FlexGridSizer content change

[Marco T. <wx...@so...>]

hello

i have a FlexGridSizer with 2 columns and 2 rows.
there is a StaticText inside the FlexGridSizer...

on some points of my program i have to change the label of the StaticText...
after i doing this i recalculate the size:

$size = StaticText->GetSize;
FlexGridSizer->SetItemMinSize(id, $size->GetWidth, $size->GetHeight);

then i do a:
FlexGridSizer->Layout

now my sizer has changed to the correct size, but sometimes a part of the
StaticText label isn't visible (just a part of it), it comes out if i resize
the window or if i minimize and maximize it.

has someone an idea why this happens?
is there a better way to relayout a sizer after changing the content?

greetings
soapy

ps: windows && wxPerl 0.07 (but think shouldn't bee a problem)

Re: [wxperl-users] Wx::SplashScreen in 0.08

[Matt F. <ma...@iw...>]

heh, I guess you're right. I just got caught up in the coolness of a splash screen.

thanks for knocking some sense back into me,
matt

--- "Marcus" <li...@wo...> wrote:
>On 02.12.01 at 07:06 Matt Felsen wrote:
>>However, this isn't working how I anticipated. I was thinking that the
>>script would halt when the splah screen appears, and wouldn't continue
>to
>>run until the splash screen times out, or someone clicks on it.
>
>As far as I know, and the way I have used them, the purpose of a splash
>screen is to show the user that loading is taking place. That's why you
>place your call to the splash screen inside a BEGIN { } for example, so
>that it loads first, then the main application is loaded. Once all the
>GUI information has loaded, you close the splash screen before showing
>the main application window. That's how they normally work. Hence, you
>don't really need a splash screen for fast loading applications.
>
>How are you using the splash screen?
>What's the purpose of having the user click on it before continuing?
>
>Marcus
>
>
>
>_______________________________________________
>wxperl-users mailing list
>wxp...@li...
>https://lists.sourceforge.net/lists/listinfo/wxperl-users

_____________________________________________________________

Re: [wxperl-users] WxPerl on FreeBSD?

[Bert D. <dri...@pl...>]

On Sun, 2 Dec 2001, Mattia Barbon wrote:

> > Alternatively I could build seperate non-threaded libraries just for
> > WxPerl (which, by the way, is not the only victim of the way threads are
> > handled on FreeBSD), but in my experience it's pretty hard to make Perl
> > play ball with that setup, unless those libs are linked in
> > statically. I've had some successes doing that in the past, but it's not
> > fun exercise...
> Does this really mean that if you have
> libwxgtk.so ( or whatever ) dynamically linked to a perl extension,
> this does not work ? and setting LD_LIBRARY_PATH ( or whatever it is on *BSD ) does 
> not work either ? This is weird...

LD_LIBRARY_PATH will be honored, but FreeBSD does not honor LD_RUN_PATH
when building a .so (it does for the final app, but that would mean Perl
itself, which is precisely what we don't need).

> OTOH, if you resolve this, would you mind writing some instructions
> to put on INSTALL.txt ?

If I do (and that's a big if :-) I'll make sure I write up the recipy.

Cheers,

				-- Bert

-- 
Bert Driehuis -- dri...@pl... -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!

[wxperl-users] Current demo.pl crashes on wxGTK

[Mattia B. <mb...@ds...>]

I suddenly realized that I _never_ tested the
Printing, MDI, and DND in wxGTK using the demo

While DND works fine, the code in the demo that
demonstrates Printing and MDI has some GTK-related errors;
these are corrected in 

http://prdownloads.sourceforge.net/wxperl/wxPerl-0.08-samples-1.zip

Sorry
Mattia

Re: [wxperl-users] Wx::SplashScreen in 0.08

[Marcus <li...@wo...>]

On 02.12.01 at 07:06 Matt Felsen wrote:
>However, this isn't working how I anticipated. I was thinking that the
>script would halt when the splah screen appears, and wouldn't continue
to
>run until the splash screen times out, or someone clicks on it.

As far as I know, and the way I have used them, the purpose of a splash
screen is to show the user that loading is taking place. That's why you
place your call to the splash screen inside a BEGIN { } for example, so
that it loads first, then the main application is loaded. Once all the
GUI information has loaded, you close the splash screen before showing
the main application window. That's how they normally work. Hence, you
don't really need a splash screen for fast loading applications.

How are you using the splash screen?
What's the purpose of having the user click on it before continuing?

Marcus

Re: [wxperl-users] WxPerl on FreeBSD?

[Mattia B. <mb...@ds...>]

> On Sun, 2 Dec 2001, Mattia Barbon wrote:
> 
> > > Unrecognized argument in LIBS ignored: '-pthread'
> > I don't know if I can work around this ( for all platforms ), but I'll try
> 
> I'm not sure it makes sense at this stage...
Maybe not for this case, but I am sick of seeing

Unknown option "-rdynamic" in LIBS: ignored

everytime I build; and I don't think that Perl should strip arbitrary
thinds from flags, either

> > > but predictably with this voodoo the extension is not very stable (a bit
> > > of clicking around in demo/samples/controls/controls.pl and some
> > > resizing, and foom: a Perl crash without further traceback in xdr_u_int;
> > > obviously a threadsafe/no threadsafe mismatch).
> > > 
> > > FreeBSD 4.4, the Perl that came with it (5.005_03), wxWindows build from
> > > the ports collection of FreeBSD 4.4 (wxgtk-2.2.7,1).
> > You might try to rebuild wxWindows with --disable-threads ( and maybe
> > gtk/glib ? ); unfortunately I can't reproduce this, because I don't
> > havd FreeBSD, and on Linux building wxWindows with threads and perl without does work 
> > just fine.
> 
> That would work, but that would cause other apps to fail :-(
> 
> Alternatively I could build seperate non-threaded libraries just for
> WxPerl (which, by the way, is not the only victim of the way threads are
> handled on FreeBSD), but in my experience it's pretty hard to make Perl
> play ball with that setup, unless those libs are linked in
> statically. I've had some successes doing that in the past, but it's not
> fun exercise...
Does this really mean that if you have
libwxgtk.so ( or whatever ) dynamically linked to a perl extension,
this does not work ? and setting LD_LIBRARY_PATH ( or whatever it is on *BSD ) does 
not work either ? This is weird...
OTOH, if you resolve this, would you mind writing some instructions
to put on INSTALL.txt ?

Regards
Mattia

RE: [wxperl-users] [ANNOUNCE] wxPerl 0.08

[Casey W. <wil...@nc...>]

Ok, I got it to work.  Not exactly sure how...  I got rid of everything
on my HD that had to do with wxPerl besides the new one.  Then installed
0.08.  All is well. :)

-Casey

-----Original Message-----
From: wxp...@li...
[mailto:wxp...@li...] On Behalf Of Casey
Williams
Sent: Sunday, December 02, 2001 12:13 PM
To: wxp...@li...
Subject: RE: [wxperl-users] [ANNOUNCE] wxPerl 0.08


> One thing though, clicking on serveral of the things in the demo make
> it crash.  1 such thing is the MDI.  When I try clicking on the mdi 
> demo it gives the attatched error before crashing.  Wasn't sure if 
> it's because it needs the 2.3 stuff as you said on your site, but I 
> thought the MDI
No, the demo should work fine with 2.2, too ( with 2.3 shows some more
things, though 
)

> should work without it.  Or maybe somethings wrong with my install?
> Ok,
I think so; try uninstalling Wx ( ppm remove Wx ), and then
re-installing it; looks 
like ppm could not overwrite th old Wx.dll




Ok, I tried reinstalling it on both my Win2K box and my WinXP box, I get
the same thing on both.

-Casey





_______________________________________________
wxperl-users mailing list
wxp...@li...
https://lists.sourceforge.net/lists/listinfo/wxperl-users

RE: [wxperl-users] [ANNOUNCE] wxPerl 0.08

[Casey W. <wil...@nc...>]

> One thing though, clicking on serveral of the things in the demo make 
> it crash.  1 such thing is the MDI.  When I try clicking on the mdi 
> demo it gives the attatched error before crashing.  Wasn't sure if 
> it's because it needs the 2.3 stuff as you said on your site, but I 
> thought the MDI
No, the demo should work fine with 2.2, too ( with 2.3 shows some more
things, though 
)

> should work without it.  Or maybe somethings wrong with my install?  
> Ok,
I think so; try uninstalling Wx ( ppm remove Wx ), and then
re-installing it; looks 
like ppm could not overwrite th old Wx.dll




Ok, I tried reinstalling it on both my Win2K box and my WinXP box, I get
the same thing on both.

-Casey

RE: [wxperl-users] [ANNOUNCE] wxPerl 0.08

[Matt S. <ma...@se...>]

On Sun, 2 Dec 2001, Mattia Barbon wrote:

> <please reply to the list>
>
> > Awesome!!
> >
> > One thing though, clicking on serveral of the things in the demo make it
> > crash.  1 such thing is the MDI.  When I try clicking on the mdi demo it
> > gives the attatched error before crashing.  Wasn't sure if it's because
> > it needs the 2.3 stuff as you said on your site, but I thought the MDI
> No, the demo should work fine with 2.2, too ( with 2.3 shows some more things, though
> )
>
> > should work without it.  Or maybe somethings wrong with my install?  Ok,
> I think so; try uninstalling Wx ( ppm remove Wx ), and then re-installing it; looks
> like ppm could not overwrite th old Wx.dll

Same bug here on Linux.

-- 
<Matt/>

    /||    ** Founder and CTO  **  **   http://axkit.com/     **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // ** mod_perl news and resources: http://take23.org  **
     \\//
     //\\
    //  \\

Re: [wxperl-users] WxPerl on FreeBSD?

[Bert D. <dri...@pl...>]

On Sun, 2 Dec 2001, Mattia Barbon wrote:

> > Unrecognized argument in LIBS ignored: '-pthread'
> I don't know if I can work around this ( for all platforms ), but I'll try

I'm not sure it makes sense at this stage...

> > Wheb built this way, "make test" reports it can't find pthread_create.
> > 
> > Manually sprinkling a bunch of "-pthread"s and "-lc_r" gets it to build,
> did you add -Wl,-E, too? 

Yup. Actually, they were already in there from the standard MakeMaker
magic.

> > but predictably with this voodoo the extension is not very stable (a bit
> > of clicking around in demo/samples/controls/controls.pl and some
> > resizing, and foom: a Perl crash without further traceback in xdr_u_int;
> > obviously a threadsafe/no threadsafe mismatch).
> > 
> > FreeBSD 4.4, the Perl that came with it (5.005_03), wxWindows build from
> > the ports collection of FreeBSD 4.4 (wxgtk-2.2.7,1).
> You might try to rebuild wxWindows with --disable-threads ( and maybe
> gtk/glib ? ); unfortunately I can't reproduce this, because I don't
> havd FreeBSD, and on Linux building wxWindows with threads and perl without does work 
> just fine.

That would work, but that would cause other apps to fail :-(

Alternatively I could build seperate non-threaded libraries just for
WxPerl (which, by the way, is not the only victim of the way threads are
handled on FreeBSD), but in my experience it's pretty hard to make Perl
play ball with that setup, unless those libs are linked in
statically. I've had some successes doing that in the past, but it's not
fun exercise...

Cheers,

				-- Bert

-- 
Bert Driehuis -- dri...@pl... -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!

Re: [wxperl-users] WxPerl on FreeBSD?

[Mattia B. <mb...@ds...>]

> Has anyone built WxPerl on FreeBSD? The problem is that Perl on FreeBSD
> is built without pthreads, but wxwindows is built with pthreads.
 
> perl5 Makefile.PL complains about library settings it inherits from
> gtk-config:
> 
> % /usr/local/bin/perl5 Makefile.PL
> Checking if your kit is complete...
> Looks good
> Unrecognized argument in LIBS ignored: '-Wl,-E'
> Unrecognized argument in LIBS ignored: '-pthread'
I don't know if I can work around this ( for all platforms ), but I'll try

> Wheb built this way, "make test" reports it can't find pthread_create.
> 
> Manually sprinkling a bunch of "-pthread"s and "-lc_r" gets it to build,
did you add -Wl,-E, too? 

> but predictably with this voodoo the extension is not very stable (a bit
> of clicking around in demo/samples/controls/controls.pl and some
> resizing, and foom: a Perl crash without further traceback in xdr_u_int;
> obviously a threadsafe/no threadsafe mismatch).
> 
> FreeBSD 4.4, the Perl that came with it (5.005_03), wxWindows build from
> the ports collection of FreeBSD 4.4 (wxgtk-2.2.7,1).
You might try to rebuild wxWindows with --disable-threads ( and maybe
gtk/glib ? ); unfortunately I can't reproduce this, because I don't
havd FreeBSD, and on Linux building wxWindows with threads and perl without does work 
just fine.

Regards
Mattia

Re: [wxperl-users] Wx::SplashScreen in 0.08

[Mattia B. <mb...@ds...>]

> Hi. In my Wx::App package in the OnInit sub, I create a Wx::Bitmap,
> then load a Wx::SplashScreen with that bitmap.  Then I create the
> main frame. However, this isn't working how I anticipated. I was
> thinking that the script would halt when the splah screen appears,
> and wouldn't continue to run until the splash screen times out, or
> someone clicks on it. This is not the case.  The splash screen
> appears, but then the frame opens right after it. Is there a way to
> fix this?
Well, I think the default behaviour is right, because I always think
that a splash screen is an eyecandy to show while the app is loading;
to achieve what you want you could:
1) put an explicit delay right after SplashScreen creation
2) add and EVT_CLOSE to the SplashScreen
   and from the OnClose function, Show() your frame

Regards
Mattia

[wxperl-users] WxPerl on FreeBSD?

[Bert D. <dri...@pl...>]

Has anyone built WxPerl on FreeBSD? The problem is that Perl on FreeBSD
is built without pthreads, but wxwindows is built with pthreads.

perl5 Makefile.PL complains about library settings it inherits from
gtk-config:

% /usr/local/bin/perl5 Makefile.PL
Checking if your kit is complete...
Looks good
Unrecognized argument in LIBS ignored: '-Wl,-E'
Unrecognized argument in LIBS ignored: '-pthread'

Wheb built this way, "make test" reports it can't find pthread_create.

Manually sprinkling a bunch of "-pthread"s and "-lc_r" gets it to build,
but predictably with this voodoo the extension is not very stable (a bit
of clicking around in demo/samples/controls/controls.pl and some
resizing, and foom: a Perl crash without further traceback in xdr_u_int;
obviously a threadsafe/no threadsafe mismatch).

FreeBSD 4.4, the Perl that came with it (5.005_03), wxWindows build from
the ports collection of FreeBSD 4.4 (wxgtk-2.2.7,1).

Cheers,

			-- Bert

-- 
Bert Driehuis -- dri...@pl... -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!

[wxperl-users] Wx::SplashScreen in 0.08

[Matt F. <ma...@iw...>]

Hi. In my Wx::App package in the OnInit sub, I create a Wx::Bitmap, then load a Wx::SplashScreen with that bitmap.  Then I create the main frame. However, this isn't working how I anticipated. I was thinking that the script would halt when the splah screen appears, and wouldn't continue to run until the splash screen times out, or someone clicks on it. This is not the case.  The splash screen appears, but then the frame opens right after it. Is there a way to fix this?

Thanks,
Matt

my $bitmap = Wx::Bitmap->new("bitmaps/splash.bmp", wxBITMAP_TYPE_BMP);
my $splash = Wx::SplashScreen->new($bitmap, wxSPLASH_CENTRE_ON_SCREEN | wxSPLASH_TIMEOUT, 3000, undef, -1, wxDefaultPosition, wxDefaultSize, wxSTATIC_BORDER | wxSTAY_ON_TOP);
my $frame = Frame->new("wxbot v0.1", wxDefaultPosition, wxDefaultSize);
$self->SetTopWindow($frame);
$frame->Show(1);

_____________________________________________________________

RE: [wxperl-users] [ANNOUNCE] wxPerl 0.08

[Mattia B. <mb...@ds...>]

<please reply to the list>

> Awesome!!
> 
> One thing though, clicking on serveral of the things in the demo make it
> crash.  1 such thing is the MDI.  When I try clicking on the mdi demo it
> gives the attatched error before crashing.  Wasn't sure if it's because
> it needs the 2.3 stuff as you said on your site, but I thought the MDI
No, the demo should work fine with 2.2, too ( with 2.3 shows some more things, though 
)

> should work without it.  Or maybe somethings wrong with my install?  Ok,
I think so; try uninstalling Wx ( ppm remove Wx ), and then re-installing it; looks 
like ppm could not overwrite th old Wx.dll

Regards
Mattia

> I'm tired, I'm rambling, I'll leave you be. :)
> 
> Thanks for all your help and patience!
> 
> -Casey
> 
> -----Original Message-----
> From: wxp...@li...
> [mailto:wxp...@li...] On Behalf Of Mattia
> Barbon
> Sent: Saturday, December 01, 2001 5:08 PM
> To: wxp...@li...; wx-...@li...
> Subject: [wxperl-users] [ANNOUNCE] wxPerl 0.08
> 
> 
> A new version of wxPerl, the Perl bindings to wxWindows
> is out!
> 
> You can download the source from
> http://prdownload.sourceforge.net/wxperl/Wx-0.08.tar.gz
> 
> Binary packages for ActivePerl/Win32 6xx builds,
> Redhat Linux 7.1 and Debian GNU/Linux "woody"
> are available along with documentation in HTML and
> MS HTML Help format from
> http://sourceforge.net/project/showfiles.php?group_id=15655
> and http://wxperl.sourceforge.net/
> 
> Regards
> Mattia
> 
> 
> _______________________________________________
> wxperl-users mailing list
> wxp...@li...
> https://lists.sourceforge.net/lists/listinfo/wxperl-users
> 

Re: [wxperl-users] [ANNOUNCE] wxPerl 0.08

[Jouke V. <jo...@pv...>]

See the website http://wxperl.sourceforge.net :)

Jouke
On Sun, Dec 02, 2001 at 10:14:01AM +0000, Matt Sergeant wrote:
> On Sun, 2 Dec 2001, Mattia Barbon wrote:
> 
> > A new version of wxPerl, the Perl bindings to wxWindows
> > is out!
> 
> What are the changes?
> 
> -- 
> <Matt/>
> 
>     /||    ** Founder and CTO  **  **   http://axkit.com/     **
>    //||    **  AxKit.com Ltd   **  ** XML Application Serving **
>   // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
>  // \\| // ** mod_perl news and resources: http://take23.org  **
>      \\//
>      //\\
>     //  \\
> 
> 
> _______________________________________________
> wxperl-users mailing list
> wxp...@li...
> https://lists.sourceforge.net/lists/listinfo/wxperl-users

-- 
*-----------------------------------------------*
|Jouke Visser            |jo...@pv...      |
|Perl GUI Geek           |http://www.pvoice.org |
*-----------------------------------------------*
PS: Notice new mailaddress!!

Re: [wxperl-users] [ANNOUNCE] wxPerl 0.08

[Matt S. <ma...@se...>]

On Sun, 2 Dec 2001, Mattia Barbon wrote:

> A new version of wxPerl, the Perl bindings to wxWindows
> is out!

What are the changes?

-- 
<Matt/>

    /||    ** Founder and CTO  **  **   http://axkit.com/     **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // ** mod_perl news and resources: http://take23.org  **
     \\//
     //\\
    //  \\

[wxperl-users] [ANNOUNCE] wxPerl 0.08

[Mattia B. <mb...@ds...>]

A new version of wxPerl, the Perl bindings to wxWindows
is out!

You can download the source from
http://prdownload.sourceforge.net/wxperl/Wx-0.08.tar.gz

Binary packages for ActivePerl/Win32 6xx builds,
Redhat Linux 7.1 and Debian GNU/Linux "woody"
are available along with documentation in HTML and
MS HTML Help format from
http://sourceforge.net/project/showfiles.php?group_id=15655
and http://wxperl.sourceforge.net/

Regards
Mattia

(Fwd) Re: [wxperl-users] BoxSizer in a SplitterWindow

[Mattia B. <mb...@ds...>]

Oops, wrong list...
------- Forwarded message follows -------
From:           	"Mattia Barbon" <mb...@ds...>
To:             	wx-...@li...
Subject:        	Re: [wxperl-users] BoxSizer in a SplitterWindow
Priority:       	normal
Send reply to:  	wx-...@li...
Date sent:      	Fri, 30 Nov 2001 23:58:26 +0100

[ Double-click this line for list subscription options ] 

> hey fellows,
> how's everybody doing tonight ?
> 
> i try to put some labels above a TextCtrl in a SplitterWindow...
> i think this way is the best:
> 
> - put a Wx::Window in the SplitterWindow
If it must contain controls, it is better to use a Wx::Panel

> - create a sizer with a Label and a TextCtrl
> - assign the sizer to the Wx::Window and SetAutoLayout for the Wx::Window
> 
> but it refuses to work... i have no idea why...
Because Wx::Window does not do automatic layout of subwindows;
Wx::Panel will allow you to navigate between controls using
<TAB> 

> any hints/tipps or better ways to solve my problem?
> i would really appreciate it...
FYI using a Wx::Window you could just add an OnSize handler that
calls ->Layout();

Regards
Mattia

> nearly forgot, my code (MyFrame part, abstracted to the problem):
> 
> sub new
> {
>       my($class) = shift;
>       my $this = $main::frame = $class->SUPER::new($_[0], -1, @_[1,2,3]);
> 
>       my $splitter = Wx::SplitterWindow->new($this, -1, wxDefaultPosition,
> wxDefaultSize);
>       my $window   = Wx::Window->new($splitter, -1, wxDefaultPosition,
> wxDefaultSize);
>       my $sizer    = Wx::BoxSizer->new(wxVERTICAL);
> 
>       $this->{tree}     = Wx::TreeCtrl->new($splitter, -1);
>       $this->{label}    = Wx::StaticText->new($window, -1, 'not working
> testlabel');
>       $this->{text}     = Wx::TextCtrl->new($window, -1, '',
> wxDefaultPosition, wxDefaultSize, wxTE_MULTILINE);
> 
>       $sizer->Add($this->{label}, 0, wxEXPAND);
>       $sizer->Add($this->{text}, 1, wxEXPAND);
>       $window->SetSizer($sizer);
>       $window->SetAutoLayout(1);
>       $window->SetBackgroundColour(wxGREEN);
> 
>       $splitter->SplitVertically($this->{tree}, $window);
> 
>       return $this;
> }
> 
> 
> _______________________________________________
> wxperl-users mailing list
> wxp...@li...
> https://lists.sourceforge.net/lists/listinfo/wxperl-users
> 



_______________________________________________
wx-users mailing list
wx-...@li...
http://lists.wxwindows.org/mailman/listinfo/wx-users

------- End of forwarded message -------

[wxperl-users] BoxSizer in a SplitterWindow

[soapy <ad...@so...>]

hey fellows,
how's everybody doing tonight ?

i try to put some labels above a TextCtrl in a SplitterWindow...
i think this way is the best:

- put a Wx::Window in the SplitterWindow
- create a sizer with a Label and a TextCtrl
- assign the sizer to the Wx::Window and SetAutoLayout for the Wx::Window

but it refuses to work... i have no idea why...

any hints/tipps or better ways to solve my problem?
i would really appreciate it...

greetings
marco

nearly forgot, my code (MyFrame part, abstracted to the problem):

sub new
{
      my($class) = shift;
      my $this = $main::frame = $class->SUPER::new($_[0], -1, @_[1,2,3]);

      my $splitter = Wx::SplitterWindow->new($this, -1, wxDefaultPosition,
wxDefaultSize);
      my $window   = Wx::Window->new($splitter, -1, wxDefaultPosition,
wxDefaultSize);
      my $sizer    = Wx::BoxSizer->new(wxVERTICAL);

      $this->{tree}     = Wx::TreeCtrl->new($splitter, -1);
      $this->{label}    = Wx::StaticText->new($window, -1, 'not working
testlabel');
      $this->{text}     = Wx::TextCtrl->new($window, -1, '',
wxDefaultPosition, wxDefaultSize, wxTE_MULTILINE);

      $sizer->Add($this->{label}, 0, wxEXPAND);
      $sizer->Add($this->{text}, 1, wxEXPAND);
      $window->SetSizer($sizer);
      $window->SetAutoLayout(1);
      $window->SetBackgroundColour(wxGREEN);

      $splitter->SplitVertically($this->{tree}, $window);

      return $this;
}

Re: [wxperl-users] In need of a little clarification...

[Mattia B. <mb...@ds...>]

> Can someone explain why the App class and the Frame
> class are two separate things?  What's the
The app represents the application as a whole;
you _must_ create one and only one app instance,
while you can create any number of frames; a frame
is a top level window, an app does not represent any
type of window.

> significance of this?  What does it allow you to do? 
> So far it seems to only be making it harder for me to
> understand. ;-)  I'm not clear on which one would load
> the contanstants, events, etc. and which one would
> handle the actual event subroutines.
In general an app does not have any event handlers ( you could
add a default event handler to the wxApp that processes otherwise
unhandled events, but this is rarely necessary ); in general event 
handlers are or in the control that generates them ( for all kinds
of events ), or in one of their ancestors ( for
wxCommandEvent-derived events, like button clicks )

Hope it is clerarer now
Mattia

[wxperl-users] In need of a little clarification...

[Jeremy B. <sco...@ya...>]

Okay, so I'm trying to get an understanding of how to
work with wxPerl.  I see how the samples work and I
can get a basic app going, but I'm just not clear on
how the actual script works.

Can someone explain why the App class and the Frame
class are two separate things?  What's the
significance of this?  What does it allow you to do? 
So far it seems to only be making it harder for me to
understand. ;-)  I'm not clear on which one would load
the contanstants, events, etc. and which one would
handle the actual event subroutines.

How does everyone else keep these straight?

Thanks,
Jeremy Blonde




__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

Re: [wxperl-users] How to kick off event functions while in a loop

[Casey W. <wil...@nc...>]

Correction:

The whole problem was in my variable declaration (should have been 'our' not
'my'), not the funtion stuff. *blush*

-Casey


> Ok, I figured out the variable thing...I was using an anonymous sub
instead
> of a regular sub ref in the Event function.
>
> ----- Original Message -----
> From: "Casey Williams" <wil...@nc...>
> To: <wxp...@li...>
> Sent: Wednesday, November 28, 2001 3:33 PM
> Subject: Re: [wxperl-users] How to kick off event functions while in a
loop
>
>
> > > > Hey guys,
> > > >     I've been seaching through the doc's for a way to fire off
Events
> > > even if I'm running a loop such as...
> > > >
> > > > foreach my $i (0..999999) {...}
> > > >
> > > > I've found the Yield() and SafeYield() functions.  But those only
> > > allow the GUI to be updated for interaction, but don't allow the
> > > functions tied to the events to be called.  At least, as far as I can
> > > tell anyhow.  Anyone have any advice?
> > > The only "real" solution to your problem is to use threads; as an
> >
> > I was afraid of that. :(  Are threads available in wxPerl?  All I
*really*
> > need to do is toggle a variable by pressing a button to make the loop
> stop.
> >
> > > ( ugly ) workaround you might use a wxTimer; using wxYield is
_strongly_
> > > discouraged because it can lead to unexpected reentrancy
> > > problems ( of course there are cases where you can't do without ).
> > > I never used it, so I can't tell if the handlers not being fired is
> > > a wxPerl or a wxWindows problem ( will check ).
> >
> > Thanks again!