To create a window with rounded corners or a tab control without a surrounding window, it would be great if i could set the transparency of the FP Window to 100% and all other elements to 0%!
This could lead to very nice looking UI's.
When your mouse rolls over a structure, a tip appears that tells you what that structure is. This is only useful the first few days that you are learning LabVIEW. From then on, and I've been a LabVIEW developer for 14 years, it is annoying hindrance, often obscuring something that you really want to see. This tip remains up for varying amounts of time depending on the complexity of the block diagram. There should be a way to selectively turn off this particular tip help; others are useful and should remain.
This is something that had subliminally bothered me for a long time. I would unconsciously move the mouse around and click other parts of the bock diagram to get the tip to leave. It was only several years ago that I became aware of this behavior and realized that it doesn't have to be there.
Whenever I have to do Serial programming or general instrument communications, I'm always googling an ASCII table to see the U8 values to STX, LF and so on.
While one might argue that simply printing a table or memorising the values should suffice, I'd love to see an ASCII display option for U8 so that I can immediately see how my serial ports are being set up for termination character and so on.
It would be cool for single-character strings also but I'm unsure as to how this could be implemented properly....
That's all folks
It would be nice to have an option for Tab Controls to "View Tabs as Buttons" which would be editable similar to regular LabVIEW buttons... resize, change color, multiple text, etc. This would help simplify the extra code needed currently to do the same functionality.
Everytime I build an executable I have to provide a custom INI file just to disable the localized decimal point. Please add a checkbox for this important setting to the application builder, e.g. on the "Advanced" page.
Whilst developing code I often need multiple copies of a subvi on my block digram. I create my duplications by click-dragging with CTRL pressed, which creates a copy. To make sure the copy is aligned horizontally with the original you can press the Shift key as well to enforce motion in one direction only (horizontal / vertical). However, this only works if you think to press the Shift key before you start the drag operation. Pressing it afterwards has no effect.
Furthermore, once a motion has begun, the chosen direction is the only allowable direction the object can be moved in. In other programs it's quite typical to restrict the motion to the direction of most linear travel from the origin, so moving back out to the right would restrict motion to horizontal, but then moving the mouse to somewhere above the origin would restrict the movement to vertical only.
I'd like to see these modifications introduced, purely to improve the development experience.
Note: This idea is the consequence of this original (flawed) idea
I'd like to see something like a conditional disable structure that would be sensitive to fields in an .ini file at runtime, not compile time.
My problem is that I have an application that can access many different third party cameras. For this application to work every VI that accesses a camera specific .dll function must have assess to that .dll or I get a broken VI. When I compile the VI I have access to these .dlls but when I build an application.exe and distribute it I only want to distribute the .dlls for one of the cameras. If I could distribute a .ini file with the application.exe that indicated which camera the drivers were installed for then the application would disable the code for all the other cameras and the VI would not break.
One thing that allows users to adapt an application to fit their work style is the ability to create toolbar containing functions they use most frequently. Labview currently doesn't expose that capability. (Though there is some functionality for it--JKI's Unit Test Framework installs a toolbar.)
Ideally we'd have floating/dockable toolbars, the ability to add/remove arbitrary commands to any toolbar, etc. In the short term I'd be satisfied with the ability to create buttons that execute a specific vi I've created and dropped in the project folder.
Please add the two primitives "Text to UTF-8" and "UTF-8 to Text" to the standard palette, probably in the string palette. It is a pity to hide such a great "tool".
The primitives are included in the VI attached to this message:
Using the LabVIEW 2009 Build Spec (as an example) allows you to add a Destination to a Library which is very handy, as it means you can namespace VIs at build-time.
I would like to take this a step forward and then be able to set that new Library as a Sub-Library of another Library that already exists in the Project.
I would then want to be able to set the scope of this Sub-Library as well (relative to its now, Parent).
This combined with my Locking State Idea would allow be create a Distribution that would hide and protect a Support VI Library
As the Sub-Library would be Private Scoped (from above) and the Parent Library would be set Locked (does not show Private Members).
I currently can implement this using Scripting but it would be nice to have it native.
I would like the option to edit the "Lock State" Properties of Project Items in the Build Spec of a Source Distribution.
I would like this feature to work on a Virtual Folder and Library and be inherited by all children.
I am chasing the exact same functionality as the Password Protection option.
I currently have to implement this as a post-build process.
Originally I thought this is what Daklu posted put that post got closed.
When I have large projects with lots of classes, Labview's edit time environment slows down to a painful crawl. Almost every meaningful action triggers a recompile that gives me a busy cursor for 3-10 seconds. My productivity falls off a cliff and I avoid making important changes in favor of the cheap hack. (The dev environment has high viscosity.)
I often wish there were a way to turn off the compiler while I make a set of changes. I'm not interested in the errors at every single intermediate state of the code while I'm making the changes. I *know* the code will be broken after I delete some nodes or wires. Let me turn the compiler off, make my changes, and then turn it back on for error checking.
I'm sure there are lots of different solutions to address this problem. My preference would be to make compiling faster so it is unnoticable. I doubt NI will ship me a new computer with the next release. My second choice would be to stop loading all of the class' member vis when any single vi is loaded. I vaguely remember a discussion about that some time ago and it wasn't practical to do that. That leaves me my third choice--more control over what automatically compiles when I make edits.
It could be something as simple as Ctrl-Shift clicking the run arrow to toggle auto-compiling at the vi level. Or it could be a right click option in the project window that controls auto-compiling for an entire library or virtual folder. Either would be okay; both would be nice.
(For that matter, it would probably be a lot cheaper if NI just shipped me a new computer...)
I started using LabVIEW when it was at version 6 and have used all the interim versions. I have always found the implementation of the Alt-Tab keystroke to be irritatingly inconsistent with other Windows applications.
If we have multiple LabVIEW wnidows open, for example, Alt-Tabbing to one of them means I have Alt-Tab through ALL of them to get to the first non-LabVIEW window. This is a real menace. If we have, for example, 8 LabVIEW windows open and the Calculator, we just want to Alt-Tab between LabVIEW and Calculator: we have to tab 8 times to get to the calculator but once will get us back to LabVIEW.
This makes little sense, since Ctrl-Tab has historically been for tabbing between multiple instances of the same application. Alt-Tab should be reserved for tabbing between applications.
By contrast, if we have multiple Microsoft Word documents open, they are mixed in with the other applications on the Alt-Tab popup, so if there's one which hasn't been topmost for a long time, it gets shoved to its rightful place at the end of the list.
Looks like this has been a hot topic for a while. Still with no concusion. Does this exclude it from the product ideas forum?
Why not make Alt-Tab behave the same way as all other Windows applications, since we'll always have the Ctrl-Tab to toggle between those self-important LabVIEW windows?
Most modern applications have a status bar at the bottom of the window for quickly finding relevant information. I'd like to see an edit time status bar on vi windows showing (and possibly setting) relevant information about the vi's properties. I'm most interested in the properties in the Execution category as there isn't a good way to check that information without opening the properties dialog box.
Case structures should have an easy to use Navigation like multiple grouped windows have in Windows 7. If a window is grouped in Windows 7 you will get a nice window that allows you to view what is in each window and navigate to the one that you want.
This would be very beneficial in LabVIEW for case structures.
It would look like the attached: