Greg -

Pretty sweet, been playing around with the text box.  I really like that it gets the clipboard stuff, that makes it feel less like a Java applet and more like a real program!

A few things for the next version:

1) For some reason, key repeat doesn't seem to be working, though it doesn't look like you're blocking it, so something must be happening higher up the chain that's keeping the events from being sent properly to the textbox class.  Probably a simple fix once located.

2) There are a few OSX issues, such as meta+V not pasting (ctrl+v still works, but is a bit foreign on the Mac), and pressing the meta key alone scrolls the box in an odd way.  I forget off the top of my head how the meta key shows up as a key event, but therein lies the solution...also, on OSX, meta+right goes to the end of the line and meta+left goes to the start, and alt (a.k.a. "option") + left/right jump by words.  Lacking home/end keys, some people become quite addicted to these shortcuts, so they might be useful to add.

3) In native text boxes, a double click often selects the nearest word, and a triple one would select the whole box - I find this very useful, it could be good to add if you're going for a solid feel.  Once the whole box is selected, further clicks do nothing until a time delay has passed with no clicks (i.e. new clicks reset the timer), at which point another click simply places the cursor at the location as usual, clearing the selection.

4) Very slight bug - when you start selecting text, if you then drag all the way to the beginning of the line, it often highlights the first two characters as a single unit instead of separate characters (i.e. there's no way to select all but the first character starting from the right).  Minor, but probably not too tough to fix.

Good stuff, I'll definitely be using this class once you're done tinkering with it.

-Eric

Figured out one thing about the meta key here - something is actually being inserted as a character into the string, though in this font it's not showing up as a character.  Probably just need to catch this key separately.

This is starting to go severely off topic, but speaking of the difference between keyPressed() and keyTyped(), I notice that both of them fire repeated events when you hold a key, whereas I would usually think that keyPressed() should only be called on the initial keypress.  Is this a bug, or is it actually the desired behavior?  It's easy enough to just set up an input wrapper that filters out the repeats, but it always seemed a little bit odd to me the way it works currently.