How To Download Video From Popup Window
Pinkie Mclucas
I have a popup window that needs to access the parent dom to generate a print page. The structure of the print page is significantly different then the structure of the parent so a print css would not solve the problem. I basically want to popup a window and then have that window grab some data from the parent of even access the dom from the popup and generate the print page without having to go to the server again. Any ideas how i can achieve this?
Thank you, PGriffith. This was my understanding as well, but attempting to change those settings to match a popup window never seemed to succeed as far as causing it to behave like one, but I believe that it is probably my own miss-understanding somewhere. I will do my best to double check again,
I was attempting to see if it was possible to pass a parameter to a popup window using a script that is ran from another window. All of the articles from ignition that I've found have been about using buttons and the navigation tab of an event handler, but I'm attempting to pass this data using a script as the information I want to pass in is more than I can do with just an event handlers property binding.
This thread is also a few years old so you may want to start a new thread, and if you do - you should show what you are trying now and what errors you are getting from your current method. It's the easiest way for people here to help troubleshoot your issue, is if we can see the actual code.
Easiest way to find an example script is to use the built-in GUI to configure one popup with parameters and then go to the script page. It'll auto generate a script and show you how parameters are passed in.
Hello I have Main Vi containing Many sub VI I set some of them to pop up when I press ok button, I set the subvi using VI properties to pop up when called. However it pop up and it is start to appear and dusappear very quickly with changing data from loop. What I want to do is to make that subvi controlable so I can close and open it easily and avoid the twikling window that happen to me now. I attached picure for part of my block diagram for main vi with subvi icon getteing the data from main vi to draw graphs in subvi.I hope this clear.
What you are seeing is by design (both LabVIEW and your code). The while loop cannot iterate until the subVI finishes if it has been called. Since you have it set up as a modal dialog, and to close its panel when it finishes, then it opens, writes data to the graph, and then closes, since that's all that's in there. What you need to do is to launch the VI dynamically so that you can leave it running while your loop continues. This means that when the popup VI is launched, it needs to keep running. I.e., it needs it own loop (though not a Greedy Loop). Your button would open/close the VI. Or, you can just have the button on the main panel open the popup, and have a button on the popup to close it (or just use the "X" button in the top-right). You can pass data to the VI using queues. Examples ship with LabVIEW on launching VIs dynamically.
In the Producer/Consumer architecture, you would ideally keep only the production of data (i.e. DAQ Assistant in your application) in the producer loop. This will ensure that the processing (or "consumption") of data (i.e. all other operations like writing to file and analysis in your application) does not affect the acquisition of the data. It is also important to use the error clusters of the queue functions - and correctly remove the queue from memory (Destroy Queue) - this is also used to stop the consumer loop (when queue no longer exists) by default.
I talked about race conditions and then forgot to initialise the stop variable myself! You would want to write a false value to the stop variable before going into any of the loops to ensure none of them read "true" from the previous run of the application before the producer loop sets the value to false. Required modification:
Popups exist from really ancient times. The initial idea was to show another content without closing the main window. As of now, there are other ways to do that: we can load content dynamically with fetch and show it in a dynamically generated . So, popups is not something we use everyday.
Theoretically, there are window.focus() and window.blur() methods to focus/unfocus on a window. And there are also focus/blur events that allow to catch the moment when the visitor focuses on a window and switches elsewhere.
I'm having a issue with quickbooks 2012 that I published with XenApp 6.5. Sometimes when a user goes and hits a button like 'Print' it is supposed to popup a dialog box. But the problem is (from what I can figure) is the popup is appearing behind the Quickbooks application which is resulting in it locking up since they cannot access the dialog box.
I have tried ALT+TAB which I believe doesn't work in a seamless session anyways.
How could I resolve this?
Its possible that it is popping up on the far right (outside of the quickbooks window in seamless mode) and not behind it. I noticed when I launched it from the server and did the same steps the window popped up on the FAR right. I moved it back to the center and the user relaunched quickbooks and now they see the window??
How could I resolve this?
Let me read what you have sent and i'll try that!
Now it is possible that it isn't popping up behind the window. It is possible the window is appearing on the FAR right because when I launch the application from the terminal server (where it is published from) the window appears are the far right. I move it back to the center and close the application and the user relaunches it and they can now see the window.
Could it be another user having dual monitors is using it and when this user launches it (doesn't have dual monitors) it is still acting like it does? The sessions should be completely seperate though so I wouldn't think that would happen
The user that was having problems is using a single monitor. I'm using storefront and used to you could change the user setting on how the window was sized. But this option seems no longer available.
I can't take seamless away from everyone so I need to do it for this particular user but couldn't figure out how
I'm going to close this because it hasn't happened again. If it does I will try the SHIFT F2 to take it off of seamless session and see where the window is (if I can) and will update this forum.
Thanks for all the suggestions!
Ok it happened again. This time I had the user (different user experienced it) hit SHIFT F2 and they found the window hiding off to the side (way off to the side)
This is why it locked up. Sorry to be a noob but I'm having trouble understanding the registry flags and how to use them. Do you have any advise on which exact one to use or is it kind of hit or miss?
A popup window is typically a window that "floats" on top of the main window. It can be resized and moved around by the user, all while the main window is still open in the background. Popup windows are great for displaying additional information about a selected item on the screen, for example a details screen about one particular component. Popup windows are often opened by components in a main window, and are meant to be on top of the screen. They are used to view setpoints and zoom into a specific area.
The great thing about Popup windows is they can also be parameterized so they can be reused. One popup window design can be reused for many components as long as the proper information is passed to the popup window.
Before you can open a popup window, you have to create it. Like main windows and docked windows, popup windows are simply windows that have specific settings. In particular, popup windows are floating windows that are not set to start maximized. In the Designer, when adding a new window, selecting the popup window option creates a window with these presets. Once you have your popup window created, you can make it as big or small as you want. You can also set properties in the Property Editor to make it closeable, resizable, change the title, and display the title bar and border in the window.
In any window, you can add a script to any component to open your popup. This is easiest to do from a component like a button on the main window using the Navigation Script Builder. Simply select the Open action and the window that you want to open. Clicking on the button will then open the popup window that was selected. Alternately, you can use one of the many scripting functions that open a window.
Popup windows can also be given a specific location to open up at, when the not being automatically centered by the script. In the Vision Property Editor, go to Layout > Location and provide a specific X and Y position (in pixels).
A parameterized popup window lets you pass information from one window to another window. You can make a single popup window, change what it does and what it points to from a parameter(s) that gets passed into the receiving window using Custom properties. Parameters can range from simple integers and strings, to properties on the window that is opening the popup, and even entire UDT custom properties.
By default, the client only opens a single instance of a popup window, but you can change this behavior. For example, suppose you have four different Tanks passing all the same parameters with the only difference being the individual Tank number. In order to see all four instances of your tanks, you need to configure component scripting to display Additional Instances. This is done by selecting the Additional Instance option when setting up the navigation scripting action.
I have a strange bug, where certain pop up windows in matlab are cut in half.
I attached two examples. One is in Image Labeler, the other in Image Browser
As a result, I cannot create ROIs with the labeler.