From: Zbigniew B. <zb...@is...> - 2009-04-17 21:16:15
|
On Fri, Apr 17, 2009 at 12:39:18PM -0500, Damon Courtney wrote: >> It strikes me that an option is rather limited -- give it about 2 >> months >> and we will see reusable bits of code on the wiki that do cool things >> (like tooltips) using -cargo, and suddenly its not really available >> for "the script author" because (s)he is trying to juggle the 5 cool >> extensions that all want to use it. If I may add my "3 cents/pennies" (not sure, will it reach tcl-core list since I'm not a subscriber - please forward, if possible): I'm pretty sure, that all of you have much more experience than I have, but I would again point your attention, that such possibility has been durings years "extensively tested" in Clipper, and there wasn't any "fight for access to field". And so I think, we can trust in programmers' sanity, and it's pretty reasonable to name such fears as exaggerated. In case of doubt all you need to do is to make a quick check "still free?" before use. > it's quite easy in Tcl. I would just use a simple command trace on the > deletion of the widget. Binding to <Destroy>, as some in the original > thread had suggested, has the side-effect of being easy to wipe out by > the developer if they choose to bind <Destroy> themselves. There are people - like myself - who prefer the option, because this will make the field contents "strictly bound" to a widget. Of course, there will be still available other ways to achieve similar result (available even now) - and in my opinion that methods are less convenient, and more complicated. And because of this I decided to make this suggestion; I'm pretty sure, many will be pleased with such new possibility. -- pozdrawiam / regards Zbigniew Baniewski |