LabWindows/CVI Idea Exchange

About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Top Kudoed Authors
User Kudos Count
1
1
Showing results for 
Search instead for 
Did you mean: 

Display More Information About Struct Members

Summary:

Display more struct member information during source editing and during debug.

 

Description:

While editing source code, CVI only displays the struct members, but no information regarding the type of the member (or declaration information, line file and line).

Add a tooltip to the right of the pop-up displaying the struct members in the source editor to display this information. Similar to this picture:

struct.jpg

Also add support for displaying nested structs and even display the member values while debugging, in form of a tree, when execution is suspended (CVI currently only displays the memory address of that struct variable).

 

3 Comments
Trusted Enthusiast
Trusted Enthusiast
Status changed to: Under Consideration
 
Active Participant pblase
Active Participant

Even better, if CVI could take a hint from eclipse/MSStudio and have a smart language-knowledgable helper going on in the background to do this stuff so that we don't have to compile the code before being able to use this feature. I can't tell you how many times I've needed this ability, but haven't gotten to the point where I can compile yet. Rather frustrating.

Active Participant Johannes_T
Active Participant

Hello pblase,

 

The idea you are describing has already been discussed in another Idea Exchange post: here. Moreover, the status of that post has been set to 'In Beta' in the meantime.