Navigation
User login
Search
Unable to select 12:30 PM. Incredibly frustrating!!
caschleen — Fri, 09/25/2009 - 17:54
I love TimeLogger, and just recently upgraded to 1.3.1 on the new 3.1.1 OS. But here's the deal. I went back to start a timer for something I had done the day before. I entered Friday 11 AM as the start time. But when I went to stop the timer at Friday 12:30 PM, IT WON'T LET ME! It keeps switching between AM and PM and then back to some bizarre default of 11 PM. I've tried everything! I tried selecting the minutes first, then the PM, then the 12... then it just slips back to 11 PM. If I try to choose 12 PM, it flips it to 12 AM. If I flip it to PM, it changes the hour to 11 PM. So bizarre and SO FRUSTRATING.
Another bit about the whole thing: since my upgrade, the number scrolling is incredibly choppy. I have plenty of space so it's not an issue of memory.
Thanks.
RE: Unable to select 12:30 PM. Incredibly frustrating!!
costmo — Thu, 10/22/2009 - 01:50Hello,
Things will be a little wonky if you set a timer for a previous day in the AM and go to reset the stop timer during the current day. Sorry. It's a behavior of Apple's date pickers, and we don't have a lot of control over them unless we decide to not enforce the setting of a stopped timer to a date and time that is after the start time.
If you run into this scenario, you should be able to do the following:
- Set the start time as you want it. For example, 11 AM on the previous day.
- When you go to set the stop time, set the time BEFORE you change the date.
- After setting the time (to 12:30 PM, in this case), set the date to the previous day.
The important thing here is to set the time before you set the date.
By the way, people who have their date format set to 24 hour format (most places outside of the USA, and those who prefer it within the USA) would not experience this issue.
The choppiness issue doesn't have to do with available disk space on your device. There is a fixed amount of operating memory on the device that is separate from the storage space. The choppiness comes from the amount of that memory that is used, combined with the utilization of the device's processor. This application is particularly data heavy and has relatively complex relationships in its data set, so it will have a tendency to react slowly in spots. That will be increasingly true with the more data you are trying to work with at one time. We are continuing to work on ways to optimize the application's utilization of the limited resources that it has.
Thanks