Community
Participate
Working Groups
Build Identifier: When using an AbstractPlannerField with PLANNING_MODE_WEEK, the following time ranges are not shown correctly: - A time range having the same start and end date and occurring on the first day displayed in the AbstractPlannerField -> The week is not marked appropriately. - A time range of at least two days, whose end date is the first day of a second week -> The second week is not marked appropriately. Reproducible: Always Steps to Reproduce: The attached scout application (ZIP file of the workspace) reproduces the failure (red marked rows). The attached patch solves this issue. However, this patch was made with only PLANNING_MODE_WEEK in mind, not other planning modes. Different implementations of the method org.eclipse.scout.rt.client.ui.basic.activitymap.TimeScale.getRangeOf(Date, Date) for differend planning modes might make sense.
Created attachment 200243 [details] Scout Application to reproduce the bug.
Created attachment 200244 [details] Possible patch.
Fixed and commited to branch 2011-Jun for the release 3.7.1 and to trunk for release 3.8.0.
I had to revert this changes. The Display was correct with this patch, but try to select one week. It does not work. Please correct it. If you need help, we can look over this bug together.
We came to the conclusion that we can not fix the problem with the attatched patch, because it also affects the behaviour of the selection box. As a workaround, we came to the conclusion that the client has to provide the data for the planner field such that the information is displayed correctly. However, this is not a viable solution in the long run; the concerned code (AbstractPlannerField/TimeScale/TimeScaleBuilder) should be redesigned.
Created attachment 202591 [details] Possible patch 2. Patch contains both a proposed fix and a test form.
Committed patch to trunk for release 3.8.0.
Created attachment 210856 [details] Patch that handles boundaries for PLANNING_MODE_DAY and PLANNING_MODE_WEEK correctly When using modes PLANNING_MODE_DAY or PLANNING_MODE_WEEK the selected columns are not handled correctly due to the used values at the end boundaries of the MinorColunns. During construction of a MinorColumn, 1ms is subtracted from the end boundary. When fetching the column index for a given end time, it has to be checked if the given end time fits into the begin and end time interval of the column. Otherwise, the previous column has to be returned.
patch applied for Juno. thank you Ken!
Comment on attachment 202591 [details] Possible patch 2. added iplog flag for this patch
ticket closed. deliverd as part of eclipse scout 3.8.0 (juno release train)
