Re: [TCLCORE] CFV on small high-prio TIPs

[Joe E. <jen...@fl...>]

Donal K. Fellows wrote:

>   TIP #210: Add 'tempname' Subcommand to 'file'

TIP#210: YES.

>   TIP #307: Make TclTransferResult() Public
>   TIP #337: Make TclBackgroundException() Public
>   TIP #338: Embedder Access to Startup Scripts of *_Main()

TIP #307: YES.
TIP #337: YES.
TIP #338: YES.

Useful stuff from the private interface that deserves to be public.

>   TIP #336: Supported Access To interp->errorline

TIP #336: YES.

Opaque Tcl_Interp *s at last!

>   TIP #306: Auto-Naming Widgets

TIP#306: NO.

This one does not play nicely with third-party widget sets
or with megawidget packages.  For the former, it places additional
constraints on widget constructors.  I have no idea how
it will interact with the latter, though I suspect the answer
is "not very well".

I did a quick spot-check: with the proposed patch, tktable
and the tile widgets automagically start supporting autonaming --
but only by accident -- while canvas3d, all BLT widgets, and
tkhtml will break in new and exciting ways if you try to use
the autonaming feature.

I don't believe the proposed feature -- a minor convenience
that only works some of the time -- is worth adding.

>   TIP #284: New 'invoke' and 'namespace invoke' Commands

TIP#284: SEND IT BACK.

I don't think this one got the API right, and it
doesn't appear to add any new functionality.
If "SEND IT BACK" is not a legal vote, then:

TIP#284: NO.


I need to think about these some more:

>   TIP #335: An API for Detecting Active Interpreters

I thought this was going to be amended to specify
Tcl_IsInterpActive() instead of Tcl_GetNumLevels().
The title of the TIP changed, but not the specification?

TIP#335: TENTATIVE NO.  If it's amended to specify
Tcl_IsInterpActive() or something similar, then YES.

>   TIP #171: Change Default <MouseWheel> Bindings Behavior

Definitely need to look at this some more.  It just
doesn't smell right to me.  One thing in particular:
instead of going through all sorts of rigamarole at
the scripting level to redirect MouseWheel events
to the widget under the pointer on Windows, wouldn't
it make more sense to simply not redirect them to
the focus window in the first place (see tkEvent.c,
InvokeFocusHandlers)?  That's how it's currently done
on OSX.  I suspect it also interferes with some of
the ttk::* widgets.


>   TIP #197: Text Widget Persistant Cursor
>   TIP #238: Fire Event when Widget Created

Don't know yet.


--Joe English

  jen...@fl...