TCL 3. graphs and switching graphs about loon HOT 3 CLOSED

Adrian

Any chance of you getting to this one?

from loon.

As for invalid command name "0" for uplevel #0 [$activewidget scaleto world]", it is pretty clear:
the method "scaleto" can return 0, at least I found correct method in

The commit as well as return 0 is not an issue directly, but it looks like here and there are some code pieces with a bit confusing basic Tcl handling, for example:

I can provide a PR fixing that...

Command uplevel #0 cmd processing the command cmd at top-level,
but in case of uplevel #0 [cmd], Tcl would firstly execute cmd at current level and then the result (returned by this command) at top-level.
If command returns empty value (or does not return something at all), uplevel #0 [cmd] is comparable with uplevel #0 {}, what simply does nothing.

There are 3 "solutions" depending on expected behavior:

• either one should rewrite it as uplevel #0 [list cmd arg1 ... argN] to force execution of cmd at top-level;
• or to relocate it to event like after 0 [list cmd arg1 ... argN] to execute it retarded (as event, at top-level too)
• or even to remove uplevel #0 [ at all, so cmd arg1 ... argN only, if execution in the current level is allowed (because doing the job all the time).

For example uplevel #0 [update idletasks] is the same as update idletasks (variant 3), because update always executes pending events at top-level and always returns nothing, so uplevel #0 {} is simply called after an update (and doing really nothing there).

from loon.

thanks @sebres. @rwoldford these issues are fixed now. Please let me know if you still find some issues with switching graphs.

from loon.