single-arg registerClass() method now throws an exception
if the object is not marked Serializable. Internally,
the package-load stuff uses the new alternate method that
allows safe non-exception throwing registration since it's
hitting it with every class in a package.
Interestingly enough, messages will still get written out
because of some questionable code in writeClassAndObject()...
but it won't be read as anything but null despite its
40+ bytes of data.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7121 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
the case of nulls. Note: this is specific to
serialized objects and is therefore not adding
a byte to things like Strings or arrays... those
will have to be reviewed separately.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7119 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
I called stuff that was meant to be internal to nifty. That's fixed now. Also had to replace the nifty examples jar with a new version. This version os BIG (15Mb). Void is working on a smaller one, but at least with this big one, things work as expected.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7117 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
There is still an issue with the mouse buttons besides the first mouse button. These should be picked up by nifty, but for some reason are not triggering a MouseButtonEvent. This is something Kirril will need to take a look at.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7114 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
Client and server should match or bad things happen and it
might be worth adding this to the connection negotation
as a validation.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7106 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
* RenderManager will reload "shader" boolean on each invocation of render(), since Renderer might not have proper capabilities set before canvas has been attached
jMP
* Fixed some illegal calls in SceneApplication
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7095 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
last minute shifts in APIs. Anyway, outbound TCP
broadcasts work again and are more efficient since the
Kernel callers can better control when their message
buffers are copied (in this case it isn't necessary so
we save a buffer copy).
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7088 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
way made the caller specify a local port due to an unusually
persistent bit of ancient lore lodged in my brain.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7086 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
* Added test that demonstrates above functionality, by starting Application without attaching the canvas, and then constantly attaching and detaching canvas from a frame.
* Deleted deprecated methods in JmeContext
* Deleted deprecated class LwjglJoyInput
* Audio renderer will not attempt to initialize OpenAL twice if already initialized
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7078 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
to give new API users a proper extension point for their
own messages. (forgot this file in the last commit)
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7070 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
- make CollisionShapeFactory use not world translation but translation relative to given parent
- add CollisionShapeFactory test
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7060 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
that can optionally flush the queued messages. Modified
DefaultServer to close-with-flush when kicking a client
so that the disconnect message actually gets to them.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7049 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
own threading rules... it's sort of heavy-handed but
given the separation of the reliable and unreliable
implementations (and the inability to really know how
they are threading from here) this is the safest way and
doesn't seem to really affect throughput.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7047 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
of message event dispatch. This is one of the reasons
I thought the existing services need to be checked for
'correctness' re: multithreading. Even in the current
implementations, a message listener may be called by
different threads.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7046 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
state so that if a caller creates a client then immediately
starts sending message, we can block until the connection
is really established.
git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7044 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
PSp..om
nor..67
rac..om
Kae..pl
mul..va
rem..om
sha..rd