I've been playing around with tooltips this weekend, trying to get them to
work, but I kept getting an error message that tells me my tooltip object is
undefined--well, the variable that is supposed to refer to my tooltip object
is undefined, which means my tooltip did not get created. I traced the
problem as far as I could, and this is what I found:
In the Tooltip package, I found these two lines:
my $parent = $_[0];
my $new = Win32::GUI->_new(Win32::GUI::constant("WIN32__GUI__TOOLTIP", 0),
@_);
The first should have $_[1], as it is currently assigning
"Win32::GUI::Tooltip" to $parent, rather than the actual name of the parent
object. (That is not actually causing any problems right now, but it
presumably will when the real problem is fixed.)
The real problem is that Win32::GUI->_new is returning undef, which is why I
get that error message. I looked in Win32::GUI->_new, and found that it is
returning undef due to the following line:
my $handle = Win32::GUI::Create($self, $type, @input);
It returns undef because nothing gets assigned to $handle. Unfortunately,
that line is calling something from either GUI.dll or GUI.lib, which I can't
do anything about (unless I learn C++ and get a compiler).
I guess I'm just wondering where completion of Tooltip functionality is on
the priority scale. (I realize that the memory leak is probably taking up
most of the time right now, so it's not a big deal--I can probably fake it
by creating a label and manipulating the -visible option, and it's not even
essential, anyway.)
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
