Hi all,

I am evaluating if the RadScheduler is fit for (our) use.

I have a very simple test project: a radscheduler with minimum plumbing (trivial datasource etc.)

If I set the DayEndTime to "23:40:00" and the MinutesPerRow to "26" I get the error:

"Microsoft JScript runtime error: 'this.cells.0.offsetHeight' is null or not an object"

in the line:

d.each(l.rows,function(){Array.add(n,this.cells[0].offsetHeight);

If I set the value of MinutesPerRow to "25" it does not crash, but 26 or higher and bam...

There are also other settings that crash but I report one here. It is reproducable on my system so it

never does not crash with the 23:40:00, 26 values.

Am I doing something wrong here?

regards,

Johan

Hi Veronica,

Unfortunately, I cannot follow your reasoning.

Please explain to me again where I do not get it.

I would expect MinutesPerRow to define the number of minutes that one row represents.

If it is set to 1, there would be 1440 rows in a full day.

If it is set to 1440, there would be one row in a full day.

If it is set to a value between 1 and 1440, there would be anything between 1 and 1440 rows in a full day.

I implemented a zoom function similar to the Wpf scheduler control on (http://demos.telerik.com/wpf/)

Controls > Data > Schedule View > Tick Frequency and Zoom

I limited the range of MinutesPerRow to [1,30]

So if MinutesPerRow = 1 the user has a very large scheduler, that is bad oversight over his appointment that day, but he can resize an appointment very accurately, that is, per minute.

And if MinutesPerRow = 30, the user has oversight over his appointment that day, but he cannot resize more accurate than per half hour.

Anything in between: well, you get it.

Now the settings of DayStartTime and DayEndTime would only function as a filter.

So if DayStartTime is set to, say, 8h and DayEndTime to 17h, there would be 9 hours = 540 minutes in the dayview, but this would not change the mechanics of the zoom.

If MinutesPerRow was set to 1, there would be 540 rows in the dayview

If MinutesPerRow was set to 30, there would be 18 rows in the dayview

If MinutesPerRow was set to a value between 1 and including 30, there would be somewhere between 1 and 18 rows in the dayview.

One more example:

If DayStartTime would be set to 01:00 and DayEndTime to 02:00

If MinutesPerRow was set to 1, there would be 60 rows in the dayview

If MinutesPerRow was set to 30, there would be 2 rows in the dayview

Anything in between: well, you get it.

Now I would not expect this setup to crash at any mentioned settings.

I would not have to handle any exceptions etc.

So please do not solve this bug the wrong way by sweeping some exception under the table (I do not say you do this but please if you should be seduced to do so, don't. Please).

I.m.o.there should be no exception but in stead the expected behaviour I described.

When I reported the bug, I chose to report one reproducible setting: DayEndTime=23.40 and MinutesPerRow=26

If this crashes, a good sw engineer i.m.h.o. would see there is something wrong, regardless of the logic or practicality of the settings.

This is smoke. So there is fire somewhere.

Please do not only combat symptoms. Solve the underlying problem.

regards,

Johan