LabVIEW 2010 Window Size/Panel Size Run-Time VI properties - unexpected behavior

[wildcatherder]

I have used the VI Properties Windows Run-Time Position - Panel Size and VI Properties - Window Size to set the desired display size for use on the application PC.

A strange thing happens, when I first open the application window, it is smaller than the specified Window Size and Panel Size (both set to 1064 x 728).  However, if I click on a horizontal border the window's vertical size snaps instantly to the 728 pixel value and the horizontal size in unchanged, still smaller than the 1064 value specified.  When I click on a vertical border, the horizontal size changes to the specified value.

I don't believe this is how these properties were intended to work.  They should open the application in a window sized as specified.  

Is this a known problem?  Is there a workaround.

[wildcatherder]

Note that the build PC and the application PC are both Win XP Pro operating system.

[Tanya_V]

Would you be able to post your VI and your executable in a ZIP file so I can quickly reproduce this? Otherwise, it might take a little longer for me to replicate this behavior.

Also, have you observed this behavior with any other program or just this one?

[wildcatherder]

I regret that I cannot post my employers' proprietary code.  I have tried to duplicate the problem with a publicly distributed VI and been unable to do so.  

I believe now that it is possible my VI was "straddling" two monitors when I made the initial changes.  

Later compilations were made using different VI properties and do not show this problem.

I have attached a file showing the relevant VI property settings used in the aberrant VI compilation.

[Tanya_V]

Hi,

I've also tried reproducing the problem with the same VI properties as yours. I've also tried having the VI straddle two monitors but have not observed this problem. If you are able to reliably reproduce the problem, would you be able to post the steps here?

Thanks!

[wildcatherder]

I have not been able to reproduce the problem in subsequent builds but I do still have the version that exhibits the problem.  While I am not able to post that VI on a public forum, I would be willing to send it as an e-mail attachment.

[Tanya_V]

To get your project to NI directly, I would recommend creating a service request for a Bug Report. You can create a new service request here. Then you can send your project to us.

Thanks!