I'm sure I really shouldn't be responding to this. It seems an open
invitation to start trouble, and that's not truly my intent. I have to
wonder why Glen wanted to be so knit-picky on my bug report. Obviously,
there isn't a 6.xx version out there, and won't be for a long time, so how
many 0's preceed the version shouldn't matter. Of course, I was
impricise, and I'm sure that's where he was coming from, but I knew what
version I had, just not where the .'s and 0's were placed, and didn't feel
such a minor detail mattered, but excuse me for thinking on that.
Glen, I don't know if you're a developer, and thus were personally anoyed
with my report or not, or if you felt my email was a classic instance of
"what not to do" so felt obligated to use me to make an example. In
either case, I didn't appreciate it. Neither the version, nor my
description were so bad that I felt I was wasting anyone's time, and I had
looked for previous versions not long before I posted that, and was
supposed to have had an email telling me when the next updates were out
(which I haven't recieved, so thanks on that end).
If you want code, here you go:
use Win32::GUI;
my( $Window, $Bitmap );
$Window = new Win32::GUI::Window(
-name => "Window",
-top => 0,
-left => 0,
-height => 300,
-width => 300
);
$Bitmap = new Win32::GUI::Bitmap( 'image.bmp' );
$Window->AddButton(
-name => "Button",
-top => 0,
-left => 0,
-height => 300,
-width => 300,
-bitmap => $Bitmap
);
$Window->Show();
Win32::GUI::Dialog();
sub Window_Terminate {
return -1;
}
That's the code which works.
Here's the code which doesn't.
I think, it will quickly become apparent, there was no need for all this
:p
use Win32::GUI;
my( $Window, $Bitmap );
$Window = new Win32::GUI::Window(
-name => "Window",
-top => 0,
-left => 0,
-height => 300,
-width => 300
);
$Bitmap = new Win32::GUI::Bitmap( 'image.bmp' );
$Window->AddButton(
-name => "Button",
-top => 0,
-left => 0,
-height => 300,
-width => 300
);
$Window->Button->SetImage( $Bitmap );
$Window->Show();
Win32::GUI::Dialog();
sub Window_Terminate {
return -1;
}
Now, you ask why waste my time with this? No one wants to set an image
after creation of a button anyways, right?
That was a simple example, sense examples seemed to be required, to point
out what doesn't work :p
The intent of my code, which I worked with for weeks, mostly not having
images show up before I figured out what actually worked and what didn't,
was setting up a series of buttons which needed to change their images in
certain instances. I wanted to be able to use SetImage to get the buttons
to change, rather than have to destroy the button, create a new button
with the new image, etc.
Perhaps I am blowing this _way out of proportion, but I think my
description matched the code above, and was far more concise.
I won't waste your time again with reports,ough. If you're that
knit-picky, perhaps you need to find them yourself.
