LabWindows/CVI Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

This X just closes out of the tab that is on top.

 

CVI window.PNG

 

Pretty much every other program with tabs has the X on the tab you’re closing out of. The current placement makes me hesitate every time, because it feels like you’re X-ing out of the entire code-viewing pane, not just the single file you want to close.

 

It’s also not consistent with the rest of the environment.

For example, in the pane on the bottom in the screenshot above, “Threads” and “Wa tch” look like two tabs, but clicking the X in that pane causes the entire pane to disappear rather than just closing the tab that is on top.

Allow you to select multiple lines and then go to Edit>>Block Comment/Uncomment to be able to comment or uncomment multiple sections of code at once.

Doing a CTRL+F and finding all instances of a word works, but is a lot of steps.  I tend to use Notepad++ a lot for my IDE and it has this really handy feature.  If you double-click a word, it will highlight that and all other instances of that word inside that one open file.  This is like a "quick find" that saves a lot of time.  See attached image to get the idea.  The darkest highlight is the one instance that was double-clicked.

The exit() function will make the application always return 0, no matter what value is passed to the function.  Per the documentation:

Note Due to the way that this function is implemented, the exit status value entered into this parameter is ignored.

 

Thanks.

 

It has been suggested much earlier here, but obviously passed out of mind:

 

When using 'Go to Definition' (CTrl+I) while in release configuration, CVI tells that no source code information was found for the identifier '...', because 'Browse information is not available in the Release configuration'... (still true for CVI2010)

 

This can and should be improved!

 

And it might be a good opportunity to also add the reverse process, 'Goto Declaration', suggested here

Hello,

 

I am glad that the event EVENT_MOUSE_WHEEL_SCROLL was added some time earlier to CVI. In principle, now it is possible to operate numeric controls, ring controls, etc. not only via keyboard and mouse, but also via the mouse wheel. This allows very smooth operations, great!

 

However, the integration level is inconsistent: While pressing the ARROW_UP key on a selected control will increase the value displayed in the control automatically, i.e. without the need of the programmer to react to a specific event, achieving the same result with the mouse wheel requires adding code to each callback. This is possible, but inconvenient as it adds a lot of overhead.

 

Right now, in every callback of a numeric or ring control that shall support the mouse wheel I have the following lines:

 

    switch ( event )
    {
        case EVENT_MOUSE_WHEEL_SCROLL:
            if ( eventData1 == MOUSE_WHEEL_SCROLL_UP )
            {
                FakeKeystroke ( VAL_UP_ARROW_VKEY );
            }
            else if ( eventData1 == MOUSE_WHEEL_SCROLL_DOWN )
            {
                FakeKeystroke ( VAL_DOWN_ARROW_VKEY );
            }

            break;
        case EVENT_VAL_CHANGED:
    ...

 

Hence I suggest

  • either to treat a mouse wheel on a selected control like an ARROW_UP or ARROW_DOWN keypress (personally preferred)
  • or to add one more attribute allowing to treat a mouse wheel on a selected control like an ARROW_UP or ARROW_DOWN keypress. In the UI editor, then there should be a checkmark (allow mouse wheel support), similar to the check marks initially dimmed etc. This attribute could be useful if there are concerns of backward compatibility - may be some users don't want to support the mouse wheel...

 

Thanks!

Ok, I guess everything is in the title

Open a source code where you fill an array

Put a breakpoint

Click on the name of the array

SHIFT F7

I would like to see the display in the bottom part of the IDE, not in a window

 

Regards, 40tude 

While developing code, having correct indentations is very helping in making sure you have all the right brackets and to see where your structures are nested easily.  Sometimes, whether by copying and pasting or just rapidly getting out a section of code, a whole segment might have incorrect indentation, which is tedious to correct.

 

This is where an auto indent tool could be a big time saver.  From somewhere like the Edit menu, where similar functionality is located in other development environments, you could select Format Selection to do a highlighted section or Format File to do the whole file.  Then, CVI can format the tabs for you:

 

autoindent.png

 

Although this is a simple example, auto indent becomes even more useful when you have multiple nested structures and decide, for instance, to add or remove another nested loop.

Personally I don't like the "unsorted" look of the libs as it is now. I always create a libs branch and put them there. This way the branch can be collapsed and saves space I don't have to scroll when having multiple projects in one workspace. Libs are files I don't edit that often so I don't have to see them all the time.

For every other file type CVI "knows" at the Add Files to Project sub menu, there is automatically a branch created - but not for libs.

It has been discussed here.

I suggest to add a note to the documentation, for example

 

WARNING!

_TARGET_PRODUCT_VERSION_ and _TARGET_FILE_VERSION_ values are updated only when the file that contains them is recompiled.

So be sure to include them only in files that are recompiled at every build.

 

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

table-editor.png

 

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.

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!

 

 

It would be nice to have canvas objects (line, oval, rectangle, etc) optionally anti-aliased when added.

I want the batchbuilt window sizeable.

 

My cws consits of 51 projects, and the configurations-list is no longer useable. I just can see the project names, but not able to see the "release/debug/..." additional informations of the projects to be built. The list looks like

" c:/../../Task_AutomaticMeasurement.prj - D"

" c:/../../Task_FullAutomaticMeasurement ..."

Hello,

 

Lets' assume a small structure or small array that one would like to have a look at during debugging. Selecting 'View Variable Value' (or Shift+F7) in the IDE puts the cursor on the corresponding line in the variable editor. If there are several variables, the variable of interest typically is in the last line of the variable editor. Now if one is interested in any element of the structure, it is always necessary to scroll down, which is quite inconvenient.

 

Hence I suggest to place the selected variable at the top of the variable view, allowing to see its first elements without scrolling.

 

Thanks

We're currently in the era of the large widescreen monitor.  Can we have the title bar in the IDE show the full path name of opened instead of abbreviating it with '...' if the window is large enough to show the full path name?  Thanks.

It would be convienent at times if the ListFindItem() function could seach a ListType by descending order (or in other words, starting at the end of the list and working towards the beginning).  This would be convienent when there are potentially multiple items in the list that match the search function, and I want to find the last instance.  This could work similar to the existing "Order" parameter that exists in ListApplyToEachEx().  Thanks.

Hello,

 

in the IDE of CVI it is possible to have both a toolbar and a status bar. Now if a file has been changed and could be saved, the disk icon is undimmed in both the status bar and the tool bar. For the tool bar, a single click is sufficient to save, while the status bar requires a double click.

 

While this double click behavior is true for all status bar actions (lock, unlock...), personally I would find it less irritating if the staus bar also would react on single clicks instead of double clicks.

 

Thanks for consideration,

 

Wolfgang 

Hi all !

 

I have some idea , it's a small thing but it can really help ,

 

When working with multiple C / H files you can switch between the open files easily in the files bar above the code area.

 

But when I'm closing the CVI and re opening it the files position in the changes , if i not mistaken i think the it's re ordering it by the previous stack status.

 

It would be nice to have the option to set a file order that will remain even after shut down.

 

Thank you.

Hello,

 

I have 2 suggestions for graph improvements.

 

1/ I suggested the first one a long time ago but it has never been implemeted so I try again trough this idea exchange board.

I would like to have the possibility to change the grid lines style to dash or dot. Today only solid is available.

I have written a routine to do it for printing graphs but as you can see it in the attachment it is not always working properly.

 

2/ It would be nice to have the possibility to set a percentage of transparency for the plots. In the example attached you can see if the green plot would have been behind the blue some parts would not have been visible. By setting the percentage of transparency of the blue one the green if behind the blue would become partly visible.

 

These 2 features are already available in the 3D graph so it would be nice to have them also on 2D plots.

 

Regards

Bertrand