How to clamp the values of a channel / ImGui input to a certain range?

[bjoern]

From the chat:

@bjoern

Is there a “nicer” way to clamp the range of an ImGui Input?

ClampImguiInput.vl (15.8 KB)

@Elias

and the 2. attempt with the foreach works ?

@bjoern

Not really, only because I am setting the pad again.

@Elias

this way we only have one channel
ClampChannel.vl (10.6 KB)

@bjoern

Huh I am sure I tried something similar and it wasn’t working. will check again later. thanks!

@Elias

it was just pointed out to me that the channel will still push the unclamped value first - so maybe this is not a solution
so it either needs a 2. “clean” channel, or we add some sort of validation layer one could plug onto a channel…

@bjoern

I think for my usecase it’ll be fine. It’s just for setting texture size and mipmap count in the texconv gui.
I tried some things with two channels and merge/consume but couldn’t get it to work.

@Elias

well you’re not alone ;) also not getting anywhere - didn’t think this would be such a tough nut

@nissidis

I know it is similar to your first approach and still quite ugly but this is what I occasionally do

@bjoern

Does this have the same “problem” as @Elias 's solution, the value “getting through” before being clamped?

@nissidis

if it is being updated form another source rather than the slider itself yes, this is wont work
if you want to clamp the values coming through the slider then pI guess it does

@gregsn

a) we could make it more generl purpose by calling a delegate in both directions. You’d get a EnsureValidValue region where you can place one clamp that gets called in both moments b) not super happy since the WYSIWYG doesn’t work. You shoudln’t be able to see values in the UI that are invalid

c) your original request probably only wants to ensure that the values coming from above get clamped(?) for that the upper node would be enough. in the implementation probably also only clamping from a to b would be enough

d) ForEach (Channel) breaks bi-directional flow output bcps of the Forach region only get pushed by the region when ingoing channels push. The other way around nothing happens.

e) validation of channels sounds nice. It should allow you to either ignore or clamp values and would always trigger no matter who tries to write. Should solve the wysiwyg issue

ClampImguiInput_BothWays.vl (21.0 KB)

@bjoern

My original goal was to not allow users to enter values outside a given range. For the current usecase it doesn’t matter if the value is outside for a frame or so, since it will only be used after “the value entry is finished”'. But I can imagine there are usecases where the value is used “in real time” and must actually never be outside the defined range.

Currently afk will check the patch asasp. Thanks!

@bjoern

b) not super happy since the WYSIWYG doesn’t work. You shoudln’t be able to see values in the UI that are invalid

I originally assumed you meant seeing wrong values in the editor UI. Now looking at the patch I see it’s displaying the “wrong” values in ImGui. That of course beats the purpose somewhat.

[bjoern]

@gregsn I’d like to request feature (e

:)

[gregsn]

the latest preview comes with just that. check the help browser for “valid”.

[tonfilm]

related: NuGet Gallery | Packages matching validation