Catch TAB and jump to new position in JTextField!!!

Question

Hi,
first of all i wanna say Hi to everyboy, 'cause this is my first post in this forum. and here comes my question:
I have a JTextfield and if the TAB-Button will be used there, the cursor should jump to a new position. So in detail, it SHOULDN'T do the normal TAB stuff (insert some blanks). Only the cursor should jump to a new position.
What I did: (workaround)
I used a KeyFieldsListener(extends KeyAdapter) which catches the TAB, copies the text before and after the blanks (which comes from the TAB). The PROBLEM is, this is to slow. The user can see what the TAB is doing.
For any suggestions I would be grateful !!!
Regards,
Robin
My Code:
if ((key == KeyEvent.VK_TAB)){
     // now position of caret (after TAB)
     int offset = HitlistFrame.searchText.getCaretPosition();
     String tempText = HitlistFrame.searchText.getText().substring(0, offset-1) +  HitlistFrame.searchText.getText().substring(offset);
     // copy text before TABING into TextField
     HitlistFrame.searchText.setText(tempText);
     // search for next blank
     while ((offset < HitlistFrame.searchText.getText().length()) &&
               (HitlistFrame.searchText.getText().charAt(offset) != ' '))
          offset++;
     // set cursor to position of next blank
     HitlistFrame.searchText.setCaretPosition(offset);
}

Answer 1

The long and short of it that the code simply assumes theat the layers don't exceed the comp size or leave the comp. Depending on where you apply the code, that may not be true. You would have to add extra stuff to make it more safe and things like specific shape layer modifications or the anchor point coordinates on shape layers being based on the middle of the layer, thus regularly producing negative values, would further complicate the matter. The code is simply too simplistic to cover such scenarios and the internal calculations in your case probably produce these aforementioned negative vlaues that the Puppet effect can't handle since in its world they don't exist. Anyway, without seeing what's actualyl going on, nobody can provide the ultimate solution. I could write an endlessly complex expression and it may still not solve your dilemma. as a start, you might consider pre-composing everything to comps of the same size and using these comps instead of the native AI file. This would also eliminate all the hocuspocus with the layer space transforms and greatly simplify things (and help performance).
Mylenium