|
01/06/2011, 02:11 PM
#3
 Originally Posted by AndyBrt71
Regarding the overwriting of other entries, there are circumstances where the app will do this intentionally. The rule is that you can only be doing one activity at a time, so if you modify or create an entry that overlaps an existing one, then the existing one will be modified accordingly (either by moving the start time later, moving the end time earlier, or deleting it completely). This rule is checked for all entries on that day, so multiple entries could be deleted. I suspect that this is what you saw. If its anything else then there's a problem I'll need to fix.
Regarding "setting the start/end time to now", this is caused whenever you change one of the time selectors to a time later than the current time. The app doesn't currently allow that, so limits the selection and tells the user that it has done so.
I have on the todo list the addition of a button to set the time to now, but its low priority. When I want to achieve this, I tend to set the end time to anything later than current time in the knowledge that it will be constrained.
I like the idea of alternatively setting the duration. It will require some restructuring of the scene but I can see it would be useful. I'll add it to the todo list.
Regarding the overwriting of other entries, there are circumstances where the app will do this intentionally. The rule is that you can only be doing one activity at a time, so if you modify or create an entry that overlaps an existing one, then the existing one will be modified accordingly (either by moving the start time later, moving the end time earlier, or deleting it completely). This rule is checked for all entries on that day, so multiple entries could be deleted. I suspect that this is what you saw. If its anything else then there's a problem I'll need to fix.
Oh, I think I meant to word this differently. My bad. I had noticed that in other scenes - the app checks and sees if the user wants to filll the gap of time for a deleted entry by extending either the previous or next entry - which i loved. Given that the app is that aware of previous and next entries, I suggest some level of checking be in place to prevent accidentally over-writing entries.
Regarding "setting the start/end time to now", this is caused whenever you change one of the time selectors to a time later than the current time. The app doesn't currently allow that, so limits the selection and tells the user that it has done so.
I have on the todo list the addition of a button to set the time to now, but its low priority. When I want to achieve this, I tend to set the end time to anything later than current time in the knowledge that it will be constrained.
What I was seeing was actually a bug - I would change the start time and the end time would automatically move to match it (any time earlier than now - if it was later - both the start and end times would move to NOW - along with a banner notification telling me the app had done that.)
Regarding the "now" rules - that makes sense - and is helpful that the app does it automatically.
Thanks for considering the duration button.
|
|
|