LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
GerdW

case structure radix: allow leading zeros or even make them default...

Status: Declined
Will be tracked as CAR 434420

When using the radix option for case selector values (hex, binary) most often we want leading zeros to easily distinguish between "000000ff", "0000ff00" and "00ff0000". But right now the case structure doesn't even accept numbers with leading zeros!

 

So allow them and when doing so preset them to show as much zeros as are nibbles in the number (for hex) as suggested here...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
7 Comments
Darin.K
Trusted Enthusiast

I think that leading zeros resulting in an invalid case selector is a bug.

 

When it comes to default behavior I do not think anything other than a user defined display format is going to work.

 

A nibble is a hex digit, so right now LV does show every nibble.  I like my hex values to be byte aligned at the very least, sometimes word aligned.  Binary values are sometimes nibble aligned, other times byte aligned.  Ranges and lists can become unwieldy with too much padding.

 

My wishlist in some order

 

1,2,3. stop breaking when I enter a leading zero

4. allow me to specify a display format in the case selector display

5. leave my input alone (ie. leading zeros)

6. default leading zeros

 

Jeff-P
NI Employee (retired)

Reported as CAR 434420

Darren
Proven Zealot
Status changed to: Declined
Will be tracked as CAR 434420
altenbach
Knight of NI

Is Darin's point # 4 part of the CAR?

 

It would still be a great idea to be able to customize the display format here.

Darren
Proven Zealot

@altenbach wrote:

Is Darin's point # 4 part of the CAR?

 

It would still be a great idea to be able to customize the display format here.


 

The CAR only pertains to the request in the original idea post.

Darin.K
Trusted Enthusiast

I was waiting to see if that suggestion was going to get sucked into this idea, I'll suggest it separately.

ChrisStrykesAgain
Active Participant
CAR 434420 has been fixed in LabVIEW 2016. Please see the LabVIEW 2016 Bug Fix List for more information.

--------------------------------------