LabVIEW
Screen size changes......sometimes
I started seeing some strange behavior with a VI right after I started setting properties in preperation of building it into an .exe
The VIs properties have been set to run in Maximized mode. But on starting (sometimes) the VI will very briefly flash to a very small size before maximizing.
I added a property node in the VI itself to insure that it would run Maximized and to possibly eliminate this "flashing" that I was seeing. At first I thought it worked. But occasionally I'm still seeing the problem.
What's really odd is that the size the VI seems to "flash" to is same size (and shape) of my Project Explorer window. I've never resized this VI to look anything like that, and certainly never saved it that way.
So I'm curious about two things.
1. How do prevent this "flashing" from happening?
2. What might have caused it in the first place?
Is it "safer" to not use the VI's property menu to set things like mode? Am I better to do this programatically?
Thanks
What might have caused it in the first place?
My guess is. You would have kept the window small and saved it. Then You might have unchecked the "window resize" option in window appearence. So now the window will be small initially and your property node might set it right and you are seeing a flash.
Just my guess 
My guess is. You would have kept the window small and saved it. Then You might have unchecked the "window resize" option in window appearence. So now the window will be small initially and your property node might set it right and you are seeing a flash.
I'm about 99.7% sure that I never saved that particular VI in any size other than maximized. Until I get my new laptop, (hopefully this week) I'm still doing everything in 1024x768. So even maximized isn't all that big. Especially when you're talking about an app that pulls from a database and dumps into a big table.
Yesterday I changed the VI's properties through the menu to stay "Unchanged". But I still left the property node in place that Maximizes the FP when the VI starts. I think that may have fixed it.
Thanks for your reply MY,
In this case I don't want the screen size to change, and I certainly don't want to scale my objects on that panel. Not sure if you've noticed or not. But if you scale all your front panel objects, they can tend to move around when size changes. There are some tricks to minimize this effect. But it's a fair bit of work.
Of course....I haven't tried resizing with scaled objects in 2009 yet. Maybe it doesn't do that anymore.
I'm about 99.7% sure that I never saved that particular VI in any size other than maximized. Until I get my new laptop, (hopefully this week) I'm still doing everything in 1024x768. So even maximized isn't all that big. Especially when you're talking about an app that pulls from a database and dumps into a big table.
Yesterday I changed the VI's properties through the menu to stay "Unchanged". But I still left the property node in place that Maximizes the FP when the VI starts. I think that may have fixed it.
Any particular formula u used to arrive at 99.7? (
just kidding)
muks wrote:
I'm about 99.7% sure that I never saved that particular VI in any size other than maximized. Until I get my new laptop, (hopefully this week) I'm still doing everything in 1024x768. So even maximized isn't all that big. Especially when you're talking about an app that pulls from a database and dumps into a big table.
Yesterday I changed the VI's properties through the menu to stay "Unchanged". But I still left the property node in place that Maximizes the FP when the VI starts. I think that may have fixed it.
Any particular formula u used to arrive at 99.7? (
Its not what we don't know that causes the biggest problems. The biggest problems come from what we DO know, incorrectly. Challenge your assumption! After all, you haven't solved the problem yet 
