@Suty ...

March 12: "we will fix this issue with accidental switching to the forecast part in the next update"

May 5: "It will be fixed in the version 46, planned to be released in the second half of May."

June 2: "Version 46 is planned to be released this week."

June 6: "Small update and apology from our team, this fix and solution will be available with next update to 46.1, since some complications appeared in the development."

And now here we are nearly three weeks since:

June 9: "But I think it will be released in a week."

Look, I've worked in software web app customer service at the manager level, wedged between needy users and oblivious devs, I get that you might caught between a rock and a hard place, but (1) I have a really hard time buying that this can't be resolved with a hotfix. Someone there can certainly invest 30 minutes to find the bit of code that is doing this and comment it out until a permanent fix is sorted, and (2) if you are powerless to make that happen, then at least hold some people accountable to a realistic actionable fix date. If it is going to take 6 months, just say so and stop the credibility bleeding. I've already been burned a couple of times here telling my group that a fix for this is just a couple of weeks away - twice.

Thanks for reading. I don't miss that job.

@Suty appears to have been fixed, thank you and thanks to your devs. My guys are deeply appreciative, as I am sure the bulk of your customers also are.

@Suty appears to have been fixed, thank you and thanks to your devs. My guys are deeply appreciative, as I am sure the bulk of your customers also are.

@Suty ...

March 12: "we will fix this issue with accidental switching to the forecast part in the next update"

May 5: "It will be fixed in the version 46, planned to be released in the second half of May."

June 2: "Version 46 is planned to be released this week."

June 6: "Small update and apology from our team, this fix and solution will be available with next update to 46.1, since some complications appeared in the development."

And now here we are nearly three weeks since:

June 9: "But I think it will be released in a week."

Look, I've worked in software web app customer service at the manager level, wedged between needy users and oblivious devs, I get that you might caught between a rock and a hard place, but (1) I have a really hard time buying that this can't be resolved with a hotfix. Someone there can certainly invest 30 minutes to find the bit of code that is doing this and comment it out until a permanent fix is sorted, and (2) if you are powerless to make that happen, then at least hold some people accountable to a realistic actionable fix date. If it is going to take 6 months, just say so and stop the credibility bleeding. I've already been burned a couple of times here telling my group that a fix for this is just a couple of weeks away - twice.

Thanks for reading. I don't miss that job.

@Suty It's June 1 and the problem persists.

@Suty

Any news on this? Here we are beginning of May and the radar keeps automatically rolling into forecast, it's really frustrating and misleading when the display changes modes uncommanded and you don't notice.