GrapeCity Forums

If I accidentally double-click in the blank area (not on an actual date) of the popup calendar on the fpDateTime control, the following error is triggered.  Is there any way to prevent this?

Exception Source:      mscorlib

Exception Type:        System.ArgumentOutOfRangeException

Exception Message:     Year, Month, and Day parameters describe an un-representable DateTime.

Exception Target Site: DateToTicks

 

---- Stack Trace ----

   System.DateTime.DateToTicks(year As Int32, month As Int32, day As Int32)

       DVSystem.exe: N 7655762

   FarPoint.Win.Input.FpDateTime.OnDoubleClickCalendar(sender As Object, e As EventArgs)

       DVSystem.exe: N 00374

   System.EventHandler.Invoke(sender As Object, e As EventArgs)

       DVSystem.exe: N 00000

   System.Windows.Forms.Control.OnDoubleClick(e As EventArgs)

       DVSystem.exe: N 00111

   FarPoint.Win.Input.ElementControl.OnDoubleClick(e As EventArgs)

       DVSystem.exe: N 00004

   System.Windows.Forms.Control.WmMouseUp(m As Message&, button As MouseButtons, clicks As Int32)

       DVSystem.exe: N 00502

   System.Windows.Forms.Control.WndProc(m As Message&)

       DVSystem.exe: N 8788613

   FarPoint.Win.Input.FpCalendar.WndProc(m As Message&)

       DVSystem.exe: N 00044

   System.Windows.Forms.ControlNativeWindow.OnMessage(m As Message&)

       DVSystem.exe: N 00015

   System.Windows.Forms.ControlNativeWindow.WndProc(m As Message&)

       DVSystem.exe: N 00048

   System.Windows.Forms.NativeWindow.Callback(hWnd As IntPtr, msg As Int32, wparam As IntPtr, lparam As IntPtr)

       DVSystem.exe: N 00089

 

Hello,

There is not a way to prevent this. I will need to report this as a bug for the development team fix for the next maintenance release.

---

Scott S.
Product Manager, Spread ASP.NET
GrapeCity FarPoint

Hi Scott,

I just updated to Farpoint Input Pro 1.0.16 but still get the same error when I click in the blank area of the calendar.  We have been able to narrow the problem down a bit.  It only happens on months with less than 31 days if we double-click in the space where the 31st would be.  February does it for the spaces that would contain the 29th - 31st.

 Thanks,

Gina

Gina,

This bug has not been fixed yet. I do not have any updates when the next maintenance release for customer bugs will be.

---

Scott S.
Product Manager, Spread ASP.NET
GrapeCity FarPoint

After updating to v1.0.16, we have found that we can no longer Hide the Lead Zero on the fpDouble control.  Even though the property is set to Hide, the control defaults with a 0, which causes problems for us.

Gina,

I have tested the reported behavior with 1.0.16 version of fpDouble control and could not replicate the issue at my side. i tried hiding the LeadZero through code as well as properties and it is working as expected. On hiding the leading zero, the control is not showing any leading zero.I used below to test the issue:

        FpDouble1.Value = 0.134
        FpDouble1.LeadZero = FarPoint.Win.Input.LeadZero.Hide

And it it working as expected i.e hiding the leading zero. Any additional steps required to reproduce the issue at our side?

---

Suresh Singh Dasila
GrapeCity FarPoint

If I set the Decimal Places property to 0 then the control defaults to 0.  I would use the fpInteger control but there is no option to Hide the lead zero.

Hello,

This is correct behavior. Here is the documentation from our online help file on the issue.

When this property is set to Show, the control displays a leading zero for values less than 1.0 and greater than -1.0, for example, "-0.21".

Note: The value zero always displays a leading zero.

If you want to display a blank value in the control instead of a zero, you would need to set the Value property to null (Nothing in VB). And first you would need to set the AllowNull property to True.

FpDouble1.AllowNull = True

FpDouble1.Value = Nothing

---

Scott S.
Product Manager, Spread ASP.NET
GrapeCity FarPoint

In version 1.0.13, setting the LeadZero property to Hide works no matter what the decimal places is set to (on form load, the control is blank).  This seems like the proper behavior to me.  Are you saying that the control was not working properly under version 1.0.13?

Hello,

That is what I am saying. If you were seeing a different behavior in the older release, then this was a bug in that release. The way it is currently working is correct.

---

Scott S.
Product Manager, Spread ASP.NET
GrapeCity FarPoint

Why, then, does the control hide the 0 (like I want it to) if the decimal places property is set to anything but 0?  Is it considered a bug when the control hides the zero in that instance?

Hello,

This should not be.. The value of 0 should always return 0. I will report this as a bug for the development team to fix for the next maintenance release.

---

Scott S.
Product Manager, Spread ASP.NET
GrapeCity FarPoint