You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Enums with specific values are not generated in the enum typedef #524
@Arrowin-87 Are you transferring data from LV -> LV or some other environment? LV enums are required to be non sparse starting from 0. So the LV enum cannot contain values 0, 12, 13, 14, 15, 16 directly which is why you see 0, 1, 2, 3, 4, 5. However, on the backend there should be a translation between the LV enum values to the desired protobuf enum values before transmitting data across the wire. So if you were receiving the data in another language/environment, you should actually see 0, 12, 13, 14, 15, 16. Are you seeing something different or were you just confused by the LV enum restrictions?
Activity
jasonmreding commentedon Aug 24, 2026
@Arrowin-87 Are you transferring data from LV -> LV or some other environment? LV enums are required to be non sparse starting from 0. So the LV enum cannot contain values 0, 12, 13, 14, 15, 16 directly which is why you see 0, 1, 2, 3, 4, 5. However, on the backend there should be a translation between the LV enum values to the desired protobuf enum values before transmitting data across the wire. So if you were receiving the data in another language/environment, you should actually see 0, 12, 13, 14, 15, 16. Are you seeing something different or were you just confused by the LV enum restrictions?
Arrowin-87 commentedon Aug 24, 2026
Yes, I just noticed this can be closed since LabVIEW doesn't support different enum values..