Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.6.2
    • Fix Version/s: 1.6.3
    • Component/s: Table
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5

      Description

      No clean way to switch off the find() action in JXTable. I prefer to use my own
      isearch implementation.

      Can workaround by:
      1) adding null value for "control F" keystroke in when_focussed inputmap
      2) removing find action from actionmap

      but would be nice to have a specific method for this, so could be sure future
      versions of the class would honour the setting.

      For example:

      /** enables searching, if false then search dialog is not shown (for example
      when user presses control F) **/
      setSearchEnabled(boolean enabled)

      {..}

        Activity

        Hide
        kleopatra added a comment -

        taken

        Show
        kleopatra added a comment - taken
        Hide
        kleopatra added a comment -

        Hmm, remove/replace the action in a xTable's actionmap is a safe enough way to
        go. What we can do is to formalize the key-name of the action to guarantee that
        is is alway "find". I would prefer not to add an additional property.

        The basic idea is to have a per-application consistent way of searching, f.i.
        higher level components in the JN-layer might look for the find-entry in the
        actionMap.

        Jeanette

        Show
        kleopatra added a comment - Hmm, remove/replace the action in a xTable's actionmap is a safe enough way to go. What we can do is to formalize the key-name of the action to guarantee that is is alway "find". I would prefer not to add an additional property. The basic idea is to have a per-application consistent way of searching, f.i. higher level components in the JN-layer might look for the find-entry in the actionMap. Jeanette
        Hide
        kleopatra added a comment -

        hach ... such an old issue - where did it hide?

        closing as wontfix - if anybody still wants such an support, feel free to re-open. Might consider to add support a property stored in the UIManager to disable the swingx find per-application. Strongly opposed to allow any per-component property as mixing different search mechanism would give a very bad user experience, IMO.

        Cheers
        Jeanette

        Show
        kleopatra added a comment - hach ... such an old issue - where did it hide? closing as wontfix - if anybody still wants such an support, feel free to re-open. Might consider to add support a property stored in the UIManager to disable the swingx find per-application. Strongly opposed to allow any per-component property as mixing different search mechanism would give a very bad user experience, IMO. Cheers Jeanette

          People

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

            Dates

            • Created:
              Updated:
              Resolved: