Re: [perl-win32-gui-users] PALINDROME Date/Time TRIVIA
Hiya I think you're right.. Dunno, they love giving hype to small stuff, technically 2001 was the beginning of the new millenium, however they hyped 2000 as the big thing. Later, Ahmed. -Original Message- From: Eric Hansen <[EMAIL PROTECTED]> To: perl-win32-gui-users@lists.sourceforge.net Date: Thursday, February 28, 2002 10:51 PM Subject: [perl-win32-gui-users] PALINDROME Date/Time TRIVIA Hey fello Win32:GUIers You may have heard in the media (internet, news, etc.) recently that a date/time palindrome would occur on Feb 20, 2002 at 8:02pm. Written in DDMM HHMM format as 2002 2002 2002 , reading the same forwards and backwards. From what I heard, this was the last time this would occur in history due to the 24 hour clock limitation. I also heard that the last time this occured was on Jan 10, 1001 at 10:01. Written in DDMM HHMM format as 1001 1001 1001. But after some calculating of my own on the subject, I found the following to be the case: DDMM HHMM 0110 01100110October 01, 0110 at 1:10 891 years pass till 1001 10011001January 10, 1001 at 10:01 110 years pass till November 11, at 11:11 891 years pass till 2002 20022002February 02, 2002 at 20:02 recently reported as last date/time palindrome to be seen in history 110 years pass till 2112 21122112December 21, 2112 at 21:12 actual last date/time palindrome 891 years pass till 3003 300324 hour clock limitation 110 years pass till 3113 311324 hour clock limitation I assume 2112 2112 2112 is a palindrome since it reads same both frontwards and backwards? What do you guys and gals think? Is it? Eric Hansen Dallas, TX USA _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
[perl-win32-gui-users] Waiting a result from a window
Yesterday, I resolve a question with the use of MessageBox, but now I am in
similar circumstancies, and I can't use MessageBox.
The question is:
How is possible for a script to obtain a result that can be obtained from the
user. That is to say, the script doesn't continue until the window return the
user information
For instance:
Module a: (without any $window, but Win32:Dialog still running)
...
...
a=Llibreria:moduleb:Initial(param_a,param_b)
...
...
Module b:
$window properties
Sub initial
{
...
$window->Show()
...
return (result)### In fact, I can't return until the user has entered the
necessary information
}
sub button1_click.
...
etc.
Guillem Cunillera i Wefers.
Re: [perl-win32-gui-users] Waiting a result from a window
At 10:32 2002-03-01 +0100, Guillem Cunillera Wefers wrote: The question is: How is possible for a script to obtain a result that can be obtained from the user. That is to say, the script doesn't continue until the window return the user information http://www.bahnhof.se/~johanl/perl/Win32GUI/Modalizer.pm It's not perfect, but it's a fairly decent workaround. Win32::GUI needs a real implementation of modal dialogs. /J -- --- -- -- -- -- - - - Johan LindströmSourcerer @ Boss Casinos [EMAIL PROTECTED] Latest bookmark: "The Ideahamster Organization" http://www.ideahamster.org/
Re: [perl-win32-gui-users] Win32::GUI Release 0.0.665
Frazier, Joe Jr wrote:
> > but I still don't know what to do when you just say use Win32::GUI ;-)
>
> Use old style by default. This avoids users
> having to change thier code until they are ready to totally update thier
> code.
yes, this is sure. by default the old style is used, the problem is when you
don't use it and put an -events option on something. maybe I should
process -events options *only* if you said:
use Win32::GUI Event_Model => 'byref';
otherwise they're simply ignored.
> I would probably do something simular to the way XML::SAX::* works and
> do this
>
> [...]
>
> -events => {
> Terminate => $gui->myhandler();
not quite... should be something like:
Terminate => \&{ $gui->myhandler };
arguments to -events can be:
- a subroutine name (string)
- a reference (eg. \&)
- an anonymous sub (eg. sub { .. })
BTW, I didn't understand the use of My::Package ... but maybe it's just me.
> Now, the question is, how does it work to pass in stuff such as the
> listview passing the row clicked? or do we have to handle all that
> ourselves? If this is covered in the docs(are the docs more fleshed
> out?), let me know and I will check there.
ops, sorry, I forgot to mention this :-)
for your joy (and many other's too), all NEM events pass the object they're
referring to as their first argument, while subsequent arguments are the
same as their non-NEM counterparts.
so you can do this:
$Window->AddButton(
# ...
-name => "Button1",
-onClick => sub {
my($self) = @_;
print "you clicked button: $self->{-name}\n";
},
);
and this will print out: you clicked button: Button1
an ItemClick event for a ListView would look like:
-onItemClick => sub {
my($self, $item) = @_;
# do something with $item
},
> Sorry to be a pain, but i am so excited to check this out and have a
> few questions on gotchas I have ran into in the past before migrating.
don't worry, this kind of pain is welcome :-)
cheers,
Aldo
__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;
Re: [perl-win32-gui-users] Win32::GUI Release 0.0.665
> At Thursday, 28 February 2002, Glenn wrote: > > >Now I've downloaded and compiled the new version. Boy was I surprised! jean bosco muzatsinda wrote: > > Hi, > How did you proceed to download and compile? > I'm knew to this matter of things ( win32::GUI)and I'm experiencing > some problems. > Thanks, > > Jean Although this was a private message (inappropriate) I'm replying back to the list, because there may be a number of others that have never compiled Win32::GUI, that now suddenly have the desire to. It was my first time to ever compile a perl module, but really, it isn't too hard when things are set up right, I guess, and it seems that Aldo has things set up right. The following is what I did to download and compile: Download: used web browser, went to http://data.perl.it/, found the link for the source ( http://dada.perl.it/Win32-GUI-0.0.665.tar.gz ), and fetched it to my local hard drive, I used d:\. Using cmd.exe, I Then "gunzip Win32-GUI-0.0.665.tar.gz" Then "tar xvf Win32-GUI-0.0.665.tar" Then "cd d:\Win32-GUI-0.0.665" I used my favorite text editor, emacs, to look around. It appears that although the code has been enhanced and restructured into multiple source files, that the documentation has not yet been enhanced in any way, and also not the sample code. Then I had to experiment to see how to compile. Since I'm using ActiveState's perl, which is reportedly compiled using MS VC, I figured I'd need to get that on my path. And I remembered that when I had installed MS VC, it had told me about a batch file that can put it on the path (doesn't need to be on the path when you use the MS IDE). And I remembered seeing, over and over again on various perl lists, the comment that when using MS VC, you have to use "nmake" instead of "make". And the theoretical process for installing modules is documented as the sequence of commands: perl makefile.pl make make install So I wrote the following batch file: call "c:\program files\microsoft visual studio\vc98\bin\vcvars32.bat" perl makefile.pl nmake nmake install Upon executing it from the command line prompt, where my current directory was d:\Win32-GUI-0.0.665, it seemed to do the trick. I then attempted to run a couple scripts for which I had already set up shortcuts, and lo and behold! they used the new version of Win32::GUI ! With the surprise reported earlier. -- Glenn = Remember, 84.3% of all statistics are made up on the spot.
Re: [perl-win32-gui-users] Win32::GUI Release 0.0.665
Glenn Linderman wrote: > > Now I've downloaded and compiled the new version. Boy was I surprised! Here's another surprise: When moving the cursor to the edges and corners for resizing things, the cursor doesn't change to the "usual" double-headed arrows which provide feedback to the user that they are in the right position for resizing. Resizing still works, but it is awkward because of the expectation from other programs and earlier versions of Win32::GUI that the cursor should change shape for that event. -- Glenn = Remember, 84.3% of all statistics are made up on the spot.
