Front panel window:open ? property

can any one clearly explain about the use of front panel window property . i am not able to get with the examples given in ni . if possible explain with help of example please

It refers to the overall window, which includes the title bar, scroll bars, grow corner, etc. Have you looked at the available properties:
The LabVIEW Help provides information on each of these. If you have the Context Help Window open you will see a brief explanation of the property as you move the mouse over each one. You can then click on the Detailed Help link to bring up the Help.
So, for example, you can change the title in the title bar:
Attachments:
FrontPanelWindow.png ‏24 KB
title.png ‏7 KB

Similar Messages

Enabling / Disabling graphs and opening a new Front Panel Window

Hi,
I have a simple application of showing 12 analog signals on 12 different graphs placed vertically in aligned position. I have to develop a user interface so that if user wants to display signal no. 1, 4 and 6 out of total 12 signals, he should make selection using check boxes and click a re-draw button. It should result in opening a separate window with these three signals displayed as separate graphs aligned vertically and adjusted to fit window size. Similarly later user can change his selection of displaying signals (from same acquired data) say 1, 3, 5, 6, 8, 9, 11 & 12 and click Redraw button. It should result in opening a new Window showing all these signals as separate graphs which are aligned vertically and resized to fit the window. Now I have two major issues in this context.
1) I have been searching LabView help to locate a way to open a new window for this purpose but I failed to locate any way for it. As per my limited knowledge, it seems that we cannot have multiple "Front Panel" windows in Labview.
2) For the graph I could not locate a control to enable/disable a graph so that it appears or vanishes. Is there any way to achieve it?
I shall appreciate your valuable advice. I shifted from "Lab View Signal Express" to "Lab View" in order to achieve this user interface design but I am still not successful in finding a good solution for this application.
Regards
Mnuet

Hi Mnuet,
You can do what was said above. Here is a KB on dynamically loading VIs. It looks something like this.
Dynamically loaded VIs are loaded at the point in code while running, as opposed to being loaded when the parent VI is loaded into memory like normal subVIs. You can make a reference to them and then control the front panel appearance, their run status, etc with property nodes and invoke nodes.
Jeff | LabVIEW Software Engineer

Refresh graph properties (colors...) when front panel not opened

I have a problem with setting the plot properties of a multiple xy-graph.
I first pass the data (n plots, number variable) to the graph control, THEN I set the according properties like color, line style etc. by a property node beginning with "active plot" followed by the properties. So when I set them, the xy-graph is already initialized with n plots.
Afterwards, I take the graph picture and save it to a bitmap-file.
That works fine as long as the front panel is opened or the number of plots and their attributes stays constant. But if the panel is closed (which is the default of that VI) and the number of plots changes, I get only as many plots plotted correctly as there are shown in the plot legend
- regardless of if the legend is shown or not.
I don't like the idea of having a huge legend on the panel which still might be too small sometimes or having the legend scaled by it's height-property in pixels.
What I need is something like a .refresh-method that forces the graph to update even if the front panel is closed. Any idea how to do this?
Cheers & thanks, Daniel

The issue you are seeing is because LabVIEW doesn't update the controls/indicator of a front panel that is not open. This is done to save computer resources. The simple way around this is to use VI server to open the front panel for it to update and then close it again. You can use the VI property FP.position to move the window offscreen where it can't be seen and perform the open/close. This will get you the results you are after while still allowing the illusion of a closed front panel.

Window.opener property from child window to parent window

Hi
When communicating between the child (popup) window to the parent window works fine as long as we pass the static reference to the window.opener
Example :
Main Page
form name = staticform
input name = col1
Popup Page
javascript :
window.opener.staticform.col1.value = some value
How can I use a dynamic reference for the staticform.col1 in the window.opener property to post the value back to the parent window ?
thanks for the help
sarma

Actually, I think tolmank's would work... I've done basically the same thing before, but more like this (if it's generic, it's a good idea to have checks for the things being in existance). This is something I used in a generic color chooser I wrote in Javascript. Had multiple fields in one form using it for selecting different foreground/background colors.
<%
String form = request.getParameter("form");
String fgfield = request.getParameter("fgfield");
String bgfield = request.getParameter("bgfield");
%>
vfnSet = function() {
   if(typeof(window.opener) == 'undefined' || window.opener == null) {
      return;
   if(typeof(window.opener.document.forms['<%= form %>']) == 'undefined') {
      return;
   var oForm = window.opener.document.forms['<%= form %>'];
   if(typeof(oForm.<%= fgfield %>) == 'undefined') {
      return;
   if(typeof(oForm.<%= bgfield %>) == 'undefined') {
      return;
   oForm.<%= fgfield %>.value = document.forms['colorform'].foreground.value;
   oForm.<%= bgfield %>.value = document.forms['colorform'].background.value;
}

Readjusting front panel window.

Double clicking on terminals in the block diagram switches to their counterparts on the front panel. Frequently this leads to an unwanted shift of the front panel, in particular if objects (such as error clusters, ...) are placed outside the visible region of the front panel. Readjustment usually requires several scrollbar actions. I wonder if there exists a simple method to readjust the front panel coordinate system with respect to the top left corner of the front panel using a simple click action.
I am presently using a workaround which does the job if the misplacement is top-left (see attachment).
Reimar Spohr
Attachments:
Readjusting front panel window.png ‏11 KB

I am suggesting a modified version according to -lvABC to be dropped into a calling VI.
Reimar Spohr
Attachments:
Move Calling VI Front Panel to Origin.vi ‏25 KB
Move Calling VI Front Panel to Origin.png ‏43 KB

Hide front panel when opened

I have a VI running as a back ground task (VI_A) to the main VI (VI_B). VI_B starts VI_A and the idea is that VI_A will be minimised on startup. There is a button on VI_B to restore the window and a button on VI_A to hide the window and return to VI_B.
This is all working OK, I open VI_A front panel when called, VI_B minimises VI_A straight away etc, I am using the WINUTIL.LLB functions to perform this. The problem I have is VI_A front panel is visible upon start up for a couple of seconds (there is no real delay in my execution to minimise). I have tried setting VI_A to be at teh back within VI_A but still it appears at the front for a couple of seconds.
Does anyone have any suggestions as to why this is occuring.
Cheers,
Wayne

One thing that you could do is to change the Windows Appearance property to NOT open front panel when called. You can then have your main VI (VI_B) open the panel for VI_A as before, but it will not start with the panel open. If you are creating an executable, go to the VI Settings tab page and click on the line with VI_A and then Edit Settings. Turn OFF the Remove Panel property. This should work for you (I've done similar already anyway).
Rob

Cluster does not populate in sub-vi unless front panel is opened

I have a sub-vi that saves my data to a database and the cluster
containing the data will not populate unless I open the front panel
when it executes. What could possibly cause this?

It is the readings cluster that does not populate. That is the input cluster for the vi. When I run in the development environment the program saves correctly without opening "Save Readings.vi". However after the complete program is compiled the data will not save unless "Save Readings.vi" is opened when it executes. I have attached the missing vis
Attachments:
Log SQL.vi ‏27 KB
Connect SQL Server.vi ‏48 KB
Update Process Info.vi ‏81 KB

[BUG] XControl allows you to shrink front panel window smaller than LV normally allows

If you set up an XControl, the facade opens up a normal window.
Which looks like this shrunk to smallest size. If you then load up a VI in to memory that calls the XControl, you can shrink it further:
Finally, once you close the VI which calls the control in memory, it unlocks the facade, resulting in:

That's why we need this idea.
LabVIEW Champion . Do more with less code and in less time .

Is there anything like a front-panel OPEN or FP.STATE property for an RT (cRIO) VI?

I'm wondering if there is a way for an RT VI to detect when its front-panel is open, both when run interactively from within a project and also when accessed remotely as an embedded window within a browser?
Solved!
Go to Solution.

I know about the "Remote Panel:Connections to Clients" property and I'm already using that to tell whether a remote connection is active (as opposed to running the VI within the development environment). It cannot however tell if the front panel is open within the development environment.
As for the property-node returning an error, that does not appear to work here (perhaps I have selected the wrong property, I'm using the get-reference-to-front-panel property). I suspect that since the VI is setup to work with a remote front panel, the VI thinks that a front panel does exist even when a remote connection does not. I suspect this error check would work if the VI had not been setup for use with a remote connection because then the front panel would be stripped out as the VI was built or perhaps deployed to the RT system.

Open and Close Front Panel of SubVI

Hi all,
Running LabVIEW 2011 on Windows 7 x64. I am trying to get a subVI front panel to open from my main FP with the press of a button and then close with a button press in the subVI. Here is the piece from my main FP that calls the VI and opens the FP
Plots is defined in another loop and all of the loops are in a flat sequence. I did it this way because I want it to start with the first press and not stop my main loop from running. I have moved the item in the left loop around a lot so I'm not sure if I can run that in the same loop as the event or not. Either way opening the VI seems to work fine.
The problem shows up when trying to close the subVI for the SECOND time. The code is here:
As I said, the first time I open and close the VI everything works as I expect it should. I am then able to open it again but now the "blank button" doesn't function and I can't close the window or even open the block diagram to probe anything. I have been trying to figure this out for awhile, any insite would be greatly appreciated!
Thanks
Solved!
Go to Solution.

Its good that you found the bug.
This code may serve as a way for you to compare notes.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Open and close front panel

Hi,
I wish to have a VI that works as a main menu from which you start new
VI's depending on your choice. When the new VI start I want the main
menu to hide it's front panel temporarily until it the second VI
returns.
Anyone has a solution to this?
/Nimrod
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
When the new VI start I want the main menu to hide it's front panel temporarily
until it the second VI returns.
If you are using LabVIEW 5.1, you can use the VI server attributes to hide
the VI by moving it off of the desktop. I will send you a sample in private
mail.
The attribute (property) you need to use is Front Panel Window -> Window
Bounds.
Set it to something that is larger than your window size, like 2000, 2000,
2200, 2200.
I hope that this helps,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]

LV 8.5 opens all sub-VI front panels

Hello,
Recently I again saw a strange occurrance that has happened to me about 10-12 times over the past year. Here specifically I am using LV 8.5 with the cRIO and FPGA module. When I was running a new RT VI from the developer environment, (deploying to the cRIO) the result looked something like this:
All the sub-VI front panels are opened, and shown in their reserved or running state.
None of these VIs are set to show front panel when called or opened, but all are sub-VIs of the top level VI within the project. It seems to have replicated a "Find all VIs in memory, within the project" and then "Show front panel" Invoke. The troubling thing is that this is not really repeatable, when I have closed all the VIs and run the VI again, it is fine. I have seen the same behavior in LV 8.2, 8.21 as well as when deploying to cFP-2120 or when on a Host computer.
Has anyone else seen this or are there any ideas of what is going on?
Thanks,
Mello
Message Edited by Mellobuck on 12-11-2007 01:17 PM
Message Edited by Mellobuck on 12-11-2007 01:17 PM
Data Science Automation
CTA, CLA, CPI
SHAZAM!
Attachments:
Multiple Windows.jpg ‏117 KB

Well now that I have seen to image, I recall having seen this myself.
Like you, it was when I was deploying to an RT target and I was not able to recreate this behaviour.
It was either an 8.0 or a 8.2 app.
So all I can do is confirm that you are not alone, but can not offer a solution.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Can not open front panel sub VI when running an application VI.

When I create an application of my program a problem occurs. When I select options (press a button or so) from the main front panel that should result in a popup menu (sub VI cal) LabVIEW indicates that something is happening but the front panel does not open. The mouse indicator changes to the time glass so LabVIEW is doing something but the window of the sub VI does not open.
The problem has the same characteristics on several places. There are some sub VI front panels that opens but I ca not find the reason for why these open and not other.

Hi
there are three ways trhough which you can force a subVI to show its front panel
1. open the perticular SUB VI
click File->VI properties select window appearence catagory.
click customize button and select "Show Front Panel when called" and "close afterwads if originally closed" check boxes
save the VI
whenever you use this Sub VI every time it will pop up front panel
2. dont perform the changes suggested in option 1. place the instance of subVI in your main application and if you want that instance to popup a front panel then right click on subVI and Select "SubVI Node Setup" again select "Show Front Panel when called" and "close afterwads if originally closed" check boxes
with this option only certain instances of SUB VI will cause pop up to occur
3. this is the most flexible option. use invoke node to show front panel. in invoke node select show front panel method to popup the VI and use close front panel method to close the pop up window.
Tushar Jambhekar
[email protected]
Jambhekar Automation Solutions
LabVIEW Consultancy, LabVIEW Training
Rent a LabVIEW Developer, My Blog

How to display remote front panels of subvis that are already open

I inherited an RT project that uses remote front panels for nearly all the user interfaces. The host application opens a remote front panel the the top level RT vi, and there are several subvis on the RT system that are opened from that top level vi and thus displayed on the host (i.e. their "Show Front Panel When Called" properties are set TRUE).
If the Host loses its connection to the RT system when any subvi front panels are opened, and the host application is restarted, it can re-open the top level vi remote front panel, but all the RT subvis that are already open will not display their front panels. I am looking for a way to open the front panels to these subvis from the host application.
The kicker is, I need to know which subvis are actually running before I attempt to open remote front panels. Is there any way to determine what subvis are actively running (and not just in memory, such as subvis that won't get executed until the top level vi reaches a certain state)? I am thinking that I could create a list of the subvis that I need access to, check to see if any are actively running on the RT system, and then invoke a remote front panel connection with those that are running.
Does anyone have any ideas as to how I might be able to do so? Or any other suggestions? [and yes, I know that RFP communication is probably not the best way to go, but we're too entrenched in this software to start over with a new system!]

TurboPhil wrote:
If the Host loses its connection to the RT system when any subvi front panels are opened, and the host application is restarted, it can re-open the top level vi remote front panel, but all the RT subvis that are already open will not display their front panels. I am looking for a way to open the front panels to these subvis from the host application.
It might be possible to work around this behavior by placing VI invoke nodes in your top level VI that reference each of your subvis and setting the Wait Until Done invoke method to false. This should cause the subvi to close when the top level VI closes even in the case of an unexpected restart.
You can access this invode node in the functions pallet by selecting Application Control » Invoke Node and also selecting Application Control » Static VI reference. Wire the Static VI Reference to the vi reference input node and double click the Static VI Reference and select the appropriate subvi in the dialog window. Left click on the Method section of the invoke node and select Run VI. Finally right click on the Wait Until Done invoke method and select Create Constant and ensure this constant is set to false.
TurboPhil wrote:
The kicker is, I need to know which subvis are actually running before I attempt to open remote front panels. Is there any way to determine what subvis are actively running (and not just in memory, such as subvis that won't get executed until the top level vi reaches a certain state)? I am thinking that I could create a list of the subvis that I need access to, check to see if any are actively running on the RT system, and then invoke a remote front panel connection with those that are running.
You can access this information by using the Real-Time System Manager (Tools » Real-Time Module » System Manager). This can be used to show what VIs and subvis are loaded into memory and which are running.
For more information on using this tool please referere to this Knowledge Base article.
Message Edited by BLAQmx on 02-18-2008 11:40 AM
Mark
LabVIEW R&D

Open front panel of sub vi when called - how?

Hello,
I have a VI with several sub VIs.
I want some of the sub VI front panels to be opened, if they are not yet opened and if they are called but I want them to stay in the background.
There are two SubVI Node setups: "Open Front Panel when loaded" and "show front panel when called"
Both are not what I want. If I select "show front panel when called", then the front panels are opened but flickering because they are called often and alternately.
Greetings Johannes
Using LabVIEW 7.1 and 2009 recently
Solved!
Go to Solution.

johanneshoer wrote:
No, no issue with my code :-)
Yeah, we've heard that one before...
@smercurio_fc: With your example I can see if a subVI is opened or not, but how can I open the subVI during run time if it is not opened
Just call the method with it set to "write" (right-click and select "Change to Write"). I don't recall if LV 7.0 has a Front Panelpen method. Check the LabVIEW manual.

Front panel window:open ? property

Similar Messages

Maybe you are looking for