The input system should be overhauled to run most input like mouse clicks etc.
on the AWT thread to simplify the logic in the input system. Special care needs
to be taken of the picking system as it requires running on the GL thread to do
the picking. This is not the case for the camera an move etc. widgets which can
perfectly fine be coordinated from the AWT thread and then just execute the
movements on the GL thread.
The Tools System should afterwards be more integrated into the Actions system
of the Platform. Right now too many parameters are passed that can be grabbed
from the lookup of any of the parameters like JmeSpatial, DataObject etc. The
wrapped objects like JmeSpatial should be passed and used for as long as
possible instead of passing Spatials etc. Methods that execute on the GL thread
should never modify global variables in the classes but use variables that have
been passed from evaluating code "logic" on the AWT thread to avoid threading
issues. This should be easier when most of the code runs on the AWT thread.
Original issue reported on code.google.com by normen667 on 8 May 2012 at 1:07
Original issue reported on code.google.com by
normen667on 8 May 2012 at 1:07