I’m facing an issue here where if a double click on the time ruler fires the beforeAppointmentCreate() method with the correct selected time interval for appointments. But if a right click on the time ruler without previously selecting a time interval, the selected time interval “Start” is inaccurate.
Is there any way I can capture the TimeRuler click to then update the selected time interval on right click?
As per my understanding when right click on the TimeRuler, the default context menu appear so are you disabling the context menu in BeforeContextMenuShow event? If yes so when you double click using right mouse button, the Appointment dialog opens with correct time interval at my end.
If my understanding is incorrect, please provide some more information. Also please share a stripped down sample of what you are trying to do at you end. Please mention the Build Version of the controls that you are using.
To get the Build Version of your control right click on the control on designer and select the Properties option, this will open a Properties dialog box of that control then on the bottom of that dialog there is a
“About ControlName” option, click on that option. It will show a nag screen in which your control build version and product key details are mentioned.
Follow these steps to reproduce what I’m referring to.
1) Double click 8am on the time ruler to bring up the new appointments window.
2)Recognize that start time is correct at 8am. Thats perfect.
3)Close appointments screen.
4)Right Click time ruler at 10am to bring up context menu, click new appointment.
5)Recognize that start time is still set to 8am. Thats incorrect because the right click on the time ruler was made at 10am.
So the issue I’m having is that when users right click on the time ruler to create new appointments, the selected start time isn’t the time that the user selected on the right click.
Below, I’ve attached a sample project. I’ve also tested this on a version from 2018 and still was able to reproduce this bug. Currently, our application is released to our clients with version 2.0.2113.183
Any suggestions to handle this would be great. Thanks
