<telerik:RadNotification ID="RadNotification1" runat="server" Animation="Fade" EnableRoundedCorners="True" EnableShadow="True" Height="100px" Width="250px" Position="TopRight" Skin="Default" ShowSound="~/facebook.wav"></telerik:RadNotification>|
KeepTrailingZerosOnFocus |
Boolean |
Specifies whether the control will keep its zero numbers(when set to true) and show them when it is focused, according to the DecimalDigits setting. Otherwise (when set to false) the old behavior is preserved - the control will not display decimal zeros when focused. By default this property is set to false. |
This behavior works radnumrecitextbox mouse click event.
Do not click the mouse when not in radnumrecitextbox zero
RadNumeticTextBox
I have had to implement recurrence on the control because WinForms and WebForms are still unable to work with the same database entries.
In doing so, when recurrence is selected, I only allow daily and create physical entries in the booking table for each appointment. The child appointments point back to the parent but the recurrence rule on the parent stays blank.
All of this works fine (mostly). This allows for editing series or occurrence entries. It does however break the moment that an occurrence that does not appear on the same web page as the master entry is edited. The problem occurs on server side when you select Series on an edit of an existing entry:
#Region "Protected properties" Protected ReadOnly Property Owner() As RadScheduler Get Return Appointment.Owner End Get End Property Protected ReadOnly Property Appointment() As Appointment Get Dim container As SchedulerFormContainer = DirectCast(BindingContainer, SchedulerFormContainer) Return container.Appointment End Get End Property#End Regioncontainer.Appointment returns Nothing. If you choose instance when editing, it works fine. If you have the master appointment on the screen at the time of selecting series, it also works fine.
Any idea why that would be the case and how I can work around it? If there is no suitable solution I will be removing the control from our project as it has created huge controversy around the rendering times, browser compatibility and WinForms integration issues.
Thank you for your time, paying for it was great fun.