Update jogamp to version 2.1.4
Little workaround on AbsoluteLayout

This solves the issue #218 . I tested it on Nifty-Editor and i didn't
notice any bugs .
Also height and width

i don't know if this is a real user case... it is only to be coherent
with the other commit .
Solve an error in the comment at line 64 

Evil cut&paste :D
Merge pull request #219 from relu91/1.4

Solve issue #218
#71 Optimize sending events when changing constraints

Changing constraints will not immediately publish an event on the
eventbus anymore (with some exceptions noted below). Instead the element
will just be marked and the event will be send on the next layout pass.

Doing it this way is more correct because the event will now be sent
directly after the change has been actually applied (and not at some -
possible long - time before it actually happened).

And when changing multiple constraints you'll now only get a single
Element changed event and not multiple.

There are some changes to an Element that will have a direct effect on
it (and not at the next layout pass) that will be published immediately:

- setParent() when the parent clip area is changed
- setStyle()
- removeStyle()
Merge branch '1.4' of git@github.com:void256/nifty-gui.git into 1.4
Adding multiClickEvent ! #53 . Follow scenario : click-click-click , three events will be raised onClickEvent - MultiClickEvent( count = 2 ) - MultiClickEvent( count 3 ) . This only works for primary button but it should be simple to add to the other methods . I've also added a global property to change multi-click-threshold
Fixed #176
Fixed #175
Some issues fixed

fixed #175 #176 and start to work in #56
try to clear my commits
Merge pull request #220 from relu91/1.4

Fixes #175 #176 and #53
Fish multiclick support

This commit adds multiclick support for all nifty mouse buttons.
Merge pull request #222 from relu91/1.4

Finish multiclick support
#43 make setVisible() none recursive and keeping state of child elements

Calling setVisible() on an element will now only change the visibility
flag of this element without modifying the child element visibility
state. Therefore when hiding a parent element and later showing it
again, the child elements visibility will not be changed.

Additionally a new isVisibleWithParent() method has been introduced that
checks the visibility of the element + the visibility of all parent
elements. This was necessary for DraggableControl which checks valid
drop targets bottom up including the visibility flag. The
DraggableControl will call isVisibleWithParent() now to make sure it
doesn't select drop targets that are visible themself but are not
actually visible because of some parent element being hidden.
Absolute clipping

Added also a simple example .
Merge pull request #223 from relu91/1.4

Absolute clipping
#83 issue example code added (SSCCE) to prove that it works in 1.4
new moveToRelative() method added to fix a bug in AllExamples example

This was actually an interesting bug to fix because there were several
things interacting in weird ways.

The problem: In the AllExamples menu the selected menu item was animated
and rendered with the TextSize effect making it larger than regular menu
items. However with the latest Nifty 1.4 the selected menu-item was
stuck at it's initial position not being moved around with the rest of
the menu. WTF?

Issues:

First, a couple of weeks back we've cleaned up rendering the way Nifty
keeps track of render states while rendering. There was a lot of
(mostly) unnecessary render state saves happening while rendering which
have been removed. I think this affected the moveTo() call on the
NiftyRenderEngine which sets a current offset being applied when
rendering. The TextSize effect uses moveTo() to adjust the text position
according to the textScale. However, it did that absolutely without
taking into account that the current moveTo could already been modified
by some effect before (like the moving in of the whole menu). I think in
the past this moveTo() state was saved correctly but because of the
change it is not saved correctly.

The second issue was the introduction of the absolute clipping. The menu
was using childClip which will only actually clip if there was no
clipping set before. With absolute clipping enabled and the menu
starting off-screen the clipping rectangle was not changed end the
absolute clipping (whole screen) was still enabled. Because of the move
effect not moving the selected menu item and it was not being clipped it
stayed at its original position looking odd :) Without absolute clipping
the moveTo bug was not really visible because it was clipped.

To fix all of this we've now introduced a new moveToRelative() method
which is used by the TextSize effect now. This will add the moveTo
effect to the one that might already be applied. So the TextSize
position adjusting (because of the new textsize) AND the move effect of
the whole menu will now be added together and applied both.

This is a little hack but it will solve the issue for now.

Future versions of Nifty will have a proper transformation matrix - I
promise ;)