Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369396

Summary:

drawEventsDownToTheHourAndMinute calculates wrong start and length of the events

Product:

z_Archived

Reporter:

Jürgen Reichl <reichljuergen>

Component:

Nebula

Assignee:

Emil Crumhorn <emil.crumhorn>

Status:

CLOSED INVALID

QA Contact:

Severity:

normal

Priority:

CC:

michel.schaffers, nebula-inbox, tilman.reinhardt

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
quickfix	none

Description Jürgen Reichl

2012-01-23 10:14:03 EST

Build Identifier: M20110210-1200

if drawEventsDownToTheHourAndMinute is true it calculates the wrong start and the wrong length of the GantEvent!

Reproducible: Always

Comment 1 Jürgen Reichl

2012-01-23 10:15:53 EST

Created attachment 209918 [details]
quickfix

solution without minutes.

Comment 2 Michel Schaffers

2012-02-25 04:56:45 EST

Made the same observation, draw to the minute feature does not calculate correct ends of an event.

fix the wrong beginning:
public int getStartingXFor(final Calendar date) {
...
            final float widthonehour = getDayWidth()/24.0f;
            final int hours = date.get(Calendar.HOUR_OF_DAY);
            extra = (int) (widthonehour * hours);
...

fix the wrong length:
private int getXLengthForEvent(final GanttEvent event) {
...
        if (_drawToMinute ) 
        {
            int minutesbetweenstartandend = DateHelper.minutesBetween(event.getActualStartDate().getTime(), 
												                    event.getActualEndDate().getTime(),
												                    false,  // assume same date
												                    false); // assume same hour
            return minutesbetweenstartandend * getDayWidth() / 24 / 60;
        }
...

Comment 3 Tilman Reinhardt

2012-03-01 08:50:09 EST

Actually i cannot reproduce the wrong behavior of drawEventsDownToTheHourAndMinute.

But i made the same observation as Michel and opened a new bug 372970 for this!

Comment 4 Wim Jongman

2019-12-12 15:58:03 EST

This bug does not have a target milestone assigned and is automatically closed as part of the 2.3.0 release cleanup.

It could be that this bug is accidentally closed for which we apologize.

If this bug is still relevant, please re-open and set a target milestone.