Mike Shellim

Aha, that explains it - thanks!

It would certainly be useful to have support for mono screens. Either way, the documentation should be more explicit, there's no mention of restrictions. https://luadoc.edgetx.org/part_iii_-_opentx_lua_api_reference/lcd-functions-less-than-greater-than-luadoc-begin-lcd/sizetext

Hmmm.... it also fails if the range of the GV is altered to -100 to +100 in the GV properties. Also, using function 'a > x' with GV1 as the...

Further thought, rather than the GV being handled incorrectly, could the channel value be the culprit? Its native range is -1024 to +1024, in comparison ops with GVs and constants...

If resetting telemetry casues it to be connected, shouldn't there also be a 'telemetry disconnected' alert immediately preceding the reset? Whatever the logic, the change in behaviour will be annoying...

System alerts are fine if they convey useful info, but not for confirming expected behaviour from a user-defined SF. After all, we don't have a 'sound played' alert for PlayTrack....

The first change of state following the special function triggering is a disconnect. So, if we're going to be consistent, we should hear 'telemetry disconnected' followed by 'telemetry connected'. Alternatively,...

> The old system had the wrong alert first, telemetry recovered. No! A 'reset telemetry' SF did not issue any alert at all. That's the whole point of raising an...

To the devs: the issue is also mentioned in #5214, see comment https://github.com/EdgeTX/edgetx/issues/5214#issuecomment-2187337033 > I use reset telemetry at the start of every flight, triggered at the same time as...

Then why is the alert needed in the context of a reset SF?