You can subscribe to this list here.
2001 |
Jan
(226) |
Feb
(139) |
Mar
(156) |
Apr
(95) |
May
(181) |
Jun
(166) |
Jul
(80) |
Aug
(59) |
Sep
(69) |
Oct
(83) |
Nov
(142) |
Dec
(33) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(42) |
Feb
(91) |
Mar
(76) |
Apr
(113) |
May
(67) |
Jun
(68) |
Jul
(37) |
Aug
(41) |
Sep
(16) |
Oct
(135) |
Nov
(51) |
Dec
(21) |
2003 |
Jan
(37) |
Feb
(36) |
Mar
(37) |
Apr
(103) |
May
(68) |
Jun
(70) |
Jul
(77) |
Aug
(12) |
Sep
(9) |
Oct
(53) |
Nov
(88) |
Dec
(63) |
2004 |
Jan
(263) |
Feb
(106) |
Mar
(36) |
Apr
(21) |
May
(21) |
Jun
(34) |
Jul
(33) |
Aug
(34) |
Sep
(35) |
Oct
(21) |
Nov
(43) |
Dec
(63) |
2005 |
Jan
(28) |
Feb
(42) |
Mar
(29) |
Apr
(14) |
May
(41) |
Jun
(20) |
Jul
(65) |
Aug
(136) |
Sep
(41) |
Oct
(74) |
Nov
(34) |
Dec
(94) |
2006 |
Jan
(85) |
Feb
(94) |
Mar
(68) |
Apr
(103) |
May
(66) |
Jun
(51) |
Jul
(24) |
Aug
(56) |
Sep
(57) |
Oct
(85) |
Nov
(73) |
Dec
(68) |
2007 |
Jan
(59) |
Feb
(32) |
Mar
(13) |
Apr
(32) |
May
(36) |
Jun
(36) |
Jul
(64) |
Aug
(35) |
Sep
(19) |
Oct
(10) |
Nov
(13) |
Dec
(20) |
2008 |
Jan
(26) |
Feb
(41) |
Mar
(19) |
Apr
(24) |
May
(16) |
Jun
(33) |
Jul
(34) |
Aug
(4) |
Sep
(11) |
Oct
|
Nov
(26) |
Dec
(23) |
2009 |
Jan
(5) |
Feb
(2) |
Mar
(21) |
Apr
(16) |
May
(13) |
Jun
(6) |
Jul
(34) |
Aug
(2) |
Sep
(1) |
Oct
(7) |
Nov
(5) |
Dec
(24) |
2010 |
Jan
(3) |
Feb
(5) |
Mar
(6) |
Apr
(6) |
May
(14) |
Jun
(6) |
Jul
(1) |
Aug
(12) |
Sep
(10) |
Oct
(9) |
Nov
|
Dec
(2) |
2011 |
Jan
(4) |
Feb
(5) |
Mar
(30) |
Apr
(1) |
May
(2) |
Jun
(5) |
Jul
(3) |
Aug
(2) |
Sep
(3) |
Oct
|
Nov
(6) |
Dec
|
2012 |
Jan
|
Feb
(10) |
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(4) |
2013 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
(3) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(7) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(5) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Brian M. <bmi...@hu...> - 2008-03-23 20:59:31
|
Jeremy White wrote: > Hi, > > I'm having a strange problem with Win32::GUI running under Vista with > PerlApp 7.1. I have raised a bug with Activestate: > > http://bugs.activestate.com/show_bug.cgi?id=74844 > > But they can't seem to reproduce the problem. If you have a couple of > minutes free and are running windows Vista I'd be greatful if you > could see if the exe (see the attachment for the URL) in the above > thread runs on your machine. > > To run the exe, just double click on it. If it runs correctly you'll > see a file selection box. If it doesn't run correctly no file > selection box will be shown (or it flashes quickly before exiting). > You'll need to run it several times as I seem to get at least 1 > failure per 10 runs. Any feedback (positive or negative) would help in > nailing this issue. > > Cheers, > > Jeremy. > I just ran it 20 times on my laptop running Vista, no failures. The file selection dialog appeared each time. -- Brian, Tommy, Helen and Paka -- bmi...@hu... This message traveled at least 44,000 miles to reach you! --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 080323-0, 03/23/2008 Tested on: 3/23/2008 4:58:25 PM avast! is copyright (c) 2000-2008 ALWIL Software. http://www.avast.com |
From: Jeremy W. <jez...@ho...> - 2008-03-22 12:21:06
|
Hi, I'm having a strange problem with Win32::GUI running under Vista with PerlApp 7.1. I have raised a bug with Activestate: http://bugs.activestate.com/show_bug.cgi?id=74844 But they can't seem to reproduce the problem. If you have a couple of minutes free and are running windows Vista I'd be greatful if you could see if the exe (see the attachment for the URL) in the above thread runs on your machine. To run the exe, just double click on it. If it runs correctly you'll see a file selection box. If it doesn't run correctly no file selection box will be shown (or it flashes quickly before exiting). You'll need to run it several times as I seem to get at least 1 failure per 10 runs. Any feedback (positive or negative) would help in nailing this issue. Cheers, Jeremy. _________________________________________________________________ Get Hotmail on your mobile. Text MSN to 63463 now! http://mobile.uk.msn.com/pc/mail.aspx |
From: Doug H. <hof...@ci...> - 2008-03-21 19:18:31
|
I have a bunch of buttons on a window that use -picture .bmp images to show if the button is on or off. The data for the buttons on and off state comes from a file that changes all the time. What's the proper way to refresh the window and hence re-draw all of the button objects on the window? I am not adding any new objects to the window, I just want to re-draw them all to reflect their on/off state. Looking at the gui docs, not sure what is the correct way to do this. Thanks for any help Doug |
From: Doug H. <hof...@ci...> - 2008-03-21 17:53:41
|
Thanks Glenn, There doesn't seem to be any gui documentaion or examples on the exact right and wrong way this should be handled. I guess it's a bit understandable why newbies like me find it confusing. :) I did play with the userdata method also and that is a pretty cool tool. I appreciate the help. ----- Original Message ----- From: Glenn W Munroe To: 'Doug Hoffman' ; per...@li... Sent: March 21, 2008 1:41 PM Subject: RE: [perl-win32-gui-users] Button onClick event Doug, That will work, but it breaks one of the golden rules of OO programming: don't access internal object data directly. Of course, it doesn't help that there isn't a 'Name' method! The same applies to the window handle {-handle}, incidentally. A more purist approach would be to use the UserData method, something like this: ################################################################## use strict; use Win32::GUI(); my $obMW = new Win32::GUI::Window( -name => 'Main', -size => [200,200], -text => 'Main', ); $obMW->AddButton( -name => 'Button1', -pos => [10,10], -size => [75,23], -text => 'Button1', -onClick => sub { Win32::MsgBox("You just clicked ".$_[0]->UserData) }, ); $obMW->Button1->UserData('Button1'); $obMW->AddButton( -name => 'Button2', -pos => [10,50], -size => [75,23], -text => 'Button2', -onClick => sub { Win32::MsgBox("You just clicked ".$_[0]->UserData()) }, ); $obMW->Button2->UserData('Button2'); $obMW->Show(); Win32::GUI::Dialog(); ####################################################################### That won't work for the handle, though, as we don't have it at control creation time. Perhaps we should add 'Name' and 'Handle' methods to the module? Glenn ------------------------------------------------------------------------------ From: per...@li... [mailto:per...@li...] On Behalf Of Doug Hoffman Sent: 21 March 2008 14:23 To: per...@li... Subject: Re: [perl-win32-gui-users] Button onClick event Thanks to all who replied. Here is the code that I received. my ($ButtonClicked, @other_params) = @_; my $ButtonName = $ButtonClicked->{-name}; Thanks to Sean for the email He was nice enough to explain the mechanics of the code above and how it fetches the button -name Here's the button add and button_click sub for all who may want it. ### add button ######################### my $Button = new Win32::GUI::Button($Main, -name => "Test", -tip => "Test", -width => 15, -height => 15, -left => 600, -onClick => 'Button_Clicked', ); $Main->AddButton($Button); #################################### #################################### sub Button_Clicked { my ($ButtonClicked, @other_params) = @_; my $ButtonName = $ButtonClicked->{-name}; ### $ButtonName is now ready for use :) ### } ##################################### Thanks, Doug The first item passed into the onClick subroutine is the Win32::GUI::Button object. (Note: NOT the {-name} of the object, but the blessed Perl object itself.) > ### create buttons ########################################### > $ButtonNumber = new Win32::GUI::Button($Main, > -name => "$ButtonName", > -tip => "$ButtonName", > -pos => [$posX, $posY], > -size => [15, 15], > -onClick => 'Button_Clicked', > ); > > > ### sub that all buttons go to ### > sub Button_Clicked{ > > ?????????????????????????? get button -name here. :P my ($button, @other_params) = @_; my $ButtonName = $button->{-name}; > $Main->Status3->Text("$ButtonName");## display button name in status bar > } > ######################################################### I can't recall off the top of my head what the other params are, but the docs should say. (And if all you want is the name, they are not important.) |
From: Glenn L. <gl...@ne...> - 2008-03-21 17:47:11
|
On approximately 3/21/2008 4:49 AM, came the following characters from the keyboard of Doug Hoffman: > I have been trying to understand how to get the -name of a button that > was clicked by the -onClick event, at the subroutine. > > I have read the win32::Gui docs over and over, read several post here > and elsewhere, but I still don't get it yet. :) > Please bear with me, I am trying to learn, but you know how that goes. > You don't get it and then all of a sudden it's all perfectly clear and > you wonder why you thought it was that difficult to begin with. My > brain seems to work really well by looking at working examples and > then figuring out how things work, but I haven't found a written > working example of this on the web so far and I didn't see an example > in the win32::gui folders in my perl install. > > Anywho. here is what I have, please be gentle :) > > I am creating a bunch of buttons on the fly from an array that is read > from a file. > All the buttons go to the same subroutine > At the subroutine I want to know the -name of the button that was > pressed and then go from there once I know the button -name. > I have no problem getting all the buttons to display and go to the > sub, the code all seems to work fine. > > Here's the basics of the button code and the button onClick sub > $Main is my window > $ButtonName comes from an array using a foreach loop and is a unique name > $ButtonNumber comes from an array and is a unique name but not the > same as $ButtonName > > ### create buttons ########################################### > $ButtonNumber = new Win32::GUI::Button($Main, > -name => "$ButtonName", > -tip => "$ButtonName", > -pos => [$posX, $posY], > -size => [15, 15], > -onClick => 'Button_Clicked', > ); > > > ### sub that all buttons go to ### > sub Button_Clicked{ > > ?????????????????????????? get button -name here. :P my $obj = shift; # try this? Untested... $ButtonName = $obj{-name}; > > $Main->Status3->Text("$ButtonName");## display button name in status bar > } > ######################################################### > > I have read this a million times but don't understand how to proceed. > "The first parameter passed to the subroutine is a reference to the > object on which the event occured." > That's where I am lost, *how exactly* do I get the first parameter > (-name) in the form of a scalar? > Can anyone help me with a bit of code in where my question marks are > so I can get a handle on this and stop pulling out my hair. :) > > Thanks so much for any assistance > Doug > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > http://perl-win32-gui.sourceforge.net/ |
From: Glenn W M. <gwm...@gm...> - 2008-03-21 17:41:08
|
Doug, That will work, but it breaks one of the golden rules of OO programming: don't access internal object data directly. Of course, it doesn't help that there isn't a 'Name' method! The same applies to the window handle {-handle}, incidentally. A more purist approach would be to use the UserData method, something like this: ################################################################## use strict; use Win32::GUI(); my $obMW = new Win32::GUI::Window( -name => 'Main', -size => [200,200], -text => 'Main', ); $obMW->AddButton( -name => 'Button1', -pos => [10,10], -size => [75,23], -text => 'Button1', -onClick => sub { Win32::MsgBox("You just clicked ".$_[0]->UserData) }, ); $obMW->Button1->UserData('Button1'); $obMW->AddButton( -name => 'Button2', -pos => [10,50], -size => [75,23], -text => 'Button2', -onClick => sub { Win32::MsgBox("You just clicked ".$_[0]->UserData()) }, ); $obMW->Button2->UserData('Button2'); $obMW->Show(); Win32::GUI::Dialog(); ####################################################################### That won't work for the handle, though, as we don't have it at control creation time. Perhaps we should add 'Name' and 'Handle' methods to the module? Glenn _____ From: per...@li... [mailto:per...@li...] On Behalf Of Doug Hoffman Sent: 21 March 2008 14:23 To: per...@li... Subject: Re: [perl-win32-gui-users] Button onClick event Thanks to all who replied. Here is the code that I received. my ($ButtonClicked, @other_params) = @_; my $ButtonName = $ButtonClicked->{-name}; Thanks to Sean for the email He was nice enough to explain the mechanics of the code above and how it fetches the button -name Here's the button add and button_click sub for all who may want it. ### add button ######################### my $Button = new Win32::GUI::Button($Main, -name => "Test", -tip => "Test", -width => 15, -height => 15, -left => 600, -onClick => 'Button_Clicked', ); $Main->AddButton($Button); #################################### #################################### sub Button_Clicked { my ($ButtonClicked, @other_params) = @_; my $ButtonName = $ButtonClicked->{-name}; ### $ButtonName is now ready for use :) ### } ##################################### Thanks, Doug The first item passed into the onClick subroutine is the Win32::GUI::Button object. (Note: NOT the {-name} of the object, but the blessed Perl object itself.) > ### create buttons ########################################### > $ButtonNumber = new Win32::GUI::Button($Main, > -name => "$ButtonName", > -tip => "$ButtonName", > -pos => [$posX, $posY], > -size => [15, 15], > -onClick => 'Button_Clicked', > ); > > > ### sub that all buttons go to ### > sub Button_Clicked{ > > ?????????????????????????? get button -name here. :P my ($button, @other_params) = @_; my $ButtonName = $button->{-name}; > $Main->Status3->Text("$ButtonName");## display button name in status bar > } > ######################################################### I can't recall off the top of my head what the other params are, but the docs should say. (And if all you want is the name, they are not important.) |
From: Doug H. <hof...@ci...> - 2008-03-21 17:23:17
|
Thanks to all who replied. Here is the code that I received. my ($ButtonClicked, @other_params) = @_; my $ButtonName = $ButtonClicked->{-name}; Thanks to Sean for the email He was nice enough to explain the mechanics of the code above and how it fetches the button -name Here's the button add and button_click sub for all who may want it. ### add button ######################### my $Button = new Win32::GUI::Button($Main, -name => "Test", -tip => "Test", -width => 15, -height => 15, -left => 600, -onClick => 'Button_Clicked', ); $Main->AddButton($Button); #################################### #################################### sub Button_Clicked { my ($ButtonClicked, @other_params) = @_; my $ButtonName = $ButtonClicked->{-name}; ### $ButtonName is now ready for use :) ### } ##################################### Thanks, Doug The first item passed into the onClick subroutine is the Win32::GUI::Button object. (Note: NOT the {-name} of the object, but the blessed Perl object itself.) > ### create buttons ########################################### > $ButtonNumber = new Win32::GUI::Button($Main, > -name => "$ButtonName", > -tip => "$ButtonName", > -pos => [$posX, $posY], > -size => [15, 15], > -onClick => 'Button_Clicked', > ); > > > ### sub that all buttons go to ### > sub Button_Clicked{ > > ?????????????????????????? get button -name here. :P my ($button, @other_params) = @_; my $ButtonName = $button->{-name}; > $Main->Status3->Text("$ButtonName");## display button name in status bar > } > ######################################################### I can't recall off the top of my head what the other params are, but the docs should say. (And if all you want is the name, they are not important.) |
From: Jeremy W. <jez...@ho...> - 2008-03-21 17:04:53
|
Hi, I didn't test the below, but it should help. You need to do something like: sub Button_Clicked{ my $self = shift; #$self now contains the button object - so you can call methods on it... print $self->Text(); $Main->Status3->Text($self->Name); #not sure if there is a method called name... } Cheers, Jeremy. ________________________________ From: hof...@ci... To: per...@li... Date: Fri, 21 Mar 2008 07:49:03 -0400 Subject: [perl-win32-gui-users] Button onClick event, how to get button -name I have been trying to understand how to get the -name of a button that was clicked by the -onClick event, at the subroutine. I have read the win32::Gui docs over and over, read several post here and elsewhere, but I still don't get it yet. :) Please bear with me, I am trying to learn, but you know how that goes. You don't get it and then all of a sudden it's all perfectly clear and you wonder why you thought it was that difficult to begin with. My brain seems to work really well by looking at working examples and then figuring out how things work, but I haven't found a written working example of this on the web so far and I didn't see an example in the win32::gui folders in my perl install. Anywho. here is what I have, please be gentle :) I am creating a bunch of buttons on the fly from an array that is read from a file. All the buttons go to the same subroutine At the subroutine I want to know the -name of the button that was pressed and then go from there once I know the button -name. I have no problem getting all the buttons to display and go to the sub, the code all seems to work fine. Here's the basics of the button code and the button onClick sub $Main is my window $ButtonName comes from an array using a foreach loop and is a unique name $ButtonNumber comes from an array and is a unique name but not the same as $ButtonName ### create buttons ########################################### $ButtonNumber = new Win32::GUI::Button($Main, -name => "$ButtonName", -tip => "$ButtonName", -pos => [$posX, $posY], -size => [15, 15], -onClick => 'Button_Clicked', ); ### sub that all buttons go to ### sub Button_Clicked{ ?????????????????????????? get button -name here. :P $Main->Status3->Text("$ButtonName");## display button name in status bar } ######################################################### I have read this a million times but don't understand how to proceed. "The first parameter passed to the subroutine is a reference to the object on which the event occured." That's where I am lost, how exactly do I get the first parameter (-name) in the form of a scalar? Can anyone help me with a bit of code in where my question marks are so I can get a handle on this and stop pulling out my hair. :) Thanks so much for any assistance Doug _________________________________________________________________ Welcome to the next generation of Windows Live http://www.windowslive.co.uk/get-live |
From: Doug H. <hof...@ci...> - 2008-03-21 11:49:20
|
I have been trying to understand how to get the -name of a button that was clicked by the -onClick event, at the subroutine. I have read the win32::Gui docs over and over, read several post here and elsewhere, but I still don't get it yet. :) Please bear with me, I am trying to learn, but you know how that goes. You don't get it and then all of a sudden it's all perfectly clear and you wonder why you thought it was that difficult to begin with. My brain seems to work really well by looking at working examples and then figuring out how things work, but I haven't found a written working example of this on the web so far and I didn't see an example in the win32::gui folders in my perl install. Anywho. here is what I have, please be gentle :) I am creating a bunch of buttons on the fly from an array that is read from a file. All the buttons go to the same subroutine At the subroutine I want to know the -name of the button that was pressed and then go from there once I know the button -name. I have no problem getting all the buttons to display and go to the sub, the code all seems to work fine. Here's the basics of the button code and the button onClick sub $Main is my window $ButtonName comes from an array using a foreach loop and is a unique name $ButtonNumber comes from an array and is a unique name but not the same as $ButtonName ### create buttons ########################################### $ButtonNumber = new Win32::GUI::Button($Main, -name => "$ButtonName", -tip => "$ButtonName", -pos => [$posX, $posY], -size => [15, 15], -onClick => 'Button_Clicked', ); ### sub that all buttons go to ### sub Button_Clicked{ ?????????????????????????? get button -name here. :P $Main->Status3->Text("$ButtonName");## display button name in status bar } ######################################################### I have read this a million times but don't understand how to proceed. "The first parameter passed to the subroutine is a reference to the object on which the event occured." That's where I am lost, how exactly do I get the first parameter (-name) in the form of a scalar? Can anyone help me with a bit of code in where my question marks are so I can get a handle on this and stop pulling out my hair. :) Thanks so much for any assistance Doug |
From: M2U G. <m2u...@un...> - 2008-03-08 18:40:27
|
Hi John, first of all it must be $file = Win32::GUI::GetSaveFileName(...); instead of $file = GUI::GetSaveFileName(...); Further I'm not really understanding what you're trying to do with the line my $file = "Untitled\0" . ' ' x 256;; Perhaps it's just a typo but it crashes the interpreter. I modified these lines and added some basic stuff in the following sample code: # --- SAMPLE START --- #!/usr/bin/perl use strict; use warnings; use Win32::GUI qw(); my $window_main = Win32::GUI::Window->new( -name => 'window_main', -size => [320, 240], -title => 'CmnDlg - Save As', ); $window_main->Show(); my $file = 'dummy.txt'; my $directory = 'C:/'; # Save as file dialog box, show files with *.txt extension, in messages folder $file = Win32::GUI::GetSaveFileName( -owner => $window_main, -title => 'Save As', -directory => $directory, -filter => ['Text files', '*.txt', 'All files', '*.*'], -file => $file, ); # --- SAMPLE END --- On my machine (Windows Vista 6.0.6000) it looks perfectly fine with all usual fields and controls. I hope this helps to fix your code, otherwise posting a little more of your code could help to find the problem... Best regards, Matthias |
From: Jeremy W. <jez...@ho...> - 2008-03-07 18:37:30
|
Hi, What version of Win32::GUI and what version of Perl? Cheers, Jeremy. > From: jo...@jo... > To: per...@li... > Date: Fri, 7 Mar 2008 10:59:32 -0800 > Subject: [perl-win32-gui-users] File Save with Vista > > I have a program that uses Win32::GUI::GetSaveFileName to open a "Save As" > dialog window. In win98 and XP it works fine. With Vista the "File Name" > and "Save As Type" text fields are missing and do not appear in the dialog > window. Any ideas on how to get these to appear with Vista? Using Vista > Home Premium version. Here's my code that fails with Vista... > > # Set up directory and file name > my $file = "Untitled\0" . ' ' x 256;; > my $directory = $cnst_graphics_directory ; > > # Save as file dialog box, show files with *.txt extension, in messages > folder > $file = GUI::GetSaveFileName > ( > -owner => $window_graphics , > -title => 'Save As' , > -directory => $directory , > -filter => [ 'Text files' , '*.txt' , 'All files' , '*.*' ] , > -file => $file > ) ; > > Many thanks in advance for your help. > > John > jo...@jo... > 801 815 9265 > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > http://perl-win32-gui.sourceforge.net/ _________________________________________________________________ Telly addicts unite! http://www.searchgamesbox.com/tvtown.shtml |
From: John W. <jo...@jo...> - 2008-03-07 16:53:06
|
I have a program that uses Win32::GUI::GetSaveFileName to open a "Save As" dialog window. In win98 and XP it works fine. With Vista the "File Name" and "Save As Type" text fields are missing and do not appear in the dialog window. Any ideas on how to get these to appear with Vista? Using Vista Home Premium version. Here's my code that fails with Vista... # Set up directory and file name my $file = "Untitled\0" . ' ' x 256;; my $directory = $cnst_graphics_directory ; # Save as file dialog box, show files with *.txt extension, in messages folder $file = GUI::GetSaveFileName ( -owner => $window_graphics , -title => 'Save As' , -directory => $directory , -filter => [ 'Text files' , '*.txt' , 'All files' , '*.*' ] , -file => $file ) ; Many thanks in advance for your help. John jo...@jo... 801 815 9265 |
From: Cloud S. <tha...@ho...> - 2008-03-05 14:15:42
|
Robert May-6 wrote: > > On 21/02/2008, Cloud Strife <tha...@ho...> wrote: >> >> I'm tried to compile Win32 GUI 1.06 for Active Perl 5.10 x64 on Windows >> XP >> Professional 64 bit Edition (Using Platform SDK and Windows SDK v6.0). >> After >> failing many times, it was successfully done. But AxWindow and Grid >> have >> problems. I'm trying to fix this when I have time. >> >> This is Active Perl PPM 5.10 and Source Distribution. >> >> PPM: >> >> http://rapidshare.de/files/38625281/Win32-GUI-1.06-AMD64-PPM-5.10.rar.html >> SRC: http://rapidshare.de/files/38627491/Win32-GUI-1.06_x64.rar.html > > Thank you for this. When I get time I will look at integrating your > changes into the main codebase. Are you having any troubles once you > have made these changes, as I know there are many place where pointer > are stored in DWORDs and LONGs (or at least cast through them), which > I would have though would cause problems on Win64?? > > Regards, > Rob. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > http://perl-win32-gui.sourceforge.net/ > > I don't have any problem (Except AxWindow and Grid). But, while compiling, many warnings keep popping up about pointer cast different variable types. Sorry for my English. I hope you understand. Regards, Cloud Strife. -- View this message in context: http://www.nabble.com/Win32-GUI-1.06-PPM-5.10-x64-and-Source-Distribution-tp15590753p15850622.html Sent from the perl-win32-gui-users mailing list archive at Nabble.com. |
From: Robert M. <rob...@us...> - 2008-03-03 18:31:17
|
On 01/03/2008, Bhupendra G J <b0...@fr...> wrote: > I wanna get the list of processes and the following function in WIn32 Gui > package is being used. > > Win32::PerfLib::GetCounterNames('', \%counter); > > On windows xp, am getting the process list but on vista this subroutine > doesn't return any value. Is there any way to get process list on vista > using Win32 GUI package. > > PS: Perl version 5.8.8 is used. This is the mailing list for the Win32::GUI package, not Win32::PerfLib. Win32::PerfLib is a part of libwin32. The README for libwin32 says: : Welcome to libwin32 version 0.28. : : All discussion of development / maintenance of the libwin32 package : should happen on the lib...@pe... mailing list. You can : subscribe by sending an empty email message to: : : lib...@pe... : : An NNTP archive of previous messages is available from: : : http://www.nntp.perl.org/group/perl.libwin32 : : Please report any bugs or enhancement requests to the CPAN : request tracker at: : : http://rt.cpan.org/NoAuth/Bugs.html?Dist=libwin32 Can I suggest that you try there instead. Regards, Rob. |
From: Robert M. <rob...@us...> - 2008-03-03 18:22:56
|
On 24/02/2008, M2U Germany <m2u...@un...> wrote: > On Thursday, February 14, 2008 6:27 PM Robert May wrote: > > I'd be interested in the solution to this! > > > > With the code below I see the toolbar jumping from 1 to 3 rows, > > despite the fact that > > the buttons only appear on 2 rows, and except for when there is only > > one row, the number > > of rows is always one too big. > > > > Nevertheless I reconsidered your example code, Rob. I finally found the > problem causing the wrong dimensions and row counts: we had set the state > constant for the seperator to "TBSTATE_ENABLED" but in fact this doesn't > make much sense because a "TBSTYLE_SEP" button can't be disabled, right? So > I just replaced "TBSTATE_ENABLED" with "0" and all strange behaviour > disappeared. This is probably not a really neat solution and I think there > might be a constant specified for this purpose. "TBSTATE_INDETERMINATE" is a > good candidate, isn't it? It works, too. Interesting. That change doesn't fix the problem for me. can you post the exact code you are using so I can confirm that I'm understanding what you say exactly. > > Of course I'm not as nearly into Win32::GUI programming > internals as you and probably most other members of this list are... so I > can only guess that using "TBSTATE_ENABLED" on a separator button causes the > toolbar sizing routines to *think* of it as a normal button with comparable > dimension needs and therefore to wrap this (imaginary and obviously not > displayed) space into the next line. As far as I am aware a 'button' of type TB_SEP should completely ignore the state, and it shouldn't make any difference what state you set. I can't see any difference myself. > Whatever the exact reason may be, the solution shown above seems to work. > Main conclusion: no bug to be eliminated... hooray! I don't think this is a bug in Win32::GUI - my gut feeling is that it is the behaviour of the underlying Win32 toolbar control, but I'd be interested in seeing a working solution. Cheers, Rob. |
From: Robert M. <ro...@th...> - 2008-03-03 18:17:42
|
On 21/02/2008, Cloud Strife <tha...@ho...> wrote: > > I'm tried to compile Win32 GUI 1.06 for Active Perl 5.10 x64 on Windows XP > Professional 64 bit Edition (Using Platform SDK and Windows SDK v6.0). After > failing many times, it was successfully done. But AxWindow and Grid have > problems. I'm trying to fix this when I have time. > > This is Active Perl PPM 5.10 and Source Distribution. > > PPM: > http://rapidshare.de/files/38625281/Win32-GUI-1.06-AMD64-PPM-5.10.rar.html > SRC: http://rapidshare.de/files/38627491/Win32-GUI-1.06_x64.rar.html Thank you for this. When I get time I will look at integrating your changes into the main codebase. Are you having any troubles once you have made these changes, as I know there are many place where pointer are stored in DWORDs and LONGs (or at least cast through them), which I would have though would cause problems on Win64?? Regards, Rob. |
From: Robert M. <ro...@th...> - 2008-03-03 18:13:24
|
On 21/02/2008, David Christensen <dpc...@ho...> wrote: > perl-win32-gui-users: > > I'm a Win32::GUI newbie who went through the tutorials the other night: > > http://perl-win32-gui.sourceforge.net/cgi-bin/docs.cgi?doc=tutorial > > and was shocked to see: > > 1. No "use strict" nor "use warnings". If you look at the tutorial demo code distributed with Win32::GUI (run win32-gui-demos from a cmd prompt) you'll see that it is all strict and warnings safe. There is a line to be drawn somewhere with respect to clarity of the documentation and 'correctness'. We'll never satify everyone with the style used, and so I have tried to err on the side of keeping the task at hand clear. This is not supposed to be a tutorial in good perl coding style, but a tutorial showing the Win32::GUI concepts. Patches are always welcome if you think you can make things clearer. > 2. The scripts used global variables to pass around references to the > windows, controls, etc.. Again, this is one possible style. Possibly not a good one, but it makes it very clear what is being done. I didn't write the tutorials, but have inherited their maintainance based on the lack of anyone else willing to do it. Again, patches welcome. > 3. There were no sender or eventargs arguments. Before this email I wasn't even aware what these things were. Remember this is Perl, not some MS language, so you shouldn't expect the idioms to be the same. There is more than enough support within Win32::GUI to provide an interface like this if you'd like to invest the time in creating all the necessary objects, but there will be a speed and memory hit from doing so (although it's probably not very significant). I think, more importantly, the procedural interface with the parameters decoded is more familiar to perl programmers. > (Not even a $self arg?) RTFM, I don't see them either. You probably want to read about the differences between the OEM and NEM event models (although there's not much in the docs, the samples provide quite a lot of material, as does searching the list archives). > Am I missing something? I was looking for an OO GUI toolkit in Perl. I > intend to build an application that will feature pop-up forms for > editing objects persisted in a database. My idea is to create a class > and a table for each object type. The class includes a method to create > and display a window for editing that type of object. When the user > needs to create/ edit an object, I create an object, stuff it/ get it > stuffed with data, and/or create/ display the editor window. The user > may have many such windows open at the same time, including multiple > windows from the same class. When the user interacts with the windows > and controls, the event handlers need to be able to find the right > object. Microsoft's "sender" argument solves this need nicely. > Microsoft's "eventargs" argument solves other needs nicely. Does > Win32::GUI have equivalents? Yes, it does. If the other replies have not helped you find the right direction, then please post back and we'll see what we can do to help you - there's nothing very hard if you're familiar with perl (and, in some cases, the Win32 API). Regards, Rob. > > > TIA, > > David > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > http://perl-win32-gui.sourceforge.net/ > -- Please update your address book with my new email address: ro...@th... |
From: Bhupendra G J <b0...@fr...> - 2008-03-01 07:32:58
|
Hi, I wanna get the list of processes and the following function in WIn32 Gui package is being used. Win32::PerfLib::GetCounterNames('', \%counter); On windows xp, am getting the process list but on vista this subroutine doesn't return any value. Is there any way to get process list on vista using Win32 GUI package. PS: Perl version 5.8.8 is used. |
From: zak <cho...@gm...> - 2008-02-29 15:57:30
|
hi gui builder by David Hiltz "gb109" wich you can download from: ftp://ftp.wh.whoi.edu/pub/gb109.zip does not run correctly in perl 5.8-5.10 using their appropriate win32-gui i have tried perl 5.6 with win-api and an old win32-gui, and it is stable , so you can design small forms and save them , after that you can add your code, and any corrections, and run it in perl 5.8...5.10 because it is hard to switch to perl 5.6 to run the program, i have used pdk 6 to convert the gb.pl file to the executable gb.exe so to play with a small number (but important) of win32-gui toys just run the gb.exe, and please keep this file it its folder sometimes we do not see the toolbar buttons, i have found that just double click the file widgets.bmp to open it will correct the problem. strange. download the new gb109.rar file from: http://www.2shared.com/file/2916295/215f9202/gb109.html regards zak |
From: M2U G. <m2u...@un...> - 2008-02-25 15:07:17
|
On Thursday, February 14, 2008 6:27 PM Robert May wrote: > I'd be interested in the solution to this! I thought that the > problem was going > to be the fact that the code got the toolbar height before calling > Autosize(), but > changing that didn't fix it for me. > > With the code below I see the toolbar jumping from 1 to 3 rows, > despite the fact that > the buttons only appear on 2 rows, and except for when there is only > one row, the number > of rows is always one too big. > > The problem goes away if I make the seperator a real button. WTF? This problem didn't affect my program any longer because its rebars have only one row of toolbar buttons and they aren't allowed to wrap anyway. Nevertheless I reconsidered your example code, Rob. I finally found the problem causing the wrong dimensions and row counts: we had set the state constant for the seperator to "TBSTATE_ENABLED" but in fact this doesn't make much sense because a "TBSTYLE_SEP" button can't be disabled, right? So I just replaced "TBSTATE_ENABLED" with "0" and all strange behaviour disappeared. This is probably not a really neat solution and I think there might be a constant specified for this purpose. "TBSTATE_INDETERMINATE" is a good candidate, isn't it? It works, too. Of course I'm not as nearly into Win32::GUI programming internals as you and probably most other members of this list are... so I can only guess that using "TBSTATE_ENABLED" on a separator button causes the toolbar sizing routines to *think* of it as a normal button with comparable dimension needs and therefore to wrap this (imaginary and obviosly not displayed) space into the next line. Whatever the exact reason may be, the solution shown above seems to work. Main conclusion: no bug to be eliminated... hooray! Best regards, Matthias |
From: Robert M. <rob...@us...> - 2008-02-23 21:33:03
|
On 22/02/2008, Gareth John <ga...@eg...> wrote: > I'm using Perl v5.10.0 and Win32::GUI 1.0.6 - I'm trying to import the > following constants: > > LVHT_ABOVE > LVHT_BELOW > LVHT_NOWHERE > LVHT_ONITEMICON > LVHT_ONITEMLABEL > LVHT_ONITEMSTATEICON > LVHT_TORIGHT > LVHT_TOLEFT > > but they don't seem to be exported by Win32::GUI::Constants. Can anyone > tell me what I need to do to get these constants? Thank you for the report. I will add these constants to the next release. For now you'll need to define the constants yourself. Try something like this: sub LVHT_NOWHERE() {0x0001} sub LVHT_ONITEMICON() {0x0002} sub LVHT_ONITEMLABEL() {0x0004} sub LVHT_ONITEMSTATEICON() {0x0008} sub LVHT_ONITEM() {0x000E} sub LVHT_ABOVE() {0x0008} sub LVHT_BELOW() {0x0010} sub LVHT_TORIGHT() {0x0020} sub LVHT_TOLEFT() {0x0040} Regards, Rob. |
From: David C. <dpc...@ho...> - 2008-02-23 06:10:03
|
jez_white wrote: > Win32::GUI supports two event modles OEM (old event model) and NEM > (new event model). OEM is like visual basic, with the control name > and the event name. So if a button was called "hello" and the button > was clicked, the sub hello_Click would be called. OEM is only sutible > for simple scripts But, apparently, does not provide VB-like sender and eventargs arguments to the event handler (?). > With NEM you pass the reference of the sub that you want to run in > response to an event (this makes NEM faster). > To some exent a NEM event is like a method being called on that > control and as such, the first parm being passed is the control. > It should be documented in the NEM section. > Does that help? Again no win32::GUI on this box..... Okay, thanks for the pointer. I was not aware of OEM and NEM: http://perl-win32-gui.sourceforge.net/cgi-bin/docs.cgi?doc=reference-opt ions Thank you, David |
From: oohayf o. <ooh...@ya...> - 2008-02-22 21:00:44
|
hello, having problem below for quite some time and no working solution... could someone please help? so the gui that i'm working with, currently to make a selection from a combobox, i would do a dropdown, select by index, then send TAB key and the gui would stick and setting works: [...] SendMessage($hnd, 0x014F, 1, 0); #showdropdown of combobox SelComboItem($hnd, $index); #select combobox by index number Sendkeys ("{TAB}") [...] problem is with a different gui, the above don't work. And the only to make the gui stick and settings valid is: to do a mouse click, then an image in a static class would change. i guess what would be best is to do a mouse click on the dropdown combobox and click on the desired item. i've tried mouseclick() but this don't work. does anyone have any suggestion or know of any win32 gui function that will solve this problem? thanks! --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. |
From: <jez...@ho...> - 2008-02-22 10:25:54
|
> To do this have a look at the UserData method. It allows you to > associate data to a window. When you use NEM events the first parm is > the object that the event fired on. Say for example you have a button > on a form, and you have many instances of that form your even handler > would look like: > My $self=shift; #the button object > My $parent = $self->parent; #the parent window > My $object = $parent->UserData; #the instance data for the window I guessed at a solution like that, but didn't see $self in the documentation for Button_Click(): http://perl-win32-gui.sourceforge.net/cgi-bin/docs.cgi?doc=button Where is this documented? ________ It should be documented in the NEM section. Win32::GUI supports two event modles OEM (old event model) and NEM (new event model). OEM is like visual basic, with the control name and the event name. So if a button was called "hello" and the button was clicked, the sub hello_Click would be called. OEM is only sutible for simple scripts With NEM you pass the reference of the sub that you want to run in response to an event (this makes NEM faster). To some exent a NEM event is like a method being called on that control and as such, the first parm being passed is the control. Does that help? Again no win32::GUI on this box..... Cheers, jez ----------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Perl-Win32-GUI-Users mailing list Per...@li... https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users http://perl-win32-gui.sourceforge.net/ _ |
From: David C. <dpc...@ho...> - 2008-02-22 06:54:34
|
Glenn Linderman wrote: > #3. I've read bunches of Windows API documentation, and have never > found anything called "sender", "eventargs", or "self". You must be > reading stuff at some higher level of abstraction. http://search.cpan.org/~robertmay/Win32-GUI-1.06/docs/GUI/UserGuide/Read me.pod "Win32::GUI is a Win32-platform native graphical user interface toolkit for perl. Basically, it's an XS implementation of most of the functions found in user32.dll and gdi32.dll, with an object oriented perl interface and an event-based dialog model that mimic the functionality of visual basic." I was expecting something like Visual Basic (although I prefer C#): http://msdn2.microsoft.com/en-us/library/system.windows.forms.control.cl ick(VS.71).aspx jez_whit wrote: > To do this have a look at the UserData method. It allows you to > associate data to a window. When you use NEM events the first parm is > the object that the event fired on. Say for example you have a button > on a form, and you have many instances of that form your even handler > would look like: > My $self=shift; #the button object > My $parent = $self->parent; #the parent window > My $object = $parent->UserData; #the instance data for the window I guessed at a solution like that, but didn't see $self in the documentation for Button_Click(): http://perl-win32-gui.sourceforge.net/cgi-bin/docs.cgi?doc=button Where is this documented? David |