Faces and changeRoutine do not work well together. #390

New issue

Open

opened 2026-02-20 10:17:05 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 10:17:05 -05:00

Owner

Originally created by @96LawDawg on GitHub (Nov 5, 2021).

I am having a problem with a changeRoutine and faces in the same widget. I made a basic widget where as the faces change, the text changes from -- to A to B to C. I tried use a changeRoutine to feed that value to another widget. But the other widget lags behind by one click. Demo room at https://virtualtabletop.io/wdyq. I used this code on the widgets on the left:

 "changeRoutine": [
    {
      "func": "SELECT",
      "property": "id",
      "value": "copy"
    },
    {
      "func": "SET",
      "property": "text",
      "value": "${PROPERTY text}"
    }
  ]

@bjalder26 found a solution using this code for the widgets on the right:

"changeRoutine": [
    {
      "func": "SELECT",
      "property": "id",
      "value": "label1"
    },
    "var face = ${PROPERTY faces} getIndex ${PROPERTY activeFace}",
    "var text = ${face} getIndex 'text'",
    {
      "func": "SET",
      "property": "text",
      "value": "${text}"
    }
  ]

But there is no reason that my code shouldn't work except for the order in which things activate. @bjalder26 suggests that activeFace updates first, then the changeRoutine fires, then the property updates.

Originally created by @96LawDawg on GitHub (Nov 5, 2021). I am having a problem with a `changeRoutine` and faces in the same widget. I made a basic widget where as the faces change, the text changes from -- to A to B to C. I tried use a `changeRoutine` to feed that value to another widget. But the other widget lags behind by one click. Demo room at [https://virtualtabletop.io/wdyq](https://virtualtabletop.io/wdyq). I used this code on the widgets on the left: ``` "changeRoutine": [ { "func": "SELECT", "property": "id", "value": "copy" }, { "func": "SET", "property": "text", "value": "${PROPERTY text}" } ] ``` @bjalder26 found a solution using this code for the widgets on the right: ``` "changeRoutine": [ { "func": "SELECT", "property": "id", "value": "label1" }, "var face = ${PROPERTY faces} getIndex ${PROPERTY activeFace}", "var text = ${face} getIndex 'text'", { "func": "SET", "property": "text", "value": "${text}" } ] ``` But there is no reason that my code shouldn't work except for the order in which things activate. @bjalder26 suggests that activeFace updates first, then the changeRoutine fires, then the property updates.

deekerman added the

labels

2026-02-20 10:17:05 -05:00

deekerman commented

2026-02-20 10:17:06 -05:00

Author

Owner

@96LawDawg commented on GitHub (Nov 5, 2021):

This may be related to #536

@96LawDawg commented on GitHub (Nov 5, 2021): This may be related to #536

deekerman commented

2026-02-20 10:17:06 -05:00

Author

Owner

@robartsd commented on GitHub (Nov 5, 2021):

I have not analyzed the relevant code recently, but my guess is that changing the activeFace triggers changeRoutine before the properties from the face are copied to the widget. The routine runs, then the properties from the face are copied to the widget without triggering changeRoutne again.

@robartsd commented on GitHub (Nov 5, 2021): I have not analyzed the relevant code recently, but my guess is that changing the `activeFace` triggers `changeRoutine` before the properties from the face are copied to the widget. The routine runs, then the properties from the face are copied to the widget without triggering `changeRoutne` again.

deekerman commented

2026-02-20 10:17:06 -05:00

Author

Owner

@ArnoldSmith86 commented on GitHub (Nov 25, 2021):

I would like to merge #536 when we have compatibility servers for breaking changes working. After that is merged, a changeRoutine would still not trigger for the properties inside the face but a GET inside an activeFaceChangeRoutine should return the expected value.

@ArnoldSmith86 commented on GitHub (Nov 25, 2021): I would like to merge #536 when we have compatibility servers for breaking changes working. After that is merged, a `changeRoutine` would still not trigger for the properties _inside_ the face but a `GET` inside an `activeFaceChangeRoutine` should return the expected value.