• Value pickers - single value behaviour

    By Pieter JD Malan 1 decade ago

    Hello,

    When you have a value picker for a single value field (listbox with search) and you select an entry in the listbox and click OK it does not return the selected value to the field.

     

    Is there a way to perhaps hide the OK button to force the user to double click? Alternatively the behaviour could be changed to detect the selected value when OK is clicked. Is this possible?

    • Hum works for me

      By Philippe Riand 1 decade ago

      When an entry is highlighted in the list, then enter actually closes the dialog and returns the value. At least on my firefox...

      • I can reproduce it as follows ...

        By Pieter JD Malan 1 decade ago

        Using the latest version of the extension library and database:

         

        1. in http://localhost/xpagesext.nsf/Core_ValuePicker.xsp, open listbox with search single value

        2. click on 'California' ONCE and click 'OK'

        3. No value returned to the field

         

        Double-clikc and pressing enter works as expected. The problem is that most end-users will select the item (single-click) and then click on the OK button.

        • can confirm this </>

          By Lothar Mueller 1 decade ago

          • can confirm this but...

            By Lothar Mueller 1 decade ago

            (sorry pressed SAVE too early on my previous answer...)

            I guess this behaviour is meant to be like that, just as in the domino name picker dialogs: select an item then put it into a selection basket and when you're done hit ok.

            I wonder though whether this really makes sense for a single value dialog. It appears to be driven by the extlib.dijit.PickerListSearch dojoType.

            Would be nice if there was a way to have a single value picker like in "Core - ListBox picker single value", but *with* some kind of filter...

        • Ok,fix is in

          By Philippe Riand 1 decade ago

          Thanks for the steps - The fix will be in the next build, which I hope to be soon.