in reply to Re: Use of break in Tkx
in thread Use of break in Tkx

:)Tkx is the worst possible option

Replies are listed 'Best First'.
Re^3: Use of break in Tkx
by Anonymous Monk on Oct 03, 2015 at 11:17 UTC
    Yes I'm slowly seeing that... I just modified the callback to subdue the error and break in the forms I've tried isn't "doing" it. Thanks for the advice
    sub custom_error_handler {} #just supresses error sub cb_entry { my $win=$_[0]; eval { $mw->g_wm_title("this is $win m8"); #this works ok #NONE OF THESE DO ANYTHING Tkx::break(); $win->break; Tkx::break(".e"); }; custom_error_handler($@) if $@; }
      Try next;
        Yes "next" did the trick. Thank you very much indeed! I lack the visibility to see how "next" is a replacement for "break" i.e. "last" seems a far more more natural replacement to end a loop. "last" certainly stopped any more bindtags being looked at but also took the interpreter out at the same time suggesting that the loop is the main message loop. It never occured to me to try and continue that loop. Once again thanks. BTW is there a best place/file I should be looking at to get your level of understanding re Tkx?
        Not sure if my response showed up as linked with the suggestion to try "next" and further help so I'm posting it again here... Your solution and further response helps a lot and as a result you have motivated me to press on with Tkx as the concept of it being a thin wrapper giving almost direct access to TK is a compelling one. >you can always write stuff in tcl, unofficially Tkx::eval('tcl source code'); That looks like a real life-saver in these sort of situations 'cos the documentation re Tk is ok. All in all...very grateful to you. Thank you!