Hi,
I've been using the time-range-switch for a while now and it does a great job. Thank's for this :)
Just today I made a mistake: I accidentally entered latitude and longitude using the comma as a decimal separator. It took me longer than it should have to find this mistake, as using the comma as the separator is common where I live. The result was that both the start and end time were set to the time at the moment of deployment and, as far as I can tell, the conditon always evaluated true.
Maybe it would be a good thing to include a check here in future releases and mention the need for a decimal point explicitly in the doc.
Hi, I've been using the time-range-switch for a while now and it does a great job. Thank's for this :)
Just today I made a mistake: I accidentally entered latitude and longitude using the comma as a decimal separator. It took me longer than it should have to find this mistake, as using the comma as the separator is common where I live. The result was that both the start and end time were set to the time at the moment of deployment and, as far as I can tell, the conditon always evaluated true.
Maybe it would be a good thing to include a check here in future releases and mention the need for a decimal point explicitly in the doc.
Regards, Daniel