setCurrentAccessibleValue insists on Integer when API says Number...

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P3
    • None
    • Affects Version/s: 1.4.0
    • Component/s: client-libs
    • None

      The documentation for the AccessibleValue.setCurrentAccessibleValue API gives
      the method the following signature:

      boolean setCurrentAccessibleValue( Number )

      In reality the current implementation ignores any subclass of Number other than
      Integer, this is inconsistent with the documentation and violates OOP.

      If the signature is a Number why cannot the "intValue()" method of Number not
      be used to extract the integer required in the implementation. Any Number
      passed in should be valid, whether it's an Integer or not, so long as it's in
      the correct range.

            Assignee:
            Lynn Monsanto (Inactive)
            Reporter:
            Darren Kenny
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: