disable view as icon

[lavalava]

Every time I create a new controller/indicator from the block diagram windows, it keeps placing the newly created controller/indicator from block diagram windows as "view as icon".  How do I disable this view so that it always default to false?  I don't want view as icon.

[lavalava]

oh I found it, never mind ...next question, when I created a waveform scope ...how do I make it zoomable so I can zoom in and out?

[smercurio_fc]

What's a "waveform scope"? I assume you just mean one of the graphs. Right-click on the graph and select Visible Items -> Graph Palette. This is explained in the LabVIEW Help.

[KianABC]

Where was it? I'm looking for the same thing. I want the new controllers/indicators NOT to show as icons. The icons are too big and useless to me.

[smercurio_fc]

It's in the LabVIEW options:

[GerdW]

Hi Kian,

options -> block diagram (just the first entry with LV2009).

Where else have you been looking for that?

[RTSLVU]

On the same lines here...

Is there a way to make the express vi's (mainly the Time Dealy vi) default to "view as icon" on the block diagram?

[Mike_B.]

I never understood why this is enabled as a default.  Is there any benefit to having an object that is 3x as large as a front panel terminal symbol?  Block diagrams get very crowded for space once your code becomes rather complicated.

I switch mine off as well.

[Hooovahh]

Apparently new users prefer the big and bulky.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Default-Option-Do-NOT-Place-Front-Panel-Terminal-as-Ic...

As for the express VI's that is a good suggestion and I've never found a way for an express VI to default as a small Icon View (and turn off the caption).  If this is hidden INI key I want it.

But honestly I use express VIs so seldom that it doesn't bother me too much.

[Mike_B.]

Thanks for pointing that out to me.  I can't believe NI would consider nuking the small terminal symbol in future releases. 

Everytime I drop one of those dopey looking icon terminals on my diagram and revisit the code later, for a split second my mind reacts "where did that silly looking sub-routine come from?  who made that?" and then I recall it is just a terminal with a pitiutary malfunction.