I just tested the FullScreenApp you point to, and it works for me, on Windows XP.
Now, I have hit an issue and report it in case it is useful to somebody else. For the test, I just save the example as 'FS', so I got a FS.exe file. Running it silently failed (no trace, etc.).
So I ran the jar instead:
Code:E:\Dev\PhiLhoSoft\Processing\FS\application.windows\lib
> java -Djava.ext.dirs=. FS
java.lang.ClassNotFoundException: FullScreenApp
at java.net.URLClassLoader$1.run(Unknown Source)
That's where I discovered the FullScreenApp string (second parameter of main()) have to be changed to the name of the sketch. It is stated in the page, but of course I overlooked that...
But obviously, that's not your problem.
Aha! I was annoyed because in the source I have, the line 6551 couldn't generate an NPE (NullPointerException).
I looked at the release notes, saw that 1.0.2 was released on Feb 21, looked at
PApplet.java history, saw that one day before, revision 5469 was checked in.
And in this version, at lines 6550-6551, we have:
Code: DisplayMode mode = displayDevice.getDisplayMode();
fullScreenRect = new Rectangle(0, 0, mode.getWidth(), mode.getHeight());
where displayDevice is a GraphicsDevice obtained via:
Code: GraphicsEnvironment environment =
GraphicsEnvironment.getLocalGraphicsEnvironment();
displayDevice = environment.getDefaultScreenDevice();
(if you don't specify --display=n option).
In short, it looks like
mode is null for some reason. Like Java fails to get your graphics configuration.
I see if you specify an additional argument:
--exclusive you go another code path, perhaps you will avoid this NPE.