G4P has been around for over 2 years and no one has reported a similar problem. Also the fact that they work locally and on the web (but only sometimes) is really confusing but based on what you say I have an idea of what is going wrong but I need to explain a little how G4P works.
When I created the library I was keen that it should be simple to use. For instance to create, draw and use a button requires just one line of code and each type of control had its ownpre-defined event handling method e.g. handleButtonEvents. Initially this caused a problem with the 3D renderers and other libraries (such as PeasyCam) because the user could not be sure when the controls were actually being drawn. To overcome this problem I allowed users to disable autodraw
BUT if they do then they
must call
G4P.draw() at the end of the draw() method instead (by the way - do not enable autodraw and use G4P.draw() at the same time) . Also, and I don''t know if you are doing this - but the user should
not call the control's draw() method directly e.g.
myButton.draw();
If you disable autodraw you only prevent them being drawn - they still exist and can still be used if you know where they are. (I see you have discovered that).
I have followed your link and seen your Pacman game (awesome work - congratulations) and I can see that you only want to show the textfields and buttons at particular times.
Having said all that I make the following suggestions.
- Do not disable the autodraw
- If you do disable autodraw then add G4P.draw() to the end of your draw() method.
- Use the setVisible and setEnabled methods to determine whether the control should be visible and/or enabled.
Let me know how you get on.
Of course it'll still have to go through my testing team but I think I'm golden!