10 Replies Latest reply on Jun 15, 2016 2:46 PM by clbennett

    Text insertion point cursor (vertical bar) persists when cursor is moved outside of field.

    clbennett

      Summary

      Text insertion point cursor (vertical bar) persists when cursor is moved outside of field.

      Product

      FileMaker Pro

      Version

      12.0v4

      Operating system version

      Windows 7

      Description of the issue

      If you are in 'Browse Mode' and 'View As List', if you click in an editable text field in a Header, the cursor 'sticks' as a vertical bar, even when you move the cursor outside the field. The only way to get the cursor back to a 'pointer' is to click somewhere else on the Header, or to mouse into a different part of the layout.

      NOTE: this is similar to the bug already reported, where the cursor turns to a hand over a button, and fails to change back to a pointer when the cursor moves off the button. See http://forums.filemaker.com/posts/9adf46504b .

      Steps to reproduce the problem

      1. Create an editable text field in a Header part.
      2. Save Layout and go to Browse mode, in List view.
      3. With the mouse, click in the text field. The cursor changes to a vertical bar.
      4. With the mouse, move the cursor outside the field. The cursor does not change back to a pointer, but persists as a vertical bar.

      Expected result

      When the cursor moves outside the field, it should change from a vertical bar to a pointer.

      Actual result

      The cursor persists as a vertical bar (until you click elsewhere in the Header or mouse over another layout part). This, as in the case of the hand cursor not changing back to a pointer when moved away from a button, is a violation of one of the oldest and most fundamental user interface rules. The cue from the shape of the cursor as to the activity the mouse is expected to perform is essential to a clear interface, and this violation is surprising and dismaying: both for having occurred at all in professional software in 2013, and for not having been fixed 8 months after being reported.

      Workaround

      None.