02-25-2015 09:00 AM
I have been having an issue (a mildly infuriating one) where my window size changes after running. See images
The window expands by the size of the scroll bars in the x and y axis. It only happens sporadically - I can't figure out a way to predict when it will happen or not. I'll just be running/stopping the program and then bam! different front panel size. I've also had it happen on multiple different machines with multiple different programs. There was no code in any of the programs that resized the FP window. I know I can force the runtime size with VI properties, but...
02-25-2015 09:10 AM
Which LabVIEW version are you using?
02-25-2015 09:43 AM
02-25-2015 10:10 AM
@ben64 wrote:
I've seen this before but not lately so it may be related to OS/LV version. What are the Window appearance and window size settings? It look like it is set to Dialog, Scrollbar setting? Does the same thing happen when you set the front panel to run mode (Ctrl+m)?
Ben64
The version is LV2014 run on Win 7.
I haven't seen it happen from going in/out of runtime mode. Window appearance settings are custom, but nothing fancy. Just hiding options I don't want the users to do.
02-25-2015 12:06 PM
02-25-2015 01:52 PM
I gutted the linked vi (with notes on what was changed) and attached it if you want to try and reproduce it. After some more playing around with it, I realized it is any time I first open the VI and run it. It seemed random because the VI was part of a project and I was frequenly opening / closing / running etc.
02-25-2015 02:13 PM - edited 02-25-2015 02:30 PM
02-25-2015 02:45 PM
@ben64 wrote:
Definitely related to the Run when opened execution mode.
Ben64
It is related to that. I tried making another very simple VI to reproduce the bug (same window / execute / position settings), but was unable to do so. I did notice that it resizes the window when bars are set to "Always Off" and "Off While Running" - but not with "Always On".
02-25-2015 03:03 PM
02-25-2015 04:12 PM
Bah. More workarounds for bugs...
I ended up just fixing it with the "Window Run-Time Position" setting.