directive has no image specified. Prior to this
it was throwing an ArrayIndexOutOfBounds exception
which was silently swallowed even though the
import fails.
Depreciated InputManager.getSimluateMouse and replaced with InputManager.isSimulateMouse for consistancy.
Removed depreciated TouchInput.getSimulateMouse().
Added InputManager.isSimulateKeyboard() to keep consistancy with mouse methods.
Also changed JmeAndroidSystem to store the view instead of the activity.
When users call JmeSystem.showSoftKeyboard(true), the default Android soft keyboard is displayed and any key presses are sent to jME as touch events. Key events are also generated so the user can use the same key listeners as Desktop to keep the user code common between Desktop and Android platforms.
works internally to avoid full-scene graph traversals
once per frame.
Random unrelated things first:
Spatial constructors were modified to be protected since it
is an abstract class and it's good practice. I also flipped
them to be this(default values) instead of this() to delegate
constructors.
Geometry and Node constructors were modified in similar ways
to at least call the this(name) version of the constructor
everywhere.
removeControl(Class) was modified to do what it's javadoc
says and only remove the first encountered control. Prior
to this change, it was removing all matching controls.
The meaty stuff:
Node.updateLogicalState() no longer traverses all children
and never traverses any children at all unless it is the root.
If it is the root node, it keeps a list of all Spatials that
require updates and only iterates that list.
Spatial was modified to have a package-private requiresUpdates()
method that returns true if the requiresUpdates flag is set
or the Spatial has controls.
The requiresUpdates flag can be set by subclasses that require
updateLogicalState() to be called even if they have no controls.
(BitmapText is such an example.) By default, subclasses will
_always_ have this flag set to true, ie: default to the OLD behavior
and avoid silently breaking.
Subclasses that wish to have the new-hotness optimal behavior
must call setRequiresUpdates(false) in their constructors.
They can opt in to better performance rather than silently
breaking with an upgrade.
The only negative side effect of this change (other than
slightly increased complexity) is that for large scene
graphs with lots and lots of controls or children requiring
updates, a large list of spatials will be kept in the root
node. This will never exceed "number of spatials in the
scene graph" and so already had a fairly small upper bound
with the old code due to performance.
I think I've captured all of the edge cases... but we'll
see. :)
Stress test example to follow.
Normen Hansen
iwgeric
Nehon
jmekaelthas
Paul Speed
shadowislord
Bebul
Rena4ka