Changing window size

[Norbert_B]

---

Vaibhav wrote:

[...]ahaa, yes, I had overlooked this option. but does it give resize-proof decorations? You mean, to create/destroy them at the run time. huh?[...]

---

Last question first:

No, there is no "resize-proof" mechanism due to the display being "digital" (as opposition to analog). I am saying that because just as sampling an analog signal, you will have errors caused by quantisation of the ADC. This can be "transferred" to displays as well: you have a limited resolution given by the pixels. This means, that you have rounding errors when "freely resizing".

LabVIEW does not support creation/removal of controls/decorations during runtime. So this is no solution. But you can play around with the property "visible".....

Now the other questions:

(0) I will do when i have some time to spare on this.

(1) "Floating" is an option for panels. "Popup" in general means a dialog box popping up during runtime displaying current important information (or asking for it). If it is modal or floating does not matter for this. Indeed, a popup is a vi called with the setting "show frontpanel when called" and "Close afterwards if originally closed"

(2)  Nope, the launcher will not display it's panel (except you want to have a so-called "splash screen" during startup which would come handy here). The launcher would look like this:

The UI itself would work like a module calling a dll.....

(3) see (0)

hope this helps,

Norbert 

[Vaibhav]

---

Norbert B wrote:

Last question first:

No, there is no "resize-proof" mechanism due to the display being "digital" (as opposition to analog). I am saying that because just as sampling an analog signal, you will have errors caused by quantisation of the ADC. This can be "transferred" to displays as well: you have a limited resolution given by the pixels. This means, that you have rounding errors when "freely resizing".

LabVIEW does not support creation/removal of controls/decorations during runtime. So this is no solution. But you can play around with the property "visible".....

Yes, I'm also against "freely resizing" in labview, as long as I am very much demanding for the FP looks with multiple controls on a tab control. Great, the "visible" On/Off will save them from being cramped? I'll do an experiment on this. But even then, donno if it's of help, since I cannot hide the decorations all of a sudden, unless they are on the page which is not visible to user.

Now the other questions:

(0) I will do when i have some time to spare on this.

(1) "Floating" is an option for panels. "Popup" in general means a dialog box popping up during runtime displaying current important information (or asking for it). If it is modal or floating does not matter for this. Indeed, a popup is a vi called with the setting "show frontpanel when called" and "Close afterwards if originally closed"

Cool, remember reading something like this in the book., about these options.  Thanks for the explanation. Now I see these "obvious" looking options make sense, in case of a popup.

(2)  Nope, the launcher will not display it's panel (except you want to have a so-called "splash screen" during startup which would come handy here). The launcher would look like this:

The UI itself would work like a module calling a dll.....

So this is more or less something like what I had posted earlier in this thread (AlternateGUI.zip), with the two inputs modified ---

Yes? Or these two approaches are different? This is with two VIs having their GUIs. Redundancy of codes. I am sorry, but still not getting an idea of 2 UI on a single VI. can you please make a small example? I would appreciate that.

---

Thanks for all the tips!

[Norbert_B]

Your approach differs in the way it works. My approach is a simple launcher which would retrieve the current resolution and therefore selecting the most fitting UI VI. This does not need any dialogs (except if desired) and the launcher will start up the VI and then finish working. This is what we define as "Launcher".

I'd call your approach a "controller" because your controller launches the UI VI, but wait on its termination. This is a little difference, but remarkable.

Regarding the decorations: sure you can "hide the decorations all of a sudden". All you need to do is to defer panel updates, loop over the decorations and set them visibl/invisible. After this loop, remove the defer panel update and the UI will update all changes in a single turn.

hope this helps,

Norbert 

[Vaibhav]

---

Norbert B wrote:

Your approach differs in the way it works. My approach is a simple launcher which would retrieve the current resolution and therefore selecting the most fitting UI VI. This does not need any dialogs (except if desired) and the launcher will start up the VI and then finish working. This is what we define as "Launcher".

I'd call your approach a "controller" because your controller launches the UI VI, but wait on its termination. This is a little difference, but remarkable.

---

Yes Norbert, I understood this difference. I would say your approach is what is better in my situation. I would need the launcher, and not controller. Actually I was not sure about the usage of those two boolean inputs. So your sample helped me in that way.

BUT, again, this is not a single VI with two UIs literally. Even in your approach (actually our approaches are different only in the way the VIs are called and stopped, I see), there are two VIs apart from the launcher VI. The redundancy of code. No? If this is incorrect, I would appreciate, if you could just make a small application with the VIs that you're saying. If possible for you.

---

Norbert B wrote:

Regarding the decorations: sure you can "hide the decorations all of a sudden". All you need to do is to defer panel updates, loop over the decorations and set them visibl/invisible. After this loop, remove the defer panel update and the UI will update all changes in a single turn.

---

I read the description of this property in the help and it's not clear to me. The phrases are not written well, or I'm unable to catch them up. May be something is missing in my understanding of the "Defer panel updates". How they will help me in this situation? Redraw them after the application is launched or what? Sorry if I sound too dumb.