Question
I want to format the text of the area for the LongIntervall of the DateScaler but I found some inconsistent appearances. Please take a look at the attached sample. My code begins at line 520.
As long as the DateScaler resolution is days and the DateScaler shows a part of a month the OnDateScalerDrawString method will be called and the Argument contains the correct OutputText. But if the resolution is hours the text disappears when the span is only from 00:00 to 12:00 or from 13:00 to 24:00. The same problem appears if you move the 12:00 marker beyond the StartTime or the 13:00 marker beyond the StopTime.
There is also a draw problem at time resolution minutes10 and minutes. The left box divider disappears if you scale to the right and the 10 minutes marker moves beyond the DateScaler StartTime. Another Question: Why the boxes showing the time goes from 0:30 to 0:30 and not from 0:00 to 0:60?
Answer
I have looked over your sample.< ?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
You are correct in your observations.
When the resolution is Day/Hours the definition is to draw the box at daystart (24:00) and the Daylabel at 12:00, however if the scale is set in such a way that the resolution is Day/Hours but neither 24:00 nor 12:00 is on screen, no box start and no label point will be defined, then no label will be placed (and this is your observation). This is not currently treated as a bug.
The same strategy is used for all the scaling, but with different values. So the thing you saw for 10min/1min is pretty much the same.
>Another Question: Why the boxes showing the time goes from 0:30 to 0:30 and not from 0:00 to 0:60?
– When we have resolution larger than a day we always place the box at start and stop of the chosen resolution (day,week,month, quorter etc) and the label in the middle of the box. But when the resolution is less than a day in the upper band it is desirable to place the upper label at the correct value position (ie 09:00:00), and hence we must place the box around the position -> 30, 30
At this point we are not prepared to make any changes to the current logic, but we appreciate your feedback. Please feel free to argue with our positions if you do not agree.