Edit menu control from block diagram

On my front panel I have a menu control that lists the existing file folders for saving the test data. If the operator want to add a new folder I want the Block diagram to write a new folder and add the entry to the menu control list.

What I would suggest is that your menu have a selection called "New", then if the user selects this, the file dialog would pop up and allow the selection of a new folder. Using a property node, write the new path to the Strings[] property to update the list. At the end of the program, you could write the list to an ini file to save the new list. You would also want to read this ini file when the program starts and write the list to the Strings[] property.

Similar Messages

Delete controls from block diagram in LV2009?

Hi,
I'm missing that "delete/copy panel terminals from diagram" option of older LV versions (see attached pics)...
Where is it hiding or is gone for ever? I really miss that feature...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Solved!
Go to Solution.
Attachments:
BlockDiagramOptions_LV71.png ‏11 KB
BlockDiagramOptions_LV86.png ‏22 KB

GerdW wrote:
Hi Ben,
thanks for the link. Actually I set this key to "True"
And this change isn't mentioned in the "LabView 2009 Features and Changes" document that opens from the LV start screen
Message Edited by GerdW on 08-21-2009 04:26 PM
That is where I stumbeld across it.
About a third of the way dwon under the section labeled
Options Dialog Box Enhancements >>> 6th bullet down reads "Rarely used options no longer exist in the Options dialog box. Refer to the Knowledgebase for a list...."
Clicking on the "knowledgebase" link took me to the page I linked previously.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Help !!! Up down left right slides missing from block diagram !!!

H E L P !!!! Hi I am right in the middle of editing my labview program and all of a sudden on my block diagram the up down and left right slides have dissappeared from the screen ? How do I get them back ? I have tried closing the program and reopening it but when the saved program reopens the slides are still missing for pulling the programs scope left right up and down !!! Thanks John

Hi,
are you sure the slides (please fill me in what are those?) are missing?
May be you have dragged the mouse while holding down the CTRL-key that auto-expands your block diagram?
To verify use the find function and search for the name of an indicator/control that has gone missing
Another way might be using ctrl-shift-N, this will show a small overview of your VI.
Ton
BTW your VI should fit into one (1) or two (2) screen of 1024X768 and never expand it in both directions!!
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Property Node activated even though it's been removed from Block Diagram

Hi,
I messed around with the property node of one of my controls and when I was finished and removed the property node from the block diagram it still makes my control blink.
How do I make it stop??
Is the option of Enable state not possible to set in property node mode. I'd like to go from disabled and grayed to enabled.
Thanks.
Solved!
Go to Solution.

Hi
Your blinking property might still be set. Add the property again to set it to False.
To set the enabled/disabled/grayed state use the "Disabled" property.
Hope this helps.

Print Problem : Print description and tips from structures, nodes and loops from block diagram

Hello,
I've just completed the entire documentation of my VI and I did describe some Case structures and Formula Nodes. Now I want to print the VI with the VI printer and when I select ''Description'' in the custom printer manager, it doesn't select the description from most functions in the block diagram such as Formula Node, Case Structure,etc.
Is there a way to get these descriptions in the printed version VI ?
Thanks a lot !
Solved!
Go to Solution.

Hi Weepet,
After some investigation, it turns out that this behavior is expected behavior. Please see the following help topic
http://zone.ni.com/reference/en-XX/help/371361G-01/lvhowto/creating_vi_and_object_de/
Essentially, Context Help will only display the description for controls, indicators, and constants. At the same time, the descriptions will only print if that description is available in context help. LabVIEW primitives will always use the description from the documentation, and will not display your custom "Description and Tips". So, for primitives like case structures and formula nodes, we cannot get that information to print. The behavior that you're seeing is expected.
Perhaps you can just use comments to document these functions? You can double click on a blank area of the block diagram and provide comments.
Regards,
Che T.
Applications Engineer
National Instruments

Automatic resizing of controls on block diagram

Hi,
I have control as strict type def and many instances (on block diagram) of this control in several VIs. When I add new element in this control all instances resizes to maximum size and that corrupt layout on block diagram because all structures resizes with that instances. Is there a way to avoid that?
Thanks, andrej

Place it on the front panel of a subVI as an output. Then call that subVI whenever you want the typedef.
You can find more on using typedefs here.
Try to take over the world!

Adding Indicators & Controls from the diagram - why do they get placed off the current screen?

When I place a button, indicator, etc. from the diagram, it gets placed on the front panel nowhere near the existing stuff. What am I missing?
Richard

I don't know the exact algorithms used when LabVIEW places a control or indicator on the front panel, but I can tell you what I have observed so far:
It seems that the new controls and indicators are always placed below all other controls and indicators. There may be additional rules, but this seems to be the most common occurrence I have seen.
If you want more control over where your controls and indicators are placed, then you should created them manually from the palette before you begin your diagram. This is good practice, but not always possible.
I hope that helps. Good luck.

Hypertrend problem adding trace from block diagram

Hello,
does anybody know the propper way to add a trace/traces to Hypertrend. To be more exact, I have multiple traces in Citadel databes that I want to extract programmaticly do some manipulations and them show the trace on hypertrend. When I try to replicate the solution from Examples (Trend Viewing Options and simnilar) the result is following :
I tried everything but I can't get to write to the field "Trace Path" (shown on picture above) instead by writing to URL property it writes to "Name:" field.
EDIT: I use LabView ver 7.1

jliles wrote:
Have you had a chance to look at this example? Would it provide you with the functionality you are looking for?
Community Example
Hello jliles,
I've tried the mentioned example but with no joy. I've switched to LV 2010 but still cannot programmaticly add traces from library. Here is the current version that I'm trying to make work.
The main reason thaht I'm trying to use HyperTrend is the issue that is coming up when using XY Graph with Citadel database. Under some conditions the XY Graph sets the begining of time to year 1904 when reading a trace. The HyperTrend doesnt have that problem, but the problem is how to add traces programmatically the same way I do it with XY Graph.
Thank You for Your time.

LabVIEW exits while editing block diagram unexpectantly

Hi all, while editing block diagram in LabVIEW 2010, I have experience some strange behaviour from the software. I have two monitors, one has the front panel of main VI and the other - block digram of the specifed VI. When I switch from block diagram to front panel, and vice versa, every now and then the LabVIEW exits unexpectantly without the notice. Upon restarting the program again I get the undo.cpp error. I have attached the error log for my clarification on the type error that I am dealing with. Does anyone have any ideas why this is occuring? Thanks in advance for your help.
Viktar
Attachments:
lvlog2010-09-17-09-35-46.txt ‏2 KB

Thanks for all the responses.
I was using an existing VI as template to create a new program. There were nested loops in the original program and I needed the logic for the outter loops only for the new program. After deleting many objects in the 'yes' case in the inner loop, I was left with many loose wires in the 'no' case. And that's when my problem started, when I was trying to delete them. Yes, I tried rebooting my PC and that did not help. The problem seemed to get progressively worse, as crashing started to happen even when I was only selecting a wire. But somehow I was later able to select one wire, delete it, and did a save. Then I went to the next wire, and so on. My program is now cleaned up and I'm ready to go on. I will experiment more when the problem returns.
Thanks again.

Type defs changes not reflected in block-diagram constants?

I'm struggling with strict type-defs today.
If I create a strict type-def, say of a cluster with an enum in it, and save it. Then create a block-diagram constant from the strict type-def in a blank vi. Then make changes to the strict type-def (say, add another item to the enum), the block-diagram constant ghosts out , as it should. If I then select "Apply changes" from the strict type-def menu, the ghosted block-diagram constant becomes un-ghosted, as it should. BUT, it hasn't update!? If I look for the new item in the enum, it isn't there!? I'm sure it should be, right?
No changes that I'm making to my type-defs or strict type-defs are being reflected in my block-diagram constants (which are definitely still linked to the controls with "Auto-update from type-def" checked on). It does work for front panel controls and indicators though - just not block diagram constants.
I'm using LabVIEW 8.5.1, Win XP Pro. Any ideas anyone?
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Solved. I think.
I tried a range of type-defined controls, including an enum, a ring list, a cluster with an enum inside it, and a cluster with a ring list inside it.
Changes to the enum items were reflected in all vi controls and block diagram constants.
Changes to the ring list items were not reflected in the controls or block diagram constants.
This snapshot shows the the last item available in each ring and enum list. Clearly the rings were not updated when the custom controls were. (Yes, I applied changes and saved too).
Switching to strict type-defs only impacted the front panel controls, as Ben highlighted, because this is GUI related. You can see from this second snapshot where all type-defs are now strict type-defs that all enums and rings updated to reflect all three items, but the block diagram rings are still out of date
I expect somebody will tell me now that this is normal behaviour???
Message Edited by Thoric on 09-10-2008 02:31 PM
Thoric (CLA, CLED, CTD and LabVIEW Champion)
Attachments:
custom_control_test.jpg ‏53 KB
custom_control_test_stricttd.jpg ‏54 KB

Missing "edit" menu in FCE

Recently when using FCE 3.0 the "Edit" menu disappeared from the menu bar. I did a complete reinstall following Apple's Troubleshooting Basics for FCE, that is, I removed all traces of the application from all locations. The "Edit" menu is still not there. It should be there between "File" and "View" but, it is missing. When the application starts up, it is seen briefly while the opening splash screen is displayed but when the app. is fully open it is gone. I have tried the reinstall process three times with no luck. I can still use the various functions by using keyboard shortcuts but I am totally baffled by this.
Is there something simple that I am overlooking or is this an indication of a brewing system problem? All of my other applications are fine and I regularly run disk utility and MacJanitor.
Thanks in advance for any assistance.
Message was edited by: Ernie Baudler

Tom, thanks for the input so far. Explain exactly what you mean by "Depends on how I'm doing it".
Forgive me for pressing the issue but I want to know exactly what is going wrong during the install process to cause this issue. What preparation needs to be done before running the installer besides the usual permissions repair before and after the install is complete. How would you install from the CD?

How to lock block diagram alone from editing leaving front panel for editing?

i want to lock block diagram from editing but front panel can be edited for creating controls, moving controls editing properties...

executables will be delivered to customer and they can create new vi and edit frontpanel and link tag through databinding. but i dont want them to open block diagram...
Natasftw is right - you seem confused about the difference.
If the customer can "create a new VI and edit frontpanel" then they have to have LabVIEW Development System.
If you give them an EXE, and they don't have the DevSys, then they can use your VIs, but not edit them or look at the code.
If they have the DevSys, then they can edit your VI and look at the code, UNLESS you protect it.
If you save a VI with protection (VI PROPERTIES - PROTECTION ) then you can LOCK it (user has to explicitly unlock it with an extra step), or you can PASSWORD PROTECT it (user has to explicitly unlock it by giving a password). Either way requires the DevSys.
There is no situtation where one can edit the front panel without being able to edit the block diagram.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

The Block diagram that cannot be edited...

The customer wanted to launch the application ( done in LV7 ) with a shortcut from the desktop and when done with it wanted to close all including the LV environment.
So I made the following changes :
1. Made the application to "Run on Open "
2. Connected the while loop Stop button to the "EXIT" function.
3. Saved and started the application.
Presto!! All worked as expected. Except that I no longer was be able to Edit the block diagram !!
Good - I had a copy of the code before the change and survived the nightmare ....
So the moral : Be very clear of what you are doing before you use the EXIT function.
Just though will share the experience, before somebody makes the fatal mistake as above.
( I have now ordered out my copy of the Application Builder, so that I can have my editable code well away from the customer's PC.)
Raghunathan
Raghunathan
LV2012 to Automate Hydraulic Test rigs.

Here's another way to do it.
Create a directory in your LabVIEW x.x directory named 'wizard', and save the attached VI there. If LabVIEW is running, you'll need to restart it, but then in the 'File' menu, you'll have a new selection named "Supress Run on Open...". Select this and you'll get a browse dialog to select the VI to open. It opens it by reference so it will not run.
This is saved in LabVIEW 6.1, but works fine on 7.0 and 7.1.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Attachments:
Supress Run on Open.vi ‏18 KB

How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel?

How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel? On the Front Panel I am making a complex control that consists of a Slider and a Numerical Input box. Both Controls display the same information and either can be used for Input. When one changs, the other is made to display the same value.
But I only want the Slider to display the Label on the Front Panel, to avoid confusion. On the Block Diagram however, I want both controls to display their Labels so that I know what they are. How do I display the Label for a Control on the Block diagram, but not display its Label on the Front Panel?

No. The Label Visible property is separate for the front panel control label and the block diagram terminal label.
How did you start out with the block diagram's label not being visible? Whenever I drop a control or indicator, the label is always visible on both the FP and BD by default. Maybe there is a LabVIEW option that causes new controls/indicators not to have their labels visible by default, but I have yet to find it. I don't think an item should ever be dropped without the label visible, good LabVIEW coding practice demands that the labels for control terminals on the block diagram be visible so that you know what control or indicator a wire is going to.
That being said, I have seen a lot of VI's posted where the label for the terminal on the BD is not shown (against good programming practice.) I've gone to the BD and right clicked to show the label. Sometimes, the people have an empty label (which will turn off the visibility for both the FP and BD) and I'm forced to add some text of my own into the label so I can figure out what their code is doing. When I add some text to the label, at that time, I find both the BD and FP labels become visible.
Are you dealing with controls that have empty labels to start?
Good programming practices:
1. Always have a name for all of your controls, never use and empty label by deleting the text in the label.
2. Make the labels unique. For example, don't have two controls both called Stop. How do you know quickly know which terminal relates to which control?
3. Always show the labels on the block diagram, so you know the function of a control's terminal. If you want to hide the label on the FP, that's okay.
4. If you want a different label to appear on the FP than whatever you actually called the control, then use the caption. You can hide the label and show the caption. This is useful if you need to programmatically change what the "label" is on the front panel such if you are making an application that needs to change its user interface such as for a foreign language.

Disable (all) functions on the block diagram with right-click menu

Hello to everyone,
here is one more idea, which I'd like to propose.
As for me, it would be useful to have the following: when all components (functions, wires, subVIs, etc.) are selected on the block diagram (like, after ctrl+A), operator could do right-click, and in the menu would appear menu item "Disable everything". After it, all the code could be placed into Disable structure.
Of course, I can add Disable structure to block diagram manually, and cover whatever I want, but with right-click menu it would be much faster.
Also, it can be modified to disable only selected items - then each of them can be placed into separate Disable structure, and, for example, additionaly in the enabled case of Disable structure, corresponding wires will be connected. Sometimes it is needed for testing - just to disable couple functions, and test subVI. Or to disable subVI fully (it's faster, then disable place, where it is called. Especially, if subVI is used in many places).
It will not make debugging difficult, because anyway Disabled structures are used; such functionallity can just make life a little bit easier...

There is always the File->New... which opens up a new window. You can have your templates in that window by putting them somewhere (I don't remember where at the moment).
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Edit menu control from block diagram

Similar Messages

Maybe you are looking for