DayPilot Forums

DayPilot is the best open-source Outlook-like calendar control for ASP.NET.
DayPilot Pro Demo (Calendar control)
» DayPilot Pro live demo (Calendar control)
DayPilot Pro Demo (Scheduler control)
» DayPilot Pro live demo (Scheduler control)
Home » Bugs » Cannot enter new event with an existing event in slot.

Cannot enter new event with an existing event in slot.

How does one enter multiple events within a slot, as the event fills the slot and hence no ability to add is available?

Anonymous - 4/25/2007 10:21:02 PM
There should be a special space (5px) after events in each day that allows clicking on the underlying time slots.

This is working fine in IE 7 and Firefox 2. There is an issue in IE6 (when you move/resize an event using AJAX callback it then fills this special space). I'm working on a fix for that.

Is this what you describe?
Dan Letecky - 4/26/2007 8:58:20 AM

I think you will find it is your XHTML usage, which IE 6 does not support..

Anonymous - 4/29/2007 9:58:29 PM
The sandbox version is now a bit better. It keeps the same event width in IE6 after a callback.

However, if there are two or more overlapping events in the same column they are not aligned to the left side and the free space is divided (IE6).

I'm still going on....
Dan Letecky - 4/30/2007 1:31:39 AM
Your sandbox version has no space visible...
Anonymous - 5/1/2007 5:36:53 AM
Yes, I'm still playing with it a little bit.
Dan Letecky - 5/1/2007 2:53:05 PM
OK. I had to throw my previous solution (from 4/30/2007 1:31:39 AM) away. It was keeping the width after AJAX callback but it was breaking the top of the calendar.

Now I have a usable (but no perfect) solution:
  1. No problems in IE7.
  2. No problems in FF2.
  3. No problems in IE6 if there are not concurrent events.
  4. Concurrent events in IE6 are not aligned to the left side of a column. However, the space is distributed among them so it is possible to use it for time range selecting.
It's in the sandbox and it will be a part of DayPilot Pro 3.6 release.

This has been a really tough issue. In order to resolve it in full, I will have to redesign the event rendering process to involve more client-side JavaScript. That will have a lot of consequences so I will keep it for one of the next releases.
Dan Letecky - 5/1/2007 4:58:18 PM
Post reply