Joe Cheng 980a1e53a7 tabsetPanel binding: unconditionally trigger change on receiveMessage ...

This brings it into line with all of the other input bindings.
The only exception is sliderInput, which has a more complicated
codepath that goes out of its way to force the slider, for its
own reasons; I didn't change the slider for fear of breaking
something, and it also doesn't exhibit the problem I'm here to
fix (next paragraph).

The goal is to ensure that if forgetLastInput is called on an
input, and then that input receives a message (updateXXXInput)
to update its value, BUT the new value is the SAME as its
existing value, that the input binding still acts like something
changed. This is because we need the id/value to go through
the InputSender code path, and alert the server if a previously
frozen input is now thawed.

2020-10-06 14:30:21 -07:00

..

app_template

Fix link

2020-05-08 10:58:19 -05:00

examples

Convert examples to single file apps (#1685)

2017-07-11 14:20:01 -05:00

template

Use inline template logic

2020-10-05 15:48:51 -04:00

www/shared

tabsetPanel binding: unconditionally trigger change on receiveMessage

2020-10-06 14:30:21 -07:00

www-dir

Update missing-UI web page to include app.R

2014-08-07 13:26:07 -05:00