ICEpdf
  1. ICEpdf
  2. PDF-85

Rationalize Viewer RI focus management

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 4.0 - Beta, 4.0
    • Component/s: Viewer RI
    • Labels:
      None
    • Environment:
      ICEpdf Viewer RI
    • Affects:
      Sample App./Tutorial

      Description

      The Viewer RI application is currently setting focus on the document panel (to support keyboard navigation of the visible document, scroll up, down, etc.) in numerous places, including every-time an actionEvent or itemChangedEvent is fired on the SwingController.

      This approach is too blunt and results in the focus being set many times when it is redundant or undesired. One side-affect of this behavior is that the Search panel is not able to set focus on the search entry field because focus is "stolen" away by some other event that sets focus on the document panel.

        Activity

        Ken Fyten created issue -
        Ken Fyten made changes -
        Field Original Value New Value
        Salesforce Case []
        Fix Version/s 4.0 [ 10212 ]
        Affects [Sample App./Tutorial]
        Assignee Patrick Corless [ patrick.corless ] Ken Fyten [ ken.fyten ]
        Ken Fyten made changes -
        Salesforce Case []
        Description The Viewer RI application is currently setting focus on the document panel (too support keyboard navigation of the visible document, scroll up, down, etc.) in numerous places, including every-time an action event or itemchangedevent is fired. This is too blunt and results in the focus being set many time when it is redundant or undesired.

        One side-affect of this behavior is that the Search panel is not able to set focus on the search entry field because focus is "stolen" away by some other event that sets focus on the document panel.
        The Viewer RI application is currently setting focus on the document panel (to support keyboard navigation of the visible document, scroll up, down, etc.) in numerous places, including every-time an actionEvent or itemChangedEvent is fired on the SwingController.

        This approach is too blunt and results in the focus being set many times when it is redundant or undesired. One side-affect of this behavior is that the Search panel is not able to set focus on the search entry field because focus is "stolen" away by some other event that sets focus on the document panel.
        Ken Fyten made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Fix Version/s 4.0 [ 10222 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Ken Fyten
            Reporter:
            Ken Fyten
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: