> > I see you are working on menus ... the AUTOLOAD problem you
> > just fixed, but now I see my menus created flat across the
> > entire first level (instead of as submenus). Can you explain
> > what you are trying to do with that area?
Must mention 'Menu' in %ptk2tcltk hash, but I saw you already got the idea
:) (I see you fixed that)
Also I prepared a patch that also fixes "Multiplewidget" error.
this one:
@@ -1905,7 +1908,7 @@
($p, $prepl) = ($1,$2);
}
else {$prepl = $p}
- if ($j+1<=$#a) {
+ if ($j+1<=$#a && ref($a[$j+1])) {
$prepl = $a[$j+1];
splice @a, $j+1, 1;
}
>
> Along the same lines, I'm not sure that the way that
> create_widget_package and create_method_in_widget_package
> are "correct". They have different method inheritance
> behavior as the previous Tk.pm.
But it was much worse:
previously, for example Button, created all its submethods in a package
Tcl::Tk::Widget::Button
Similar to Label and some other 'standard' widgets.
All widgets that have their predeclared creation method lived in package
Tcl::Tk::Widget
And method with same names will intermix.
>
> For example, DialogBox used to get "resizable" from the
> AUTOLOAD that handled Toplevels. Now I get an error that
> that isn't a recognized method. Are only the created
> methods in a widget package then recognized? This makes
> it to hard to make renamed/megawidgets. Is there an easy
> way to correct inheritance while maintaining the
> separation you were trying to achieve?
I hope this is quite doable...
I'll see tomorrow eveing.
Yet it is obvious to have test suite for creation all required widgets.
(DialogBox must be included at the very first place).
Will do at next weekend and make another release to CPAN.
But anyone with faster test creation fu is welcomed here :)
Best regards,
Vadim.
|
