FAQ
Cover
This is the archive Discourse for the Processing (ALPHA) software.
Please visit the new Processing forum for current information.

   Processing 1.0 _ALPHA_
   Bugs
   Software Bugs
(Moderator: fry)
   0058 throws null pointer exception on 'alt'
« Previous topic | Next topic »

Pages: 1 
   Author  Topic: 0058 throws null pointer exception on 'alt'  (Read 852 times)
ziz


0058 throws null pointer exception on 'alt'
« on: Aug 25th, 2003, 11:05am »

When you start a sketch running, go into the sketch window, and press the 'alt' key (on my system: Windows XP, JRE 1.4.2, P5 0058 ), the following exception is thrown.  You don't need to have any code in the sketch, and the sketch continues running properly (as far as I can tell).
 
 
java.lang.NullPointerException
 at javax.swing.SwingUtilities.getWindowAncestor(Unknown Source)
 at com.sun.java.swing.plaf.windows.WindowsRootPaneUI$AltProcessor.postProce ssKeyEvent(Unknown Source)
 at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)
 at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)
 at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)
 at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)
 at java.awt.Component.dispatchEventImpl(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)
 
Then, the same exception is thrown when the alt key is released.
 

not exactly working in your best interests since 1984
fry


WWW
Re: 0058 throws null pointer exception on 'alt'
« Reply #1 on: Aug 28th, 2003, 5:31pm »

argh.. thought this one was fixed.  
 
i think it's a java 1.4.2. issue (versus 1.4.1) in how they changed some aspect of the event handling works. but i'll look into it, because i thought we had it ironed out.
 
Pages: 1 

« Previous topic | Next topic »