Stopwatch + AsString Integer bug

As it was already marked as fixed, here is a new bug report for the AsString node.

I am on 30.2 x64 and when set to integer AsString is still very buggy. Connect a stopwatch to it and it will a) not be converted to an integer and b) only update once a second. LFO updates twice a second.

When set to Real none of these problems occur. Strange indeed, see attached patch. While on the subject of Real and Integer, why are there soo many different kinds for each. I never use anything other than Real (Min Float … Max Float) and Integer (0 … Max Int) and never felt i needed something else, so what in the world are the others used for?

AsStringStopwatchBug.v4p (6.2 kB)