swingx
  1. swingx
  2. SWINGX-708

JXMonthView: updateUI changes visible month

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 0.9.2
    • Component/s: Calendar
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      708

      Description

      weird side-effect: the visible month is decades in the future

      added tests (visual and unit) to expose

        Issue Links

          Activity

          Hide
          kleopatra added a comment -

          the "surface" problem was that delegate's lastDisplayedDate property wasn't
          updated - did so as a quick fix.

          another misbehaviour is that today isn't updated. Currently, there's no way to
          do so - it's a notification-only property of the monthView.

          Sure there is other state unkept ... which leads to the core problem: waaaayyy
          tooo much state kept as aliases in the BasicMonthViewUI. Will open a task to
          cleanup. Which unfortunately will hurt LF-implementations.

          Jeanette

          Show
          kleopatra added a comment - the "surface" problem was that delegate's lastDisplayedDate property wasn't updated - did so as a quick fix. another misbehaviour is that today isn't updated. Currently, there's no way to do so - it's a notification-only property of the monthView. Sure there is other state unkept ... which leads to the core problem: waaaayyy tooo much state kept as aliases in the BasicMonthViewUI. Will open a task to cleanup. Which unfortunately will hurt LF-implementations. Jeanette
          Hide
          kleopatra added a comment -

          the base problem is fixed.

          Opened issue 711 to clean up the property related issues (the missing today
          update should be handled there) and issue 712 to clean up the extensive
          aliasing/state duplication

          Show
          kleopatra added a comment - the base problem is fixed. Opened issue 711 to clean up the property related issues (the missing today update should be handled there) and issue 712 to clean up the extensive aliasing/state duplication
          Hide
          kleopatra added a comment -


          correct number of aliasing cleanup is issue 710

          Show
          kleopatra added a comment - correct number of aliasing cleanup is issue 710

            People

            • Assignee:
              kleopatra
              Reporter:
              kleopatra
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: