in reply to Re^3: Using Tk::Text and '<<Modified>>'
in thread Using Tk::Text and '<<Modified>>'

Among the modules I am currently using, the methods to get/set their contents, or be notified when they change, vary wildly. Eg:
... I'm sure I've missed some
This to me is inconsistent. Why isn't there a 'get()' and 'set()' for all of these, together with a standard callback option to be called when they change? They could still have all their idiocyncraciesspecialities additionally if needed.

Anyway, this is one of the major arguments that people keep giving me to try and persuade me to switch to some other GUI system, as Tks worst side.. And I keep coming across things that make me agree.

BTW, I'd prefer Tk::Text be configured more like Tk::Entry and the rest, ie a -command or something on create, instead of the extra bind command, but thats probably just because all the widgets Im currently using also work that way.

C.

  • Comment on Re^4: Using Tk::Text and '<<Modified>>'