0 Replies Latest reply on Nov 8, 2012 4:12 PM by JohnDuncan

    Keystroke Selection in Numeric Drop-Down list Fails on Windows

    JohnDuncan

      Summary

      Keystroke Selection in Numeric Drop-Down list Fails on Windows

      Product

      FileMaker Pro

      Version

      12.0v3

      Operating system version

      Windows 7 Pro

      Description of the issue

      When a ValueList displaying a list of numbers derived from another table us displayed in a Drop-Down list it is not possible to select an item by typing a number on the keyboard.  This behavior does not occur on Macintosh.

      Steps to reproduce the problem

      A table is used as the source of a ValueList.  It contains a field "Code".  3 records are in the table:

      Code
      2
      30
      88

      This Field is then used as the source of a ValueList (all values).  A field from another table is displayed linked to this ValueList as a Drop-Down list.  When tabbing into the empty field the Drop-Down list is displayed with nothing highlighted in the list.  Typing a "2" selects the "2".  Typing a "3" selects the "30".  Typing an "8" also selects the "30".  Typing a "3" selects the "88".  Typing an "88" quickly still selects the "30".  The following is the behavior of all of the numeric keys:

      0 - selects the 2
      1 - Selects the 2
      2 - Selects the 2
      3 - Selects the 30
      4 - Selects the 30
      5 - Selects the 30
      6 - Selects the 30
      7 - Selects the 30
      8 - Selects the 30
      9 - Selects the 30
      30 (quickly) - Selects the 30
      88 (quickly) - Selects the 30

      Interestingly if you type a 38 (quickly) it will select 88

      Expected result

      Expected it to behave like a normal Windows 7 drop-down list where you can keystroke to select the item you want.  If I put the same values in a static ValueList it behaves as expected.

      Actual result

      (see above)

      Exact text of any error message(s) that appear

      N/A

      Workaround

      If the field on which the ValueList is changed to a text field then it works correctly although the sorting is now incorrect (for a number - i.e. 100 sorts before 2)