Bug in a widget
in [TCL]
|
Prev: How to send a virtual event from C++
Next: TclOO: Can I execute a method from an object in the context of anotherobject?
From: Arjen Markus on 12 Apr 2010 04:56 On 12 apr, 10:51, Keith <kilowattra...(a)use-reply-to.invalid> wrote: > On Mon, 12 Apr 2010 01:48:35 -0700 (PDT), Arjen Markus > > <arjen.markus...(a)gmail.com> wrote: > >- unsetting the variable may not be enough - the trace creates it > >again > >- the best way is to first destroy the widgets and then unset the > >variables, > > otherwise they may magically reappear > > >(I learned that in a somewhat similar situation :)) > > Do you mean actually use destroy on the entry widget's path? > > destroy .widget.entry.1 > ?? I am not sure that is required, but I would to be sure Regards, Arjen
From: Keith on 12 Apr 2010 06:56 On Mon, 12 Apr 2010 01:56:19 -0700 (PDT), Arjen Markus <arjen.markus895(a)gmail.com> wrote: >On 12 apr, 10:51, Keith <kilowattra...(a)use-reply-to.invalid> wrote: >> On Mon, 12 Apr 2010 01:48:35 -0700 (PDT), Arjen Markus >> >> <arjen.markus...(a)gmail.com> wrote: >> >- unsetting the variable may not be enough - the trace creates it >> >again >> >- the best way is to first destroy the widgets and then unset the >> >variables, >> > �otherwise they may magically reappear >> >> >(I learned that in a somewhat similar situation :)) >> >> �Do you mean actually use destroy on the entry widget's path? >> >> destroy .widget.entry.1 >> ?? > >I am not sure that is required, but I would to be sure > >Regards, > >Arjen Ok I have it working properly now. Thank You.
From: Arjen Markus on 12 Apr 2010 08:17 On 12 apr, 12:56, Keith <kilowattra...(a)use-reply-to.invalid> wrote: > On Mon, 12 Apr 2010 01:56:19 -0700 (PDT), Arjen Markus > > > > > > <arjen.markus...(a)gmail.com> wrote: > >On 12 apr, 10:51, Keith <kilowattra...(a)use-reply-to.invalid> wrote: > >> On Mon, 12 Apr 2010 01:48:35 -0700 (PDT), Arjen Markus > > >> <arjen.markus...(a)gmail.com> wrote: > >> >- unsetting the variable may not be enough - the trace creates it > >> >again > >> >- the best way is to first destroy the widgets and then unset the > >> >variables, > >> > otherwise they may magically reappear > > >> >(I learned that in a somewhat similar situation :)) > > >> Do you mean actually use destroy on the entry widget's path? > > >> destroy .widget.entry.1 > >> ?? > > >I am not sure that is required, but I would to be sure > > >Regards, > > >Arjen > > Ok I have it working properly now. Thank You.- Tekst uit oorspronkelijk bericht niet weergeven - > > - Tekst uit oorspronkelijk bericht weergeven - What was the secret? Regards, Arjen
From: Keith on 12 Apr 2010 08:36 On Mon, 12 Apr 2010 05:17:19 -0700 (PDT), Arjen Markus <arjen.markus895(a)gmail.com> wrote: >On 12 apr, 12:56, Keith <kilowattra...(a)use-reply-to.invalid> wrote: >> On Mon, 12 Apr 2010 01:56:19 -0700 (PDT), Arjen Markus >> >> >> >> >> >> <arjen.markus...(a)gmail.com> wrote: >> >On 12 apr, 10:51, Keith <kilowattra...(a)use-reply-to.invalid> wrote: >> >> On Mon, 12 Apr 2010 01:48:35 -0700 (PDT), Arjen Markus >> >> >> <arjen.markus...(a)gmail.com> wrote: >> >> >- unsetting the variable may not be enough - the trace creates it >> >> >again >> >> >- the best way is to first destroy the widgets and then unset the >> >> >variables, >> >> > �otherwise they may magically reappear >> >> >> >(I learned that in a somewhat similar situation :)) >> >> >> �Do you mean actually use destroy on the entry widget's path? >> >> >> destroy .widget.entry.1 >> >> ?? >> >> >I am not sure that is required, but I would to be sure >> >> >Regards, >> >> >Arjen >> >> �Ok I have it working properly now. Thank You.- Tekst uit oorspronkelijk bericht niet weergeven - >> >> - Tekst uit oorspronkelijk bericht weergeven - > >What was the secret? > >Regards, > >Arjen Destroy the widget and then unset the variables.
From: Andreas Leitgeb on 12 Apr 2010 08:37
Keith <kilowattradio(a)use-reply-to.invalid> wrote: > grid [ frame $t.g -bg white ] -row 1 -column 0 -sticky w > lsort [set clip(hj) [array names clip2]] This lsort does nothing. Well it does something, but you ignore its result, so its as ineffective as adding 42+54 and then ignoring the sum. Either you want: (no sorting) set clip(hj) [array names clip2] or: (with sorting) set clip(hj) [lsort [array names clip2]] > lsort [set clip(hj) [array names tty]] here the same. For your problem of "phantom" widgets, add code to print out the actual contents of your "clip", "clip2" and "tty" arrays, e.g.: parray clip2 and watch the terminal or console(tkcon) Perhaps you didn't yet know, that after these two lines: array set clip2 {1 one 2 two} array set clip2 {3 three 4 four} array clip2 will contain all 4 (four!) keys, not just those two of the second "array set". Maybe you want to call "array unset clip2" at appropriate places. |