Minor issue with action Input Dialog in 1.30.0
Posted: 06 Mar 2016 16:30
Hi Martin,
I've found what appears to be a very minor bug in version 1.30.0. My Galaxy Note 5 is set for 12 hour time and I have a number of flows that use the action Input Dialog with a dialog type of Time. If I run the flows before 12:00PM and enter an hour and minute that's after 12:00PM, the hour and minute will display correctly but AM/PM indicator does not change to PM, and of course this results in getting an AM value. For example, if the current time is before 12:00PM and I enter 1:30PM, the resulting value is 1:30AM. The only way I can get the correct value is by tapping on PM first and then setting the hour and minute. This behavior is consistent and my process of tapping on PM works every time, but if I don't select PM first it will result in an AM value every time. I never had this occur until I updated to the Material Design version of AutoMagic.
I hope I've explained this so it makes sense. Again, it's a very minor issue that has a simple workaround, but this behavior is different from past versions of AutoMagic and I thought I would let you know about it.
I've found what appears to be a very minor bug in version 1.30.0. My Galaxy Note 5 is set for 12 hour time and I have a number of flows that use the action Input Dialog with a dialog type of Time. If I run the flows before 12:00PM and enter an hour and minute that's after 12:00PM, the hour and minute will display correctly but AM/PM indicator does not change to PM, and of course this results in getting an AM value. For example, if the current time is before 12:00PM and I enter 1:30PM, the resulting value is 1:30AM. The only way I can get the correct value is by tapping on PM first and then setting the hour and minute. This behavior is consistent and my process of tapping on PM works every time, but if I don't select PM first it will result in an AM value every time. I never had this occur until I updated to the Material Design version of AutoMagic.
I hope I've explained this so it makes sense. Again, it's a very minor issue that has a simple workaround, but this behavior is different from past versions of AutoMagic and I thought I would let you know about it.