Re: Bug: Tk::Entry 804.027 validate?

[zentara]

<2 cents> First of all, my immediate reaction is that using validate with textvariable, is asking for trouble..... but your point about existing scripts breaking is valid.

Validate is intended for inspecting the value of something entered into the Entry widget. Some tidbits from the perldoc:

The characters to be added (or deleted). This will be "undef" if validation is due to focus, explcit call to validate or if change is due to "-textvariable" changing.

So you have undef values poping in there, when textvariable change occurs.

In general, the textVariable and validateCommand can be dangerous to mix. If you try set the textVariable to something that the validateCommand will not accept it will be set back to the value of the entry widget. Using the textVariable for readonly purposes will never cause problems.

So my advice is to redesign your script, to check for values in another way, rather than relying on the validate callback.

Why design something to use something which may go undef? You could just as easily put the value-check in the button callback( or wherever you set $entryText ).

If you really want to pursue this, you should probably ask on comp.lang.perl.tk. where one of the Tk internals experts may know something. </2cents>

[strat]

Hello zentara,

The reason why I want to do it that way is Tk::EntryCheck. This module that allows you to control which chars may be entered and up to which lenght into a Tk::Entry widget. I wrote this module because I prefer preventing invalid or too many chars to letting the user insert everything and then checking it and rising errors and the like.

Well, I now try to rewrite this module using Tie::Watch.

[zentara]

Hi, the mention of Tie::Watch, triggered my memories of Tk::Trace( which may work better with Tk). It's only glitch, is that you need to pre-declare package Tk and add Tk::Trace. See Simple Tk Gauge