Skip to content
Commits on Jan 25, 2015
  1. [maven-release-plugin] prepare for next development iteration

    Illarion Jenkins - CI committed
  2. [maven-release-plugin] prepare release nifty-main-1.4.1

    Illarion Jenkins - CI committed
Commits on Nov 19, 2014
  1. fix: CheckBox control did not keep it's state when being hidden/shown

    void committed
    The custom Nifty effects for the CheckBox (scale + fade) have been
    removed for now. The new way of keeping the visible state of child
    elements intact when a parent element is hidden introduced issues with
    the custom effects.
Commits on Oct 22, 2014
  1. @bgroenks96

    Fixed chat control not displaying text in player/chat list boxes

    bgroenks96 committed
    -> TextRenderer.setText/setLabel were placed before setStyle in ChatBoxViewConverter; this caused setStyle to overwrite the submitted text because it calls setStyle(<original text>). Both method calls were moved after setStyle. This *seems* to have resolved the issue.
    Fixes #293
Commits on Sep 1, 2014
  1. @relu91

    Update Listbox

    relu91 committed
  2. @relu91

    Fix code style

    relu91 committed
Commits on Aug 31, 2014
  1. @relu91
Commits on Aug 29, 2014
  1. [Button] MoveCursorDown and MoveCursorUp don't check parent anymore

    void committed
    NextInputElement and PrevInputElement didn't check the parent of the
    elements they change focus to/from. There is no known reason why it
    should not be the same for MoveCursorDown and MoveCursorUp.
Commits on Aug 25, 2014
  1. @3xp0n3nt

    Refactor element mouse interaction.

    3xp0n3nt committed
    There is an ambiguously-named method in the Element class that spurred
    on this refactoring: onClick.
    Surely this method began long, long ago with good intentions...
    But now that Nifty has separated the idea of a click from a release, now
    that there exists multiclicks, primary clicks, secondary clicks,
    tertiary clicks, and combinations of clicking and releasing, this method
    is embarrassingly outdated.
    What it actually does is simulate a click-release of the primary mouse
    button. "Simulate" means that normally all mouse actions are handled via
    events, but in this case, the event system is bypassed and the mouse
    action is handled AS IF it received an event.
    This simulation is useful when we want to cause mouse actions to occur
    that are not originated by the user. The only actual INTERNAL use case
    for this currently is handling NiftyStandardInputEvent.Activate events.
    Not only is the Element.onClick method name ambiguous, but the method it
    delegates to is also ambiguous; that is, ElementInteraction.activate,
    and the method that that method delegates to is also ambiguous:
    ElementInteractionClickHandler.activate, and finally this last method
    also delegates to another ambiguously named method,
    Why are they ambiguous? Because these "activate" methods are really
    simulating a primary mouse button click-release. This "activate" concept
    is a bad abstraction because in all these classes it is surrounded by
    other methods that very specifically refer to mouse related parts and
    actions (wheels, buttons, clicks, etc).
    It's very important to have a consistent level of abstraction here. So
    the solution is to rename all these "activate" methods to what they are
    so that they harmonize with the other methods there, which means using
    the phrase "clickAndReleasePrimaryMouseButton" or similar wording as
    This renaming revealed that there were some methods missing for
    supporting simulating secondary and tertiary mouse button
    click-releases, so add those methods as well (most of the framework was
    already in place for secondary & tertiary mouse actions).
    Now we have elegantly solved the ambiguity of Element.onClick while
    simultaneously adding some interesting features:
    Now we can directly cause a click-release for either of the three mouse
    buttons supported by Nifty, without having to dig through the code to
    interpret the meaning of bad abstractions (Element class already
    contains much explicit mouse-related functionality, so the above three
    methods are not out of place).
    Because the Element.onClick method is public, deprecate it rather than
    deleting it (in line with other past refactorings of public Element class
    methods). Refer users via the onClick javadoc to
    Make Element.onClick delegate to
    Add extensive javadoc to Element.onClickAndReleasePrimaryMouseButton,
    Element.onClickAndReleaseSecondaryMouseButton, &
    Element.onClickAndReleaseTertiaryMouseButton to explain what they do and
    in what situations they won't work. (This information was missing on the
    Element.onClick method, making it even worse).
    Change all internal callers of Element.onClick to use
    Element.onClickAndReleasePrimaryMouseButton. Now, Element.onClick has no
    uses internally and is ready to be deleted after the next release of the
    Element.onClickAndReleasePrimaryMouseButton is used internally to handle
    NiftyStandardInputEvent.Activate events. The name of the new method is
    self-documenting and should eliminate confusion for users implementing
    custom controls and/or custom input mapping. They also now have the
    option of mapping to secondary and/or tertiary mouse button
    When Element.clickAndReleasePrimaryMouseButton is called, now not only
    will a NiftyMousePrimaryClickedEvent be generated as before, but ALSO a
    NiftyMousePrimaryReleaseEvent. The same applies for secondary & tertiary
    mouse button click-releases. This was actually a preexisting bug that
    has been fixed.
    Other changes:
    Remove all other methods from the Element class that were deprecated in
    the previous version of Nifty. It should be safe to remove them now that
    they are deprecated in the current release version of Nifty. None of
    these methods were in use internally.
    The multiclick mouse code was poorly written, not conforming to the
    library's code style, contained spelling errors and poorly written
    comments. This has been improved although it is still far from complete.
    The logic of the multiclick code has not been changed.
    All unit tests are passing, and integration testing was successful.
Commits on Jul 6, 2014
  1. [maven-release-plugin] prepare for next development iteration

    Illarion Jenkins - CI committed
  2. [maven-release-plugin] prepare release nifty-main-1.4.0

    Illarion Jenkins - CI committed
  3. @mkaring

    Stop the search for droppables in case a element that consumes (is vi…

    mkaring committed
    …sible to) mouse events is located covering any other droppable
Commits on Jun 7, 2014
  1. Removed easymockclassextension (was deprecated anyway) and update to 3.2

    void committed
    some test made problems because it was using classes from the easymock
    classextension jar and the regular easymock jar. however classextension
    has been deprecated some time ago and was therefore removed. tests have
    been modified accordingly.
Commits on Apr 27, 2014
Commits on Apr 1, 2014
  1. #43 make setVisible() none recursive and keeping state of child elements

    void committed
    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.
Commits on Mar 31, 2014
  1. @relu91

    Some issues fixed

    relu91 committed
    fixed #175 #176 and start to work in #56
Commits on Jan 25, 2014
  1. TreeItem old format

    Torge Rothe committed
  2. Fix treetime format

    Torge Rothe committed
Commits on Jan 10, 2014
  1. @mkaring
Commits on Dec 29, 2013
  1. @mkaring
  2. @mkaring

    Fixed tree box

    mkaring committed
    The tree box is now responding to input events again.
Commits on Dec 28, 2013
  1. @mkaring

    Fixed drag'n'drop notifications

    mkaring committed
  2. @mkaring
  3. @mkaring
  4. @mkaring
  5. @mkaring
  6. @mkaring
  7. @mkaring
  8. @mkaring

    Fixed tab group error

    mkaring committed
    Usage of tab groups no longer freezes the entire GUI
  9. @mkaring

    Added some missing annotations

    mkaring committed
Commits on Dec 27, 2013
  1. @mkaring
  2. @mkaring

    Improved list box

    mkaring committed
     - Avoided use of the execute end of frame element effects function
     - Cached element references for faster resolving
  3. @mkaring

    Improved scroll panel

    mkaring committed
     - Improved access performance for scroll bars
     - Removed the nasty execute end-of-frame element actions call
Something went wrong with that request. Please try again.