Timeline bars of OAP are to long

[lordsurfer]

[lordsurfer]

You use the wrong start date!!!!!

[lordsurfer]

And this will happen if you link the OAP as dependencies:

The tasks are too short...

[janek-bieser]

when logging the start dates to the console, it showed that most date object represented some day at 2pm. that might be one reason why the work packages are too short.
from looking at the timeline source code (APCalendarPanel.java) it seems like the timeline is getting the correct dates but maybe the calculation itself ist wrong.
We might have to rethink the time calculation based on the new MySQL backend. Right now the class TimeCalc.java is a bit difficult to understand and therefore its hard to find and fix bugs.

[lordsurfer]

The WPs are 1 Day...

[janek-bieser]

A workaround for the strange timeline behavior can be found in the iss87_testing_workaround branch (https://github.com/paffman/WBS-Project/tree/iss87_testing_workaround) inside APCalendarPanel#createDataset

This workaround is very limited though. Its expecting you to only use hole numbers for the BAC of any work package (4.5, 7.6..., are not working correctly). So a project might look like this:

One Day is shown from 12:01 am to 11:59 pm. This is only done for displaying the work packages on the timeline. The dates of the actual work packages are not changed.

All the work packages have a BAC of 1 and are correctly represented on the timeline. March 1st ist a Saturday and March 2nd a Sunday, which is the reason for the gap. There is still one problem though with the first work package (1.1.0.0 - Teil 1). Its BAC is 1, the start date is Feb 25 but calculated release is Feb 26. When I created the project it was Feb 25 in the evening, so maybe the tool knows that the next work day is Feb 26 and therefore the work package should be completed at that date. But it is ignoring this fact for the calculation of the start date for some reason.