Hint timing is much too fast

Viewing 5 posts - 21 through 25 (of 25 total)
  • Author
    Posts
  • #69503
    Support
    Keymaster

    // But they may not show at all (that’s bad).

    I will check it.

    #69659
    HeDiBo
    Participant

    It’s no better in 15.16 đŸ˜’

    #69660
    HeDiBo
    Participant

    Have a look at these two GIF’s.
    GIF Screen2Gif15 shows the timing if HandleDisabledCtrls is False. That timing look OK.
    GIF Screen2Gif16 shows the timing if HandleDisabledCtrls is True. That timing is totally wrong. Having timing like that clobbers the screen with hints.
    I strongly advise to redesign the timing of hints. Especially a hint timing that allows reading long hints (a timing dynamically adjusted to the amount of text) would be enormously beneficial.

    What also shows is the changed position of the hint. If HandleDisabledCtrls is True the hint is much more to the right.

    • This reply was modified 4 years, 1 month ago by HeDiBo.
    Attachments:
    You must be logged in to view attached files.
    #69679
    Support
    Keymaster

    Dick: But they may not show at all (that’s bad).

    Serge: I will check it.

    Dick: It’s no better in 15.16

    Me: Are you sure? Hint is not shown at all still?
    Or, do you mean a timing? It’s not easy to make a delayed hint on disabled control because timer will conflict with standard hint timer. Autoaligning of hint on disabled control will be checked.

    #69685
    HeDiBo
    Participant

    Yes, I mean the timing. It is so terrible, that I disabled hints on disabled controls all together.
    A user cannot put the mouse cursor in any field without getting a hint immediately. That’s very awkward behavior. Screen2Gif16 shows that very clearly.

Viewing 5 posts - 21 through 25 (of 25 total)
  • You must be logged in to reply to this topic.