In fact I can’t enter a numeric value for any function that takes a literal number for a value. I don’t know what I’m doing differently than what I have for the last 5 years. Right where the arrow goes I want to type in a value and no matter what I do it won’t accept a numeric value. Ideas?
I need to add the value as arbitrary text and then convert it to a number. I used to be able to just enter the number in.
The function I see is not + Second, but changes seconds in… I think the reason is that..
I’ve been experiencing this annoying bug myself since last night.
Anytime I try to enter a number literal bubble is interpreting it as a string (even showing quotes around it).
A work around (as annoying as it is) is to create a custom state number with a default value and use that.
Another potential workaround that comes to mind is to use arbitrary text: converted to number. If that is not giving any bugs at least.
This (easier to enter number/string) is definitely a ‘feature’ rather than bug (new property editor reasons) but strange it doesn’t convert to string for you. For me, if used in an expression where it should be a number, it becomes a number.
OK, i get it now - they’ve changed the interface for entering numbers without (so it seems) telling anyone.
@wardey0513 it appears that you now have to select the number from the dropdown menu after you type it (or press enter - but that only works about 20% of the time) instead of just clicking away like you used to have to do until yesterday.
Yes, it appears pressing enter does not work anymore. This is the same for the :default function as well. You will need to select the item from the dropdown list with the “value”.
Looks to have just happened recently since this was the same for the 5+ years I have been using bubble.
Yeah I posted the wrong screenshot but the problem is the same more or less.
Yeah that works, but shouldn’t need to use it.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
