I have ported my application from 1.1.7 to 1.2, and after changing all the com.sun.java to swing gotten the application to compile. It blows up, however, with a null pointer exception, the first time the user presses a button which eventually triggers a call to JComponent.paintAll(). The components were originally painted once, successfully without causing null pointer exceptions so I'm curious what the difference could be. This code gave no trouble in jdk 1.1.7. I have looked at everyplace I could think of on the Sun site documenting changes in API to see if there was anything about this sort of thing and came up empty. It would seem that for something this simple to break it would have to be a major change in the way the whole swing system works. Does anyone have any information on any sort of macro-level changes to swing that could cause this behavior? Or could it be a bug in the linux port? (I don't have a 1.2 platform yet to test the code under Windows, but I will soon.) In any case I have sent a bug report but perhaps someone here has information. ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
