Digital data table control - user friendly input limits

[Pappion]

TABLE Control: Is NOT user friendly.
No limits on column bits. Bits scroll off screen.
User needs right click instructions to: delete columns, empty table etc...

My chip designers don't need a LabVIEW trial by fire.

They just need a quick and intutive control that's hard to mess up.

It be nice if I could just limit entries to U8 rows etc...

As it is, an interactive scrubing loop is needed (read-scrub-writeover).

[mikeporter]

I'm confused, is this just venting or are you looking for solutions to some/all of these problems?

Mike...

[crossrulz]

This seems like something that should belong in the LabVIEW Idea Exchange.  That is where we put ideas for NI to implement.  And we vote with kudos to show community support.  It does help NI find a direction.

[Pappion]

It is a request for help and a gripe.

I did not see a property node that would help here, but I don't know them all.

Likewise, there are 3rd party controls available for free that I don't know about.

The numeric control set to binary is too dificult to read as it grows larger.

It could use signal numbers or spacing between groups of 4.

Maybe it can be done and I have missed something here too.

[mikeporter]

Given that you are just entering 1s and 0s anyway, why not make the input a 1D array of clusters with 8 booleans in the cluster? So you would have something like this:

 

or the same thing but with enumnerations:

Personally, I like the booleans --- easier to read.

Mike...

[johnsold]

Or an array of U8 numerics formatted for boolean display with minimum widht = 8 and padded on left with zeros:

Lynn

[Pappion]

Nice inputs, but what about: "It could use signal numbers or spacing between groups of 4."

What happens if I have to scale up to 32 bits wide and place it under a Mask word?

Right now I'm dealing with commands that can span 1 to 4 bytes (1-32 bits).

It's handy to make uneeded rows disappear. The tables do that, but what about your example controls?

BTW:Years ago I dealt with one enginner who never got a handle on what the array index does.

It's best if thats hidden and rows and columns labled (strict type def or locked).

You'd think that after all these years we would not have to reinvent the wheel.

[mikeporter]

OK, I see. You don't tell us exactly what you want, but you are more than willing to throw rocks at people who try to help because we don't offer solutions with spaces in the right place.

Well, excuse the heck out of me.