LabWindows/CVI Idea Exchange

Summary:

Implement Swap Lines shortcut key (Alt+Up/Down).

Description:

Often, I need to swap two lines of code in my source file or maybe just move one or several lines up or down inside my code.

In order to do this, you normally have to do a cut and paste in order to move the lines.

Having a Swap Lines feature in the CVI source editor could significantly speed up this process, especially when you have to handle big chunks of code.

The Swap Lines mechanism could be triggered by the Alt+Up/Down.

This feature should also support multiple lines selections.

View All (3)

Using SetTableCellRangeVals to update several thousands table cells is very effective.(better than using ATTR_CTRL_VAL)

I miss similar function for set atribute values in the same way. In example:i need to set text to be bold or set background color for each table cell separately.

Ithik that usability of SetTableCellRangeVals will be better if SetTableCellRangeAttributes will be avivaible because there will be the same program approach/logic for values and attributes,instead of mixing multiple cell vallue update and one by one cell attribute update.

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!

View All (2)

Hi,

In an application I allow users to select

one file (using FileSelectPopup)
one or more files (using MultiFileSelectPopup) or
all files in a given directory using DirSelectPopup.

Unfortunately it is not possible to select two or three directories. Of course this can be emulated using MultiFileSelectPopup and marking all the files in all directories - but without the comfort of simply clicking a few folder names.

I thus would like to see a companion function MultiDirSelectPopup allowing the selection of several directories, in close analogy to MultiFileSelectPopup.

Thanks!

View All (1)

Hello,

once in a while, typically when creating a new UI, I find myself playing with different control styles, e.g. ring or menu ring, or different types of decoration (classic vs. lab style...).

Unfortunately, it is not possible to easily replace one type of control with one of its relatives: I imagine an additional command in the right-click popup menu: below 'Edit Control' I'd like to have a 'Replace Control' command which permits replacing e.g. a 'Recessed Narrow Frame' with a 'Recessed Box', keeping location, size and z-plane order (in general, as many attributes as possible)

Thanks for consideration.

View All (2)

Debugging code involving arrays is complicated by the facts that

In order to view a value from an array one has to press first Shift F7 and then F4: one key press would be simpler Right now only graphical array view has its one click shortcut...
Every time I restart the program I have to reposition the array display window to a place where it does not overlap with source code window, variable window,... It would be much more convenient if the window position of Array Display could also be saved such that in the next run and pressing Shift F7, F4 the window would be usable immediately, without the need to reposition it

Thanks!

View All (2)

View All (1)

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

View All (3)

Now I have done this function to do it, you surely can do it better with extended error detection.

void CmtWriteTSQDataInFirstPosition(CmtTSQHandle Queue_Handle, const void *Buffer, size_t Number_of_Items, int Timeout_ms, int *Number_of_Items_Flushed)
{
	CmtTSQHandle Queue_Handle_Temp = {0};
	const void *BufferTemp = {0};

	size_t ItemsInQueue = {0};
	size_t ItemsSize = {0};
	
	CmtGetTSQAttribute (Queue_Handle, ATTR_TSQ_ITEMS_IN_QUEUE, &ItemsInQueue);
	CmtGetTSQAttribute (Queue_Handle, ATTR_TSQ_ITEM_SIZE, &ItemsSize);

	CmtNewTSQ(ItemsInQueue + Number_of_Items, ItemsSize, 0, &Queue_Handle_Temp);
	CmtWriteTSQData (Queue_Handle_Temp, Buffer, Number_of_Items, Timeout_ms, NULL);
	
	BufferTemp = calloc(ItemsInQueue, ItemsSize); 
	while(ItemsInQueue > 0)
	{
		int CmtStatusOrItemRead = {0};
		CmtStatusOrItemRead = CmtReadTSQData (Queue_Handle, BufferTemp, ItemsInQueue, 0, 0);
		CmtWriteTSQData (Queue_Handle_Temp, BufferTemp, CmtStatusOrItemRead, Timeout_ms, NULL);
		ItemsInQueue -= CmtStatusOrItemRead;
	}
	free(BufferTemp);
	BufferTemp = 0;

	CmtGetTSQAttribute (Queue_Handle_Temp, ATTR_TSQ_ITEMS_IN_QUEUE, &ItemsInQueue);
	CmtGetTSQAttribute (Queue_Handle_Temp, ATTR_TSQ_ITEM_SIZE, &ItemsSize);
	
	BufferTemp = calloc(ItemsInQueue, ItemsSize); 
	while(ItemsInQueue > 0)
	{
		int CmtStatusOrItemRead = {0};
		CmtStatusOrItemRead = CmtReadTSQData (Queue_Handle_Temp, BufferTemp, ItemsInQueue, 0, 0);
		CmtWriteTSQData (Queue_Handle, BufferTemp, CmtStatusOrItemRead, Timeout_ms, Number_of_Items_Flushed);
		ItemsInQueue -= CmtStatusOrItemRead;
	}
	free(BufferTemp);
	BufferTemp = 0;

	return;
}

View All (2)

Moving from CVI 2017 to 2019, I really miss the feature where, in 2017, if the editor cursor was placed within the confines of any variable name, uses of that variable would be highlighted in all the locations it is being used on the display. With 2019 that same feature exists, but you now have to select the entire name of the variable as opposed to just having the single cursor within the confines of the variable name. It really slows things down for me.

I still use 2017 a lot of times for that reason, along with the lack of a line delineating the editor proper from the breakpoint diamond vertical area. I can't count how many times I've clicked and defined a breakpoint when all I wanted to do was have the editor cursor to the full left of the display. Argh E10!

View All (1)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

LabWindows/CVI Idea Exchange

Swap Lines

Add SetTableCellRangeAttributes to improve performance in the same way like SetTableCellRangeVals

Integrated mouse wheel support

SHIFT F7 should display variable content in the IDE, not in an external window

stick Resource Tracking window status to current workspace

MultiDirSelectPopup

Move "Build Options" to the build menu

UI editor: allow replacing similar controls

Provide a version of or an extra parameter for GetUserEvent so that it doesn't wait during a tracking loop

Save window position of Array Display

spell checking of source code comments

Make status bar behave like tool bar (i.e. single click response)

Relative Indentation When Pasting Code

Create a function that insert an object in the first position of a queue

Bring back horizontal scroll wheel

Bring Back Automatic Variable Recognition!

Please Add DataPlugin Capability to LabWindows/CVI

Change All Font Sizes Using Mouse Wheel

Provide a 'Save All' button or a 'Do this for all files' checkbox

Provide a 'Save All Files' Button for the Toolbar