On 17/09/2015 20:15, Colin Holgate wrote:
It was a bit flakey, but I’ve learned things since then. All the app did was to
switch to the information screen that corresponded with the nearest beacon.
But, if the nearest one is fluctuating by enough, and the second nearest beacon
fluctuates and becomes stronger just for a moment, the screen would switch.
Also, sometimes a beacon will not read at all. I think that happens if the
polling happens just after the beacon has finished transmitting for that second.
In electronics engineering, these types of issues are quite common
(especially on input circuits). Usually you can get around it by
inserting some level of hysteresis.
Did you consider that approach? I imagine you could do it by treating
the currently-selected beacon as x feet nearer than the signal suggests
for the purpose of deciding whether to switch beacons.
Peter
--
Dr Peter Brett <[email protected]>
LiveCode Open Source Team
LiveCode on reddit: https://reddit.com/r/livecode
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
