Using decimal step sizes in range

[PGimenez]

It seems it is not possible to have decimal range step size. Here's a MWE with what I've tried:

using GenieFramework
@genietools

@app begin
  @in range= RangeData(UnitRange(0.0,1.0))
  @in qrange= StippleUI.Ranges.QRange(0.0,0.1,1.0)
  @onchange range begin
    @show range
  end
  @onchange qrange begin
    @show qrange
  end
end
ui() = range(0:0.1:1.0,:range)*range(0:0.1:1.0,:qrange)

@page("/", ui)

This is the HTML that's generated:

<q-range :min=0.0 v-model="range" :max=1.0 :step=0.1>
</q-range><q-range :min=0.0 v-model="qrange" :max=1.0 :step=0.1></q-range>

The RangeDatatype does not directly accept floats, so you have to pass a UnitRangeto it. However, the range does not work the browser and the console shows an error:

On the other hand the q-range bound to the QRange object does nothing, the handler is not triggered.

[essenciary]

@PGimenez Does Quasar support it? If it does, then we can do it too...

[essenciary]

Yes, quasar does support it - so we can add it.

[hhaensel]

Why do you want RangeData to contain steps?
Wouldn't it be sufficient to have

mutable struct RangeData{QRangeType}
    min::QRangeType
    max::QRangeType
end

That does work.

[hhaensel]

If you want to coerce the result to the step size you would need RangeData to contain upper bound, lower bound, step and lower range and upper range., e.g.

struct RangeData{QRangeType}
    min::QRangeType
    max::QRangeType
    step::QRangeType

    range_min::QRangeType
    range_max::QRangeType
end

Then you can parse the result and round to the nearest step with a Stipple.convertvalue() routine.

[hhaensel]

Would be nice to have this fixed before the next release...

[hhaensel]

I'd probably go with the first version.
Any opinions?

[hhaensel]

There was some confusion about what a UnitRange is (on my end).

It has a start and a stop field and doesn't contain any stepsize. That's correct and desired, because the step size is not transmitted, as stated already above.

The problem was actually with the parser. Strangely, UnitRange(1.2, 3.4) is displayed as 1.2:3.4 but this cannot be used as constructor for a UnitRange, instead it creates a StepRange. But exactly that pattern has been used by the parser. So the remedy of the problem is fixing parser.

The title is a bit confusing, because the problem is not the decimal step size but the decimal min/max values.

With the latest fixes the following app works correctly.

@app begin
  @in range = RangeData(0.0, 1.0)
  @onchange range begin
    @show range
  end
end

ui() = range(0:0.1:1.0, :range)

@page("/", ui)

Will be released soon.

BTW, there are new ways to define RangeData:

RangeData(min, max)       # equivalent to RangeData(UnitRange(min, max))
RangeData(min:step:max)   # coerce the max value to the least possible value with the given min and step size.
RangeData(min:max)        # equivalent to RangeData(min:1:max)