• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Button Tooltip Not Shown

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Button Tooltip Not Shown

    Hello,
    I would like to submit a bug where a tooltip may not show. To reproduce:

    1. Add three app vars:
    a.) An app var named "tooltip". Note that to easily reproduce this bug we are going to use this tooltip app var like a status.
    b.) An app var named "isEnabled". Give it the expression:
    Code:
    {[tooltip]} == "E1"
    c.) An app var named "isDisabled". Give it the expression:
    Code:
    !{[isEnabled]}
    2. Add 3 buttons to a grid widget.
    a.) A button titled "Enable with tooltip E1"
    Set the On Click action to set the app var "tooltip" to the text "E1".
    b.) A button titled "Disable with tooltip D1"
    Set the On Click action to set the app var "tooltip" to the text "D1".
    c.) A button titled "Button with Tooltip".
    In the "Link To App Variables" for this button, put "isDisabled" in the Disable field and put "tooltip" in the Tooltip field.

    3. Now that the app is setup. Launch the app and click the "Disable with tooltip D1" button. Observe that the "Button with Tooltip" becomes disabled and hovering over it shows a tooltip of "D1". All that is good and expected so far. But now click the "Enable with tooltip E1" button and the "Button with Tooltip" becomes enabled as expected; however, the problem is that no tooltip comes up if you hover over the "Button with Tooltip". The tooltip should have read "E1" if there were no bug.

    Note that if I had set isEnabled to true/false explicitly when the buttons are clicked, instead of having the expression of {[tooltip]} == "E1", then it does not have this tooltip issue.
    Attached Files

  • #2
    Thank you for the detailed explanation of the bug. We believe this will be fixed in the next update

    Comment

    Working...
    X