LabView windows minimizing and resizing while programming

[spaceman_spif]

I'm working on a program using LabView 2013 (service pack 1) and it's been acting strange the last couple of days.  I'll be doing something simple, like wiring a connector or just moving around an item on the block diagram when all of a sudden the block diagram will minimize and then the front panel pops up and suddenly doubles in size.  Then I have to bring back up the block diagram and resize the front panel.  It seems like it's trying to resize everything at random times while I am programming.  Any ideas what's causing this?

[spaceman_spif]

It appears to happen most often whenever I undo something.

[James.M]

Have you tried turning it off and on again?

Is this only in LabVIEW? It sounds like a Windows issue. The only thing that resizes a LabVIEW window in the development environment is Windows or the window shortcuts. Example: ctrl+T will put your FP and BD side by side.

[spaceman_spif]

Yup, I rebooted, burnt an offering, danced a happy jig, everything.  It's only happening in LV.  I've had resizing issues before when I take my laptop home and work on a program then when I come back in to work and connect it to my dock (which has two monitors) and I find items on the front panel changed sizes.  Locking the front panel helped there.  But this is new and it just started a couple of days ago.  It's happened both at home (just my laptop) and at work (connected to a dock with two monitors).

Btw, operating system is Windows 7 Enterprise, service pack 1.

[James.M]

Dang... it might be something wrong with your install.

Oh wait, you said it happens on both your Laptop and your work computer..???

Is it specific to a certain VI or set of VIs? If you create a blank VI and mess with it or open an old VI you haven't worked onin a while, does it change?

The closest thing I can find is this post from 2005 and it says the bug was patched long ago.

[Bob_Schor]

Look at the Text Settings on the Front Panel and Block Diagram.  I've noticed that the default Point Size (right now, my home system shows 15 pt) seems to be set by the resolution of the monitor on the system you are using.  So if I bring code home and work on it with my laptop, new Controls, Indicators, and other things may have different text sizes because the defaults on my laptop might be, say, 14 pt.

I've noticed less of this in recent years -- I'm not sure whether this is due to changes in LabVIEW (and thus might be Version-specific), changes to my hardware (I might have stumbled onto configurations that have similar resolutions), or changes "somewhere else".  See if you notice a change in the default Point Size when you switch environments, and let us know if this explains what you are seeing.  How to fix it is another matter, but identifying and clarifying the cause gives you some place to start.

Bob Schor

[spaceman_spif]

I'll look into the font size and see.

And my laptop is my work computer.  I have a docking station for it at work.

[spaceman_spif]

Interesting...after I finished replying I went back to my programming and found my front panel was once again expanded to cover both monitors.  I noticed the font for the front panel was set to "25 pt current font" while the block diagram was set to "15 pt application font".  I've set both to "15 pt application font", so let's see what happens.

[tst]

---

@James.Morriƽ wrote:

The closest thing I can find is this post from 2005 and it says the bug was patched long ago.

---

With Spif coming back and a bug along these lines I feel like I *am* in 2005 (and that bug was annoying enough that as soon as I saw the mention of undo I immediately thought about it too, although that specific bug was definitely fixed, as mentioned there).

[spaceman_spif]

---

@tst wrote:

---

@James.Morriƽ wrote:

The closest thing I can find is this post from 2005 and it says the bug was patched long ago.

---

With Spif coming back and a bug along these lines I feel like I *am* in 2005 (and that bug was annoying enough that as soon as I saw the mention of undo I immediately thought about it too, although that specific bug was definitely fixed, as mentioned there).

---

Wait...what year is this??  You mean...my time travelling subroutine actually worked?!??!??