It appears to me that an initial content field does not allow the dynamic data to start with a number. What is the best way to write “100 - Input 1?” I’m having difficulties with the response of the element when I write it as '“(Input1 * -1) + 100.” The -1 causes delays in the response of the element, but not when I change it to + 1. Does that make sense?
maybe you should just put it in an Arbitrary text: converted to number

put the variable first and then you can do math, multiply by -1, since it is negative
That’s the way I have it currently. The problem is the element has a hard time processing the negative number and causes delay in processing it. When I remove the negative it operates just fine. Hence the problem.
I don’t know how to write that in an equation.
you can use custom state in this case. Set up a custom state with option 100 and reference it to where you want to use it.


do it this way then, an auxiliary variable with the initial value of 100, using variables it is possible to do the math
It’s a strange problem, the plugin element ListofNumbers just doesn’t like the negative number, as in “(Input 1 * -1) + 100.” When I replace the negative with a positive, (Input 1 * 1) + 100, it runs fine, but with the negative number it produces a delay–but only on the first time the input is changed, never after. Isn’t that weird?
HOWEVER, this list of numbers is the data source for the repeating group. If I remove the repeating group from the page, then the Input 1 and ListofNumbers works correctly. So somehow List is interacting with RG.
I should note, the “delayed response” is within Input 1 itself, meaning the input itself freezes when you type 2 digits into the input, only on the first time the page is loaded and only when the negative appears in the List.
I get this delay consistently in the input, even with nothing else on the page but a text element. sample page preview
It looks like Bubble is caching and delaying the typed input to avoid continuously changing the value. Unfortunately the first digit typed is sent through immediately, resulting in an invalid single-digit value, a delay, then the full value.
One workaround is to put zeroes in the List of Numbers, and set a Conditional to only use the input value when it is valid, i.e. within the range.
Very good, Misha. I think that works. I’m reviewing.
I added this so it knows what to do with an invalid entry, otherwise it blanks out. The age is saved in workflow so it remembers the last valid entry.
It seems to work. It’s still odd that the original fails only on the first time after page load.





