I think you've found the simplest way around the problem.

Looking into the module's code, the binding is done deliberately, although it seems fairly safe to remove.

If you go into the subs (note that line 104 also calls the ButtonHack sub), you'll see the following:

# This hack is to prevent the ugliness of the arrow being depressed.
#
sub ButtonHack {
    my ($w) = @_;
    my $b = $w->Subwidget('arrow');
    if ($w->{'buttonHack'}) {
    $b->butUp;
    }
}
[download]

So, from that, it seems a purely cosmetic thing, and isn't (shouldn't be) critical to the operation of the widget at all.

Of course, I don't know how ugly the depressed arrow button is *grin* .. maybe that's a factor.

I definitely need to point out I haven't tested this, at all, it's based on looking through the module's source code. I also wouldn't even think about changing the module's code, unless it's completely necessary.

I'd suggest that the hack round the problem that you've already found and are using already is probably the best way to go. That'll certainly be the simplest and easiest-to-implement solution, not to mention helping when it comes to the future maintaining of the script.

Hope that helps ..
-- Foxcub

Random Note: It's taken a long while to get here, but this is my 100th post. Roll on 1000 ...