[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[aspectj-dev] ajbrowser run problems
|
I'd like to make the ajbrowser run button work for demo purposes,
or, failing that, disable it.
Currently it successfully runs a main class in the same VM, which
works for console appplications but not for AWT applications -
spacewar in particular. I'm not sure whether or how an AWT
application can be written to share an event queue with a Swing
application. (Fixes, advice, and pointers (beyond sun docs)
welcome.) Failing that, Mik started a process-launching
implementation which I could complete, time permitting.
Below is the behavior, including 1.4 variants in case the
1.4.1 AWT focus changes are having an impact.
Wes
----- using spacewar from 1.1rc2, 1.4 == Sun 1.4.1 on NT
- compiling with ajbrowser under 1.4 or 1.3 - ok
- running directly under 1.3 - ok
- running directly under 1.4 - bug (info window)
- info window contents not drawn
- main windows show black background,
and all display items work
- input accepted and processed
- running with ajbrowser under 1.3 - bug (main window, input)
- does show info window content
- main windows show black background,
but nothing in display
- input ignored
- ajbrowser not responsive, no damage repair
- running with ajbrowser under 1.4 - bug (main and info window, input)
- no info window content
- main windows show black background,
but nothing in display
- input ignored
- ajbrowser not responsive, no damage repair