I would like to see a few improvements to the BM:
I see that the actual work is done in the "Get VI Bookmarks" Invoke Node, thus it may not be trivial to add such features.
one related Idea deals with providing custom tag identifiers: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/book
It's not secret that .NET or ActiveX object on front panel appears to be child window of NI container clipping window, which itself is a child of front panel window. When there's only one object in the container on FP, it is easy to get its window handle (HWND) by calling GetTopWindow or simply by iterating through all child windows of FP. This handle has to-one correspondence with automation refnum on block diagram. But when there are several .NET/ActiveX objects on the panel, it's impossible to identify their handles with refnums on BD.
The way of handle obtainment could be implemented by any of the following methods:
(or let it be private property, being activated with special *.ini key)
MgErr AutoRefNumToHWND(refNum, hwndp); - this variant is analogue of LabVIEW Manager function FRefNumToFD, where refNum is automation refnum of .NET/ActiveX object (type LVRefNum) and hwndp is pointer to child window handle (type HWND *).
Probably many people may consider this idea unimportant, but when it comes to drawing different shapes, displaying text, copying window content etc., my suggestion may be very relevant.
Sometimes we create code, which is not reused elsewhere, but may be visually large or unpleasant (bad readability etc). Creating a file/subVI is not always the most elegant approach to solve this, but seems to be the only option.
It would be nice, to have the option to "Collapse" and "Expand" code parts (like some editors for textual programming have).
The example below may not candidate as visually large or unpleasant, but here goes...
We have some code.
And wants to collapse part of the code.
We mark/select the code part and right-click. From the menu, we select "Collapse".
The code we selected, collapses into some icon, without generating any files. It is purely visual.
If we want to edit or see the collapsed code, we double-click the icon, to open a new window containing the code.
If we want to return to the originally code view, we right-click the icon and select "Expand".
We now see our code in its originally form...
I think this option would be nice to have.
I like to suggest adding a possability to show the text definition of signal values inside the XNET database editor, (e.g 2 => 'moving'). Right now I need to open another tool to check the meaning of a value that is already describt inside the opened dbc.
in my opinion the XNET database editor is nice to handle database carrying some 10th of signals, but not some 100th to 1000 if a specific property is used.
- Implement a list view of all signals with its details, so that signals could be sorted by their properties, e.g. static or event type.
- Highlight FlexRay coldstart frames and nodes icons in tree view
I suggest to handle CRC calculation of frames by XNET HW (similar to other thread in this foram that suggest handling message counter on CAN).
In every project there are frames that needs a CRC over whole frame content, e.g. for CAN:
<Data1> <Data2> <Data3> <Data4> <Data5> <Data6> <MessageCo
Currently, all is handled by CPU which results in dependence to CPU and OS. Actually, complete frame raw data must be build in PC to calculate CRC (even if symbolic signal names are used).
With multipe CAN busses in parallel use and different repetition rates of CAN frames, timing may become critically.
It would be great if it would be possible to configure CRC-8 calculation for frames. Since the calculation has some parameters that are different from customer to customer, a perfect solution would be a formula node, that could be shifted to XNET board and liked to multiple frames with parameters:
- frame name
- CRC protection start byte
- CRC protection stop byte
- CRC byte position or signal name
I missed the posibility to set the automatic wrapping of text in the table and listbox controls. Similar to string control, the text should wrapped at the end of a cell and the row height (if property 'Automatic Row Height' is activated) expand if needed.
Please can you add the ability to have subscript or superscript test in label strings? For example, for plot axis labels. Matlab can do this no problem (preceed any subscript character with _ or any superscript character with ^). It should't be that hard to implement.
Writing good code typically involves spending a lot of time coding up error handling cases.
Dropping error cases around enumerated or string controlled cases is a common structure task.
This takes up quite a bit of diagram space and coding time when integrated over the entire job.
If an enumerated or string controlled case structure could have an optional terminal dedicated for the error data type only, this structure could be more efficient to code.
A typical implementation looks like this:
My proposed structure would look like this:
Right now - Requried Terminal is identified by either 1. Bold text in Help window 2.Broken arrow.
Will it be posible to highlight / mark the required terminal, so to identify at first look ? Something like mentioned below.
Sorry i couldnt draw properly. but some thing like this to highlight both in FP and BD.
My suggestion would be to include a way to see what the default values are for inputs to a sub VI easily. This could either be implemented in the way shown below through the hover over tool tip, or by the context help window. Either way, it would solve the problem of seeing what they are and whether one needs to place a constant there or not. Currently it takes a few clicks and wasted time adding a constant to the diagram and deleting it if is a default value which is sufficient.
It would be really nice to have a feature to Replace an Enum with a Tab and the Tab control contains the items which was configured in the Enum control. This would work the either way by replacing a Tab with an Enum containing the Items configured as Tabs. This makes sense because both are of the same data type.
I like quick drop shortcuts, and I would use them even more often if they could sync between computers that I work on. I'd like to see an option to specify the location of my quick drop shortcut options. Then I could store them in a folder that would stay in sync across multiple machines, ie my dropbox folder.
Hi LabVIEW users.
One of our customer would like to change Increment and Decrement Buttons' color programatically.
Although it can be changed using custom controls, it is more easy to change UI if the function is implemented.
How do you thinks?
LabVIEW currently has functions Format Date/Time String and Scan Value to convert between time stamps and strings. Unfortunately, these functions do not handle arrays of time stamps and strings. While this conversion can be handled using a For Loop, a specific function would be cleaner and probably faster. This functionality is currently available for other numerics and should be extended to time stamps.
I suggest modifying the Format Date/Time String function to handle arrays of time stamps, integers and floating point numbers as well as single values. An additional function Date/Time Sring to Time Stamp should be created to convert strings and array of strings to time stamps.