Setting maximum visible array rows from front panel using property nodes.

[GerdW]

Hi EmHill,

I still don't know why you want to change the number of visible rows all the time. All you get is a very bad UX!

If you insist on this "feature" I don't know why you need to access the very same property 3 times:

(German LabVIEW: AnzZeilen=NumRows, VertBildlauf= VerticalScrollbar)

Edit: Maybe you need to adapt the inclusion rules of InRangeAndCoerce to your needs, I just used the defaults…

[JÞB]

Gerd.  With integers, limit options are always included for IR&C.  The Glyphs are simply a source of potential confusion.:(

[GerdW]

Hi Jeff,

With integers, limit options are always included for IR&C.

Nope, I just tested this with LV2017!

Using I32 I receive "out of range" for upper limit=3, input=3 and lower limit=1 with default coercion settings:

Coercion settings ("include upper limit") are affecting the result in this small snippet!

The help for IR&C also doesn't mention the behaviour as described by you. It only mentions not to mix up unsigned and signed inputs…

[JÞB]

---

@GerdW wrote:

Hi Jeff,

With integers, limit options are always included for IR&C.

Nope, I just tested this with LV2017!

Using I32 I receive "out of range" for upper limit=3, input=3 and lower limit=1 with default coercion settings:

Coercion settings ("include upper limit") are affecting the result in this small snippet!

The help for IR&C also doesn't mention the behaviour as described by you. It only mentions not to mix up unsigned and signed inputs…

---

My apologies, I was mobile at the time and could have been clearer. The Include U/L Limit options Do affect the In Range? output. but not the coerced(x) output.