Commits on Oct 7, 2012
  1. fix missing scm:git in developerConnection

    void committed Oct 7, 2012
  2. changed <scm> configuration to github

    void committed Oct 7, 2012
  3. Revert "Merge branch '1.3' into 1.4"

    This reverts commit 72e7648, reversing
    changes made to e147934.
    void committed Oct 7, 2012
  4. Merge branch '1.3' into 1.4

    void committed Oct 7, 2012
Commits on Oct 3, 2012
  1. mouse events have been returned as processed = false in some wrong cases

    It was possible that Nifty returned processed = false for events that
    from a intuitive standpoint should have been processed. Example:
    Clicking on a DropDownControl so that it opens and while it is
    opening releasing the mouse button. This was reported as processed =
    false which would make it possible for your game to handle the event -
    although that would be very odd in that special case.
    The problem is that Nifty will block interaction while
    onStartScreen/onEndScreen/interactionBlocked-Flag is active. This is
    expected in most cases but since these elements could not be interacted
    with Nifty return processed = false. This has now been corrected:
    Elements that are generally available for interaction but are not at the
    moment will still be treated as processed = true.
    void committed Oct 3, 2012
Commits on Oct 2, 2012
  1. reactivate elements in resetLayers()

    The onEndScreen effect will disable interaction with elements by setting
    a done boolean to true. Unfortunately this flag was never reset when you
    gotoScreen() to the same screen. It was therefore possible for elements
    to be visible but not being able to interact with them. Now done is
    explicitly reset to false in the startScreen() method.
    void committed Oct 2, 2012
  2. fix failing tests

    void committed Oct 2, 2012
  3. ignoreMouseEvents and ignoreKeyboardEvents added at element level

    The new methods to ignore mouse events and keyboard events at the global
    Nifty level have now been added at the element level as well. You can
    now ignore mouse and keyboard events for individual elements too! Please
    note that this is a bit redundant to the existing visibleToMouseEvents
    but we've kept the same names to be consistent with the method on the
    main Nifty instance.
    We see it so: visibleToMouseEvents should be used to generally define
    visibility to mouse events and ignoreMouseEvents / ignoreKeyboardEvents
    to temporarily disable access.
    void committed Oct 2, 2012
  4. delay focusHandler element removal in nifty.removeElement() to frame end

    element.removeFromFocusHandler() is now called when the Element is
    really removed at the end of the next frame update loop and not directly
    when nifty.removeElement() is called.
    void committed Oct 2, 2012
  5. mouseWheel() interact method will now be consumed by the scrollbar

    This especially fixes a problem in the ScrollPanelControl where you
    could move the vertical Scrollbar while hovering the horizontal
    Scrollbar. The problem was that originally the mouseWheel() event was
    not consumed by the Scrollbar and was therefore send to the mouseWheel()
    event of the Scrollpanel Control as well.
    void committed Oct 2, 2012
  6. CheckBox: Prevent toggle animation when there is no change in state

    When you uncheck a CheckBox that is already unchecked or you check a
    CheckBox that is already checked then now there is nothing changed. This
    prevents the somewhat ugly display of a check mark that disappears when
    a CheckBox is initially unchecked and is set explicitly to unchecked by
    code again.
    void committed Oct 2, 2012
Commits on Oct 1, 2012
  1. nifty.gotoScreen() will now remove all previous focusHandler elements

    This is necessary to prevent duplicate entries when calling
    nifty.gotoScreen() for the same screen, e.g. you goto a screen, go to
    another screen and then return back to the first screen. Prior to this
    change all focusable elements where added again o_O
    void committed Oct 1, 2012
  2. NiftyInputConsumerNotify added (can be enabled on Nifty instance)

    This is a debugging / information feature. You can enable an
    NiftyInputConsumerNotify instance on the main Nifty instance and Nifty
    will call you back to inform you about the mouse- and keyboard-events it
    has received AND if the events have been processed by Nifty.
    void committed Oct 1, 2012
  3. onInitialClick() will now ALWAYS capture the mouse

    This is done to prevent losing mouse events when you click and hold the
    mouse button on some GUI element and then move the mouse away from the
    control. This kind of capturing the mouse already worked well for all
    controls that are focusable. Some controls - like the buttons of
    a Scrollbar control - are not supposed to be focusable individually. For
    these controls the mouse was not captured but it is now.
    void committed Oct 1, 2012
Commits on Sep 30, 2012
  1. Merge pull request #54 from mkaring/1.3

    Improved Label-Control builder
    void256 committed Sep 30, 2012
Commits on Sep 26, 2012
  1. Issue #50 DropDown Improvements Part II fixed

    "displayItems" attribute is now supported for the DropDown control too.
    void committed Sep 26, 2012
Commits on Sep 24, 2012
  1. should fixed issue #52 Listbox Focus Problem

    The problem was that the Listbox of the DropDown is hidden but it's
    still being updated with all the data, selection and the correct focus
    item. The problem is that without showing the Listbox at least once
    Nifty does not know the layout of the Listbox and the Scrollbar. So
    internally the handle position is kept at 0. This has now being fixed
    with an explicit (internal) update of the position when the Listbox (and
    the scrollbar) is being shown initially.
    void committed Sep 24, 2012
Commits on Sep 22, 2012
  1. add some commented out logger configurations

    void committed Sep 22, 2012
  2. fixed DraggableControl not processing mouse events in some cases

    It was possible for DraggableControls to return "processed = false"
    for mouse events when it was being dragged very fast or when the mouse
    leaves the screen while it was dragged. This should be fixed now.
    Implementation note:
    Nifty already supported exclusive mouse events for elements that are
    focusable. When such an element was initially clicked the element
    internally was marked as the one element that captured the mouse. Nifty
    made sure that all mouse events were only sent to this element.
    However it still was possible to have mouse events that didn't hit any
    element at all and therefore were returned as "processed = false". This
    has now been changed. Now all mouse events will be send to the element
    that has captured the mouse no matter if the mouse hovers the element or
    Additionally when a DraggableControl is being dragged it is
    now automatically marked as exclusive.
    void committed Sep 22, 2012
  3. logging tweaks

    void committed Sep 22, 2012
Commits on Sep 19, 2012
Commits on Sep 18, 2012
  1. Merge pull request #48 from mkaring/1.3

    Bugfix in ListBox
    void256 committed Sep 18, 2012
  2. Fixed conflicting ID problem that happened in case two dropdown eleme…

    …nts were placed on the same screen.
    mkaring committed Sep 18, 2012
Commits on Sep 11, 2012
  1. Merge pull request #47 from mkaring/1.3

    Fixed tab-control bug
    void256 committed Sep 11, 2012
Commits on Sep 8, 2012
  1. #59 fix calling nifty.gotoScreen() with pending closePopup() (

    nifty.closePopup() will not be executed directly but will be scheduled
    for execution at the end of the next update loop. nifty.gotoScreen()
    however will be executed immediately. Because of this it was possible
    that calling nifty.closePopup() directly followed by a call to
    nifty.gotoScreen() messed up some internals - because the current
    screen already has been removed when the popup is still active
    and in the process of being removed.
    Now we will close all popups in nifty.gotoScreen() directly prior of
    actually changing the screen to the new one.
    If you use effects when the popup is closed and you need to wait for the
    effects to end you should use nifty.closePopup() with an EndNotify and
    call nifty.gotoScreen() when the EndNotify is called.
    void committed Sep 8, 2012
  2. #62 [JME3] Enable/disable consuming of mouse events by Nifty (

    Use nifty.setIgnoreMouseEvents(true) to completely disable mouse event
    processing in Nifty . The NiftyInputConsumer.processMouseEvent() will
    always return false in that case.
    Use nifty.setIgnoreKeyboardEvents(true) to completely disable mouse
    event processing in Nifty. The NiftyInputConsumer.processKeyboardEvent()
    will always return false in that case.
    void committed Sep 8, 2012
Commits on Sep 7, 2012
  1. Merge pull request #46 from mkaring/1.3

    Dropdown control improvement
    void256 committed Sep 7, 2012