My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1713: event.end should never be null
1 person starred this issue and may be notified of changes. Back to list
Status:  Duplicate
Merged:  issue 799
Owner:  ----
Closed:  Aug 2013


Sign in to add a comment
 
Reported by m.pah...@gmail.com, Mar 1, 2013
Hello,
I guess that's more an issue than a bug, but I find no documentation for this behaviour and in my opinion it doesn'n make sense:

When I create an event by clicking a one-day(!) slot in week view, event.start and event.end aren't null and I can handle these values (from the fullcalendar-select-event) for example within a dialogeditor. But, when I drag the same event to another slot, event.end is suddenly null - resulting in some codebehind-trouble, cause I didn't know that before. I see no reason for this behaviour and this causes some extra null-checks in clientside editing or codebehind which aren't necessary at all. So, question is, whats the main purpose for the different behaviours of event.end in select-event and dragging-events?

greetings, Mica

Aug 23, 2013
Project Member #1 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Duplicate
Mergedinto: 799
Sign in to add a comment

Powered by Google Project Hosting