4.2 and 4.3 Trial 99 Columns
18 years ago.
Here is the stack:
> JScript anonymous function JScript
JScript anonymous function JScript
_ctl0_MainPageContent_schedule_Init JScript
JScript global code JScript
It is throwing the exception in the WebResource.axd file at:
$a.width=$C.Width+"%";
The uniqueID for $a is "ms__id1".
$C looks like this:
Width: 0
ToolTip: null
Name: "12/4/2007<br/>1-a"
InnerHTML: "12/4/2007<br/>1-a"
Date: "December 4, 2007 00:00:00 +0000"
Value: "1"
BackColor: "#ECE9D8"
I hope this helps.
Thank you,
Scott
for (int i = 0; i < 100; i++)But isn't it possible that you already have some Columns defined in the .aspx template (I would guess for 2 columns) and add more columns in the code behind without calling DayPilotCalendar1.Columns.Clear() first?
{
DayPilotCalendar1.Columns.Add(i.ToString(), i.ToString());
}
We aretrying to use the calendar as an interactive ui for scheduling service routes. The columns must describe a route for a day with the rows being time slots. (We have an existing app (winform) that uses DBI's calendar control in that format). While there is a practical limit to how many columns a user could deal with, it is well within reason that the person doing this task will wish to see all routes (could be 100) over a 6 day period. The bottom line is, the pivioted view provided by the Scheduler control will not do.
What would be best is to allow (column width in pixels) * (number of columns)to determine the table width.
This question is more than 1 month old and has been closed. Please create a new question if you have anything to add.
DayPilot