Re^4: Displaying NUL in a TK::Text widget

This method gets the display right, however, as long as I'm asking for the world...:)

When Tk handles the conversion of non-printable characters, when I use the arrow keys to navitate in the text pane, it treats the non-printable as one character. That is to say that if I position the cursor right before the "\" and hit right arrow once, the cursor ends up after the "}". With this solution, that is not the case as I'm replacing one character with several. The translation is happening in such a way that it displays perl's notion of hex characters. I just don't know where that translation is happening.

Alternatively, if I can tell Tk to treat that series of characters (\x{10}) as only one character, that'd be acceptable too.

Finally, I'd like to thank everyone for their help thus far.

thor

Feel the white light, the light within Be your own disciple, fan the sparks of will For all of us waiting, your kingdom will come

Comment on Re^4: Displaying NUL in a TK::Text widget

Replies are listed 'Best First'.
Re^5: Displaying NUL in a TK::Text widget by Aighearach (Initiate) on Nov 07, 2004 at 21:24 UTC
I wish I had a better sollution to recommend, but all I can think of is to: put a tag around the text when there is input, see if the "insert" mark moved past the start of a tag of type mytag if so, move the "insert" mark past the end of the tag. A lot of work, but worth it IMO if you're going to use this thing a lot. You also might want to consider subclassing Tk::Text to support all these changes. Maybe overloading `insert` to make the transformation before handing it off to `SUPER::insert`... -- Snazzy tagline here	[reply]
Re^6: Displaying NUL in a TK::Text widget by thor (Priest) on Nov 08, 2004 at 01:26 UTC
Ah...crap. I know just enough Tk to be able to do simple things. Well, I suppose this could be the task that broadens my horizons...:) thor `Feel the white light, the light within Be your own disciple, fan the sparks of will For all of us waiting, your kingdom will come`	[reply]