This is a migrated thread and some comments may be shown as answers.

OnClientAppointmentClick after OnClientAppointmentResizeEnd

13 Answers 129 Views
Scheduler
This is a migrated thread and some comments may be shown as answers.
Ian Russell
Top achievements
Rank 1
Ian Russell asked on 20 Oct 2008, 03:40 PM

How to prevent OnClientAppointmentClick event happening as part of OnClientAppointmentResizeEnd event? When I handle the OnClientAppointmentResizeEnd I do not want the OnClientAppointmentClick to fire.

13 Answers, 1 is accepted

Sort by
0
Peter
Telerik team
answered on 20 Oct 2008, 04:10 PM
Hello Attila,

Could you please elaborate on what exactly you need to achieve. The first question that comes to my mind is that you cannot simultaneously resized the appointment and click on it so I wonder what are you concerned about? Please, explain and we will try to provide you with a solution.


Kind regards,
Peter
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Ian Russell
Top achievements
Rank 1
answered on 21 Oct 2008, 03:09 PM
If you look at your Client-Side Events online example and try to resize the schedule appointment, there is an event log:
Appointment resize start: Breakfast
Appointment resizing: Breakfast
Appointment resizing: Breakfast
Appointment resizing: Breakfast
Appointment resizing: Breakfast
Appointment resizing: Breakfast
Appointment resizing: Breakfast
Appointment resizing: Breakfast
Appointment resize end: Breakfast
Appointment click: Breakfast

I do not want the last event(Appointment click) to fire when I am resizing an appointment. But I do not want to disable the OnClientAppointmentClick completely. I just do not want it to be a part of the client-side appointment resizing/moving.
0
Peter
Telerik team
answered on 21 Oct 2008, 03:33 PM

Thanks! We verified that this is a bug with RadScheduler. I have logged it and our developers will see to it.


All the best,
Peter
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Matthew
Top achievements
Rank 1
answered on 04 Dec 2008, 05:49 PM
Just wondering, has this been fixed yet?  Thanks in advance.
0
Peter
Telerik team
answered on 05 Dec 2008, 01:35 PM
Hello Matthew,

Unfortunately, it hasn't been fixed yet. I will remind our developers about it. Thanks.


Peter
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Oleg
Top achievements
Rank 1
answered on 15 Jan 2009, 06:54 PM
Has it been fixed in version 2008.3.1314.20 by any chance?
0
Peter
Telerik team
answered on 16 Jan 2009, 03:38 PM
Hello Oleg,

I just tested the online example and apparently it has been fixed.


Regards,
Peter
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Ian Russell
Top achievements
Rank 1
answered on 22 Jan 2009, 04:32 PM
It is still doing it for the OnClientAppointmentMoveEnd.
0
Peter
Telerik team
answered on 23 Jan 2009, 01:21 PM

You are right. It happens very rarely in IE7, but in Firefox 3 the problem occurs almost for every test. We will fix it in a couple of weeks, so you can try then with the latest internal build.


Kind regards,
Peter
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Matthew R Longhouse
Top achievements
Rank 1
answered on 22 Mar 2009, 06:19 PM
As of the 3.18 build, the onClientAppointmentMoveEnd firing twice has not been fixed yet. I am working on a workaround atm on my end, hopefully it gets addressed with one of the latest internal builds.
0
Peter
Telerik team
answered on 24 Mar 2009, 03:52 PM

Hello Matthew,

How exactly do you test the onClientAppointmentMoveEnd event. Our local tests show that everything is fine with this event.

All the best,
Peter
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.
0
Matthew R Longhouse
Top achievements
Rank 1
answered on 24 Mar 2009, 05:44 PM
Hi Peter,

I sent in a support ticket for this issue as well. We are setting it like:

OnClientAppointmentMoveEnd="onClientAppointmentMoveEnd"

as part of the RadScheduler declaration. The onClientAppointmentMoveEnd is just a javascript function which I put in with an alert to see if it got there or not. We are on 2008.2.826.20, where it fires normally. Its when I tried to upgrade to q1 2009 which is when it began firing twice. I logged in and got the latest internal build, tested with that, and it was still firing twice. I noticed there was a hotfix there as well, but that is for 3.5 only, and we are still on .net 2.0.
0
Peter
Telerik team
answered on 25 Mar 2009, 02:23 PM

Thanks for the additional information. Yes, you are correct abou this. What happens is that if you test with an alert, the post back is cancelled on the first alert display so in this case the event fires twice. This problem occurs only if you use an alert. In your scenario, do you need to use an alert dialog. If not then you sould be concerned about this issue.

We will try to avoid this behavior for future versions.

Best wishes,
Peter
the Telerik team

Check out Telerik Trainer , the state of the art learning tool for Telerik products.
Tags
Scheduler
Asked by
Ian Russell
Top achievements
Rank 1
Answers by
Peter
Telerik team
Ian Russell
Top achievements
Rank 1
Matthew
Top achievements
Rank 1
Oleg
Top achievements
Rank 1
Matthew R Longhouse
Top achievements
Rank 1
Share this question
or