AnVn @ 21.09.2014, 01:14
Only the "stupid remove" remains.
jumha @ 20.09.2014, 21:31
Paid - zhmaknul on the same cheboksu with adjustable reaction
... for example, become invisible. The result is the same.
AnVn @ 21.09.2014, 01:14
and it will be all the time "hanging out" (in this first, and then in the past tense)
jumha @ 20.09.2014, 21:31
event at midnight will be transferred to the next day at the same time
AnVn @ 21.09.2014, 01:14
how many of these events happened in the year? That's right, 52
You are not quite right. Even just wrong. There is a base, there is one entry. Depending on the request (report) it will be displayed in the required time-dates. But there is one entry and will not ship the system, as if I created 52 independent events (record in the database) in the database. And I can this record (and display it in the designated dates) to remove a single click, if you choose "delete all events." This would be impossible with independent events (entries in the database). Something like this.
AnVn @ 21.09.2014, 01:14
A task - it is only one! And always in the nearest scheduled time
I wrote above - a recurring event are also one record in the database. But the fact that repetitive tasks is displayed in the calendar is always a time to the nearest date (huh? Not tested) could be a minus. It is necessary to me to stretch the time for 2 weeks in advance, and there will be no more weekly tasks ambush ... And the events in each week will illuminate.
AnVn @ 21.09.2014, 01:14
Events - this is a reminder that "something" to happen in due time ... ie in general that usually lies outside of our ability to influence the fact ...
AnVn @ 21.09.2014, 01:14
Yes, there were recently "floating events" that can be moved relative to the scheduled time, but the sense and logic of the term "event" from it have not changed.
Who cares how we'll determine ... that they are moved, if forget about them, and that's that problem that event. This program, she do not care about our notions of time management: D.
AnVn @ 21.09.2014, 01:14
And here is the problem - it is quite another matter. This is exactly what depends entirely on us, on our actions. We can do and not do, but the need to perform this task from this will not go away. It just will not be performed, but in the "past" will not go away, in contrast to the events of her anyway, sooner or later you need (and have to) perform.
paraphrase:
assigned to the event - it is exactly what depends entirely on us, on our actions. We can do and not do, but the need to perform this event from this will not go away.
What has changed?
This is your vision and organization, I understand and agree in principle. But I was uncomfortable to use tasks which they are subject.
I bore on a horoscope, I need to paint the day time and clearly see it. It is possible and convenient to do only with the events, tasks are displayed as a list on a specific date. And "floating" event is not going anywhere, as the problem, you forgot already. And if need be can be displayed as a task with a daw "for the whole day."
IMHO, this is a wonderful program is very flexible configuration, and bind it to the interface objects, each is free to its ideology, the work program of this does not change. One convenient me, you on the other, I listened to you, something has opened, and on occasion use. I think that the benefits of such discussions is unquestionable for all.
Here are just a program quite buggy, Synchro anyhow have to wipe, however: suicide: