| Issue 1780: | FullCalendar dayClick function conflict with select function | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I have noticed when I am trying to implement the dayClick: and the select functions there seems to be a collision somewhere.
Here is some narrowed down code.
// WHEN YOU SELECT MULTIPLE DAYS
select: function(start, end, allDay) {
var title = prompt('New Select Date:');
if(title) {
calendar.fullCalendar('renderEvent',
{
title: title,
start: start,
end: end,
allDay: allDay
}, true);
calendar.fullCalendar('unselect');
alert("end of select");
}
},
// ADDING A NEW EVENT
dayClick: function (date) {
alert("Day ("+ date +") was clicked");
},
So the issue comes when I "click" on a day, it alerts me which is fine, but then it brings up the prompt for SELECT functionality.
So it runs an ALERT and then a PROMPT window. I am not sure why it's doing this, I haven't been able to narrow down the reasoning, perhaps someone else has had a similar issue?
Please let me know if you have run into a fix or this same issue. Cheers.
Aug 24, 2013
Project Member
#1
adamrs...@gmail.com
Status:
ReproTemp
Aug 25, 2013
This message is being bulk-sent to a number of issues, both [very] old and new.
I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:
http://arshaw.com/fullcalendar/wiki/Report-a-Bug/
Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.
If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.
I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.
Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status:
Invalid
Labels: Type-Bug |
|
| ► Sign in to add a comment |