BoldSignEasily embed eSignatures in your .NET applications. Free sandbox with native SDK available.
[script] function showRadialMenu() { //create instance for radialmenu var radialMenuInstance = $('#defaultradialmenu').ejRadialMenu("instance"); // call the private function to show the radailmenu radialMenuInstance._radialClickHandler(); } |
<code> [Index.cshtml] if ($(args.events.target).hasClass("e-workcells") || $(args.events.target).hasClass("e-alldaycells") || $(args.events.target).hasClass("e-monthcells")) { this._cellSelection(args.events.target); var renderDate = (this.model.orientation == "horizontal" && this.currentView() == "month") ? this.monthDays : (this.model.orientation == "vertical" || this.currentView() == "customview" && this._dateRender.length <= 7) ? this.dateRender : this._dateRender; renderDate = this.model.orientation == "horizontal" && this.currentView() == "customview" && this._dateRender.length <= 7 ? this._dateRender : renderDate; var curDate = new Date(renderDate[this._cellIndex]); //Here you get the current date of selected cell alert(curDate); } else { var _target = $(args.events.target); var appoint = _target.hasClass("e-appointment") || _target.hasClass("e-monthappointment") || _target.hasClass("e-alldayappointment") ? _target : _target.parents(".e-appointment,.e-alldayappointment,.e-monthappointment"); if (appoint.length > 0) { var appId = parseInt(appoint[0].id.split("_")[1]); // Here we are find the appointment Id based on the target var schObj = $("#Schedule1").data("ejSchedule"); var app = new ej.DataManager(schObj._processed).executeLocal(new ej.Query().where(schObj.model.appointmentSettings["id"], ej.FilterOperators.equal, appId)) // Here we are find the appoitment details based on the appointment Id var appointmentSubject = app[0].Subject; //Here you get the appointment details on appointment right click alert(appointmentSubject); } |
Since your last query is different from your previously reported issue we have created a branched incident 144077. Your query will be addressed in the incident 144077. We request you to follow up with the incident 144077 for further updates.
Regards,
Arun Kumar S