Great client!
Here's some small bits to add if you like using ^U to get rid of the text in the input widget...
Around line 541, you originally have:
$Inputfield->bind("<Return>", \&Say_Click);
$Inputfield->bind("<Control-Return>", \&Msg_Click);
$Inputfield->bind("<Tab>", \&completeName);
insert the ^U binding after the statements above:
$Inputfield->bind("<Control-u>", \&clearentrybox);
and around line 682, between the end of the
Msg_Click sub and the beginning of the
completeName sub, I put my ^U subroutine:
######################################################################
+##########
#
# clearentrybox
#
# clears the entry box on ^U
#
sub clearentrybox {
$Inputfield->delete(0,'end');
}
So far, so good here on my system... a perusal of
Tk::Text didn't reveal conflicts with normal keys...
(Update: Added context to make locating the spots to put the code a tad easier)
--
Me spell chucker work grate. Need grandma chicken.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.