LabWindows/CVI Idea Exchange

I find this full stop at GetUserEvent because of a tracking loop (e.g. mouse pointer hovers at a menu bar) irritating.

Hello NI,

during program development and debugging typically there is more than just the source window visible, i.e. the lower part of the screen is used by the find or the build output window. Now, if I switch to a different tab/window to edit the UIR file, this build output window will still be there and take valuable space, although it is completely useless for editing the UI. If I close it, it will remain closed even if I switch back to the source code.

I would prefer that 'context sensitive' wndows such as 'find results' / 'build output' ... only show up if meaningful, while they are automatically hidden if not needed, i.e. when a UIR window is displayed, and automatically redisplayed if the source code window is back.

Thanks for possible consideration,

Wolfgang

Hi,

In the CVI IDE I am using tags to mark functions as 'ready'. It would be nice if different tags would be available allowing to simultaneously flag several characteristics, such as 'checked', 'verified', 'tested'... I would imagine differently colored flags, possibly similar to the colored flags available in Outlook.

In larger projects this might be a useful feature to add some quick 'documentation' of the development status, and using F2 (goto next tag) to go to the next function that is not finished yet, has not been tested, etc.

Thanks.

Hello,

If one is interested in having a popup menu that shows up only for row or column headers it would be convenient to have the analogon to the event EVENT_TABL​E_ROW_COL_​LABEL_CLIC​K (which actually is a EVENT_TABL​E_ROW_COL_​LABEL_LEFT_CLIC​K event...), i.e. I am suggesting an event that is fired when a right click is received on a table column (or row) label.

It should be added that right now this is already possible with 11 additional lines of code, see the example colview, so I do not consider this idea as urgent , but still...

Hello,

following the discussion here I suggest to (more clearly) indicate the number of allocated rows and columns in the UI table editor.

I imagine something like

where the left number indicates (as now) the currently selected row, and the right number (11 in my quick example) indicates the number of all table rows.

The same might also be added for the number of total columns.

Thanks.

I had a customer associated with SR# 7325346 ask how to change the maximum value for his Y axis in CVI.  I rightfully directed him to the SetAxisScalingMode function.  The customer told me that they were using an equation to determine the Max parameter for their Y axis [YMax=2*x + sqrt(x) + log(x)] or something to that effect.  He also said that the equation could change to something else, and he would like to change the equation on the fly within CVI. 

Basically, he's asking for functionality that would enable a text box to act similar to an Excel cell, which could evaluate simple equations such as add(val1,val2) or sqrt(val3).  We should build a tool that makes this possible.

Hello,

imho the nice tool tips feature provided by the Programmer's Toolbox leads a miserable existence, because it is extra effort integrating it into a GUI.

I would love to see the tool tips integrated into the IDE, that is, when editing a control in the GUI editor, I would like to be able to also set the tool tips text and if it is initially enabled, just like it is possible to enter a control label text. This would include moving the tool tips from the Toolbox to the regular user interface library.

Many Thanks!

Currently, there is no way to access the historical data on a stripchart.  The only way to manage this data is to maintain a separate buffer and update it whenever you add data to the strip chart, which is inefficient and tedious. Accessing data is possible for graph controls using the data attribute:

GetPlotAttribute (panel, PANEL_GRAPH, plotHandle, ATTR_PLOT_XDATA, &data);

 Something similar should be implemented for the strip chart, either as an attribute in the getTraceAttribute function, or as a standalone function (getTraceData, etc.)