Message-ID: <1839630559.8667.1711654519262.JavaMail.web05$@web05> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8666_367201770.1711654519246" ------=_Part_8666_367201770.1711654519246 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Sets or returns the category value at which the value (y) axis crosses t= he category (x) axis, represented as DateTime
=20public System.DateTime ValueCrossingPointAsDate{ get; set; }=20
Public Property ValueCrossingPointAsDate() As Date=20
This property can be found in Excel under the "Axis Options" f= or the category axis. It corresponds to the "At date" choice unde= r the "Vertical axis crosses:" section (or under "Horizontal= Axis crosses" section for bar charts). This choice is replaced with &= quot;At category number" if the category axis is not a date axis. If t= his is the case, CategoryAxis.ValueCrossingPoint will be more appropria= te.
=20New charts will have their axis crossing point set to "Between date= s" and the value returned for this property is Dec 31st, 1899 (an ille= gal Excel date). If this property is set to any date, then the chart will h= ave its crossing point manually set to that date and will no longer be auto= matic. Currently, there is no way to reset a chart to use an automatic axis= crossing point.
=20If this property is set to any date before Jan 1st, 1900, the ValueCross= ingPointAsDate will instead be set to Jan 1st, 1900.
=20If CategoryAxis.AxisCrossesMaxCategory is set to true, then this= property will have no effect on the resulting file.
=20This property is directly tied to CategoryAxis.ValueCrossingPoint. T= he number of days this date passes Jan 1st, 1900 corresponds to the value o= f ValueCrossingPoint, plus one. So for example, if this property is set to = Jan 16th, 1900, then ValueCrossingPoint will be set to 16.