Hello,
Thank you for providing a video.
Let me use your example to explain this RadGantt behavior:
1. When you set the Start Date to 01.06.2014 and the End Date to 30.06.2014 you have created a Task that spans 30 days. Start Date determines when the Task starts and End Date determines not when the Task ends, but how many days it spans, in other words by setting the Start and End day you say its starts on 01.06.2014 and it will last 30 days.
2. After you have set the Task's starting date and span if you set a new Start Date you are changing only the starting date and not its span. So when you set it to 15.06.2014 it now means: the task starts on 15.06.2014 and since it lasts 30 days -> End Date automatically changes to reflect that change and the new End Date now is 14.07.2014.
This RadGantt feature makes easier moving your Tasks in time by changing only the Start Date, since changing the Star Date does not change the Task's duration.
Regards,
Ivan Danchev
Telerik
Thank you for providing a video.
Let me use your example to explain this RadGantt behavior:
1. When you set the Start Date to 01.06.2014 and the End Date to 30.06.2014 you have created a Task that spans 30 days. Start Date determines when the Task starts and End Date determines not when the Task ends, but how many days it spans, in other words by setting the Start and End day you say its starts on 01.06.2014 and it will last 30 days.
2. After you have set the Task's starting date and span if you set a new Start Date you are changing only the starting date and not its span. So when you set it to 15.06.2014 it now means: the task starts on 15.06.2014 and since it lasts 30 days -> End Date automatically changes to reflect that change and the new End Date now is 14.07.2014.
This RadGantt feature makes easier moving your Tasks in time by changing only the Start Date, since changing the Star Date does not change the Task's duration.
Regards,
Ivan Danchev
Telerik