[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-comment] cell-content-is-between
Hi,I am not quite sure what you mean with value1 or value2 being null. "value1 and value2 are a numberValue, a string or an expression". The latter should evaluate to something . While there is clearly a problem if the effective values of value1 and value2 are of different type, I am not sure how null gets into the mix.
Andreas On 15-02-24 10:01 AM, Camille Moulin wrote:
Hi, I came across a compatibility problem between two applications regarding the validation of data in cells ; so I checked ODF's specification to have a clear idea of the correct behaviour and it seems that the definition of cell-content-is-between might be incomplete. It is currently quite straightforward [1]:cell-content-is-between(value1, value2): true if the cell's value is> between value1 and value2. You'll notice that there is no indication that value2 should be greater than value1, and it doesn't consider the cases where one of the value is null (or both) : this can happen when using variable, and this is the root of my problem. Both applications label the first value as "Minimum" and the second as "Maximum", but they show quite different behaviours For application A: if value1<value2 : it works as expected if value1>value2 : no value gets accepted if value1 is null : any numerical value gets accepted if value2 is null : any numerical value gets accepted if both value1 & 2 are null: any numerical value gets accepted For application B: if value1<value2 : it works as expected if value1>value2 : it works according to current ODF specification (i.e. values between value1 & 2 get accepted) if value1 is null : any value inferior to value2 gets accepted (which is consistent with the application labelling it as "maximum") if value2 is null : any value inferior to value1 gets accepted (which is not consistent with the application labelling it as "minimum", I would consider it a bug) if both value1 & 2 are null: no value gets accepted (which is not very consistent either IMHO) So, does the specification already cover those cases in a place that I would have overlooked? Or should they be added ? Best regards, Camille [1]http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1418316_253892949
-- Andreas J Guelzow, PhD FTICA Registrar Professor of Mathematical & Computing Sciences Concordia University College of Alberta
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]