Re: [libreoffice-users] Unexpected behavior while writing Calc Functions

Hi Andrew,

Andrew Douglas Pitonyak schrieb:
> I wrote a simple function
>
> Function mydate As Date
>    mydate = CDate(100)
> End Function
>
> I then called this function from a Calc document
>
> =myDate()
>
> Finally, I directly accessed the cells with the dates from a macro
> similar to the following code:
>
> Print ThisComponent.Sheets(0).getCellByPosition(0, 1).Value
>
> The cell displayed the value as I expected, but the returned value was
> zero.
>
> Turns out that dates are converted to strings when returned to Calc.
> Oops. The proper thing to do (if you want it to work as expected) is to
> return a numeric value.

I'm not sure about that. "date" is a special Basic data type, it is not 
type "double". The "Programming Guide" tells vaguely "StarOffice
Basic uses an internal format that permits comparisons and mathematical 
operations on date and time values."

I do not find informations about mapping type "date" to UNO. The 
Developer's Guide has a mapping UNO -> Basic, but I miss the other way 
round. There seems to be some conversions already in Basic. If your 
function returns double not date, then you get the serial number of the 
date/time.

It is more a documentation issue, than a real bug.

Kind regards
Regina









--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted