Loading...
Logo
Processing Forum
Hello,

I'm using G4P 2.0.2 and Processing 2.0b3 on Windows 7.  I am not able to enter text into my G4P textfields (which are placed inside GPanels).  I can click in the text field and get focus, but typing does not add anything to the display.  When I click outside the text field, the callback method recognizes an ENTERED event.

Has anyone else noticed this?  Perhaps the use-model for GTextField is different in the new version?

Regards,
bbc

Replies(8)

The library authors are struggling to get right the integration of their library with the (moving) target of the 2.0 API. Now that it reached beta state, the API should be more stable (that's the point of alpha releases, to improve the API with feedback from users).
quarks is active on updating his library, so it shouldn't be long before he releases a working version.
I figured quarks was working on it, but wanted to post in case others have the same question or something changed regarding how I should be catching the events.  Hopefully, I'm not too much of a pest... :)

I needed to move to Processing 2.0 because of an error with exporting libraries to applications in 1.5.1 ( http://code.google.com/p/processing/issues/detail?id=638 ).  

thanks
bbc
in Processing 2.0b1 the PFont.getFont() method was removed and it broke the library so I wanted to release a new version ASAP. Unfortunately there was a bug in b1 that caused contributed libraries that used keyboard input to crash.

This meant that I was unable to fully test G4P 2.0.2 and I accidentally made a typo in the code that switched off the GTextField class from keyboard events. My mistake OOPs

I have made the corrections and tested them successfully with 2.0b3 and I plan/hope to release a new version tomorrow and make an appropriate announcement in the Library and Tool Development forum.

@PhiLho thanks for explaining the situation.
" Hopefully, I'm not too much of a pest"
No, error reports and other feedback are always useful for library writers...

Just seen PhiLho's comments re pest and agree totally - people that report problems help the writers make better software.
Ok, I'll keep posting when I see something... :)

Thanks for the quick responses!  G4P hasn't been 'perfect', but every issue I've had has been resolved very fast.

Someone much smarter than me says "there is no such thing as bug-free code" and "if you aren't making mistakes, you aren't working"...

Problem fixed in G4P V2.0.3 which is now available.