Does everyone here have a 4000x1500 monitor?

[camerond]

<Warning - Rant starts here>

Come on, can't we shrink these BDs and FPs just a little bit? It seems like a common size of the block diagrams posted these days is about 3X my monitor width and 2-3X its height. And the front panels don't even come close to fitting. I don't know about anyone else, but I have trouble following things when I have to scroll all over the place to follow wires. Is the new standard monitor for programmers a 55-inch diagonal OLED?

I like to try to help folks, but this just makes it impossible.

<Rant ends here - Return to normal>

Cameron

[crossrulz]

I feel your pain.  But I find most people just have huge windows open but using very little of the window.  Luckily, I have a nice little plug-in I made to shrink the windows down.

[billko]

I think some people DO have that huge a monitor because some of the VIs I open are barely visible in the lower right corner...

[altenbach]

Many users have dual monitors, of course.

I have a single one, but it is 2560x1440, which is sufficient for all I do. My diagrams are always small compared to the screen size and I am always annoyed with all the forum attachments that have the front panel and diagram maximised to the screen. 😞  When opening them, all I get is a whiteout condition with a little code in the upper left corner and the rest all empty white diagram or grey front panel, covering everything else I am working on (Yes, I do many things in parallel!). 😮

Anyway, this is a good time to revive my old proverb:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
If your LabVIEW problem can be solved by getting a bigger monitor, the problem is elsewhere.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

[GregSands]

---

@altenbach wrote:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
If your LabVIEW problem can be solved by getting a bigger monitor, the problem is elsewhere.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

---

True.  However, I must say that having two 1920x1200 monitors is great for development.  Especially to find room for the Project window, the Help window, and a few pinned palettes, without obscuring where I'm coding.

[altenbach]

---

@GregSands wrote:

True.  However, I must say that having two 1920x1200 monitors is great for development.  Especially to find room for the Project window, the Help window, and a few pinned palettes, without obscuring where I'm coding.

---

Agreed. I recently tried to do some local instrument debugging of my software using a 1024x600 netbook... grrrrr. After a few minutes I connected an external monitor in order to be able to breathe. 😄

[crossrulz]

---

@altenbach wrote:

---

@GregSands wrote:

True.  However, I must say that having two 1920x1200 monitors is great for development.  Especially to find room for the Project window, the Help window, and a few pinned palettes, without obscuring where I'm coding.

---

Agreed. I recently tried to do some local instrument debugging of my software using a 1024x600 netbook... grrrrr. After a few minutes I connected an external monitor in order to be able to breathe. 😄

---

I'm lucky enough to have a very good laptop with a large screen to work on.  But when I go to a test set with a 19" monitor, I feel so crowded.

I like when I'm docked at my desk where I have 2 1920x1200 monitors.  Even still, I tend to keep all of my code on my main monitor, leaving the help and other stuff on the second monitor.  Just helps to keep things out of the way.

[Norbert_B]

Hehe, nice that diagram size is such a concern for most developers.... that is why styleguides recommend a size of 1024x768...still 😉

I think that something with 1280x1024 is also ok, but it shouldnt exceed that in a normal VI....toplevel VI, maybe.

I often receive block diagrams which are six times the width of my laptop (1920x1080) and four times the height with the request for debugging. Sorry, this is not debuggable. NO WAY.

So, keeping diagrams small not only helps yourself in managing your code, but it also enables other developers to HELP you!

thanks,

Norbert

[StevenHowell]

care to share that plugin? 

[crossrulz]

---

@stormchaser373 wrote:

care to share that plugin? 

---

Mine does so much more and I don't feel comfortable sharing it at the moment, mostly because I just used code from other people's RCF and QD plugins.  But in the mean time, you can just use jcarmody's Quick Drop Plugin: Move Block Diagram Contents to Origin.  I got him to shrink the window as well.