Wondering Why, File Dialog Question

[JÞB]

---

@aputman wrote:

The File Dialog is probably the one that least requires an Express VI.  If you open the Selection Mode window of the primitive VI, it looks the same as when you double click the Express VI.  All other parameters are wired as inputs for both methods.  I see no difference between the two.  

---

Turn on context help (Ctrl + H)  See the difference now?

[aputman]

---

Jeff·Þ·Bohrer wrote:

 Turn on context help (Ctrl + H)  See the difference now?

---

Not really.  Nothing significant, that is, except that the primitive is not supported on a diagram.  It confirms that the inputs/outputs are the same as the Express VI.  The default selection mode for both is "New or Existing Files".  I'm just saying that I see no benefit to the Express VI, for this particular function.  I don't use the Build Text Express VI but I can see where that adds a huge user experience for a beginner that doesn't know formatting codes.

I'm probably missing out on something, since my company only chooses to upgrade Labview every 5 years.  

[JÞB]

See This express vi is configured as follows... That is worth an index sized area of BD Constants and comments.

Now, that does not mean that Express vi's should ALWAYS be used.  They have appropriate uses and use cases where they are less appropriate.  Just like any vi.  And, unfortunately some have real problems deep in the innards. 

Learn how to use each tool for the purpose it was built.  There are no "Screw Hammers" 

 OTOH I tend to use this attachment

OK You can get one here but, it really is a joke like the Signetics 25120 IC

[aputman]

Sorry, can't open your VI.  

I just don't see where that one comment in the help file justifies an express VI and gives a better user experience.  The primitive VI help file could be updated to include that statement.  Other than that, the icon has color and as Altenbach pointed out, the label doesn't align with the blue square.  

I'm not trying to argue with anyone.  I'm just backing up my irrationality with reasons.  

[JÞB]

OK, let's not argue.

But, Having the RCM selection mode as a express configuration (with a default to configure express vis immediately) and exposing the mode in the context help sure beats R-Clicking and tossing up a modal dialog to find where you chose the wrong selection mode:) JMO  You can have yours.

Of course, that begs the question --- "Why the F Cluster to Array isn't an Express.vi with the primitive depreciated?" But, that question I'll leave to some Proven Zealots to answer.

[Darren]

Just to add to what Jeff said, built-in functions (primitives) with custom right-click options for configuration have been historically difficult for LabVIEW programmers to use (just do a forum search for "Array to Cluster" to see what I mean). The Express VI has an easily identifiable form factor (blue halo) that shows that it is a configurable node. And as I mentioned above, there's not much value in having diagram space taken up by the constants needed to configure a File Dialog.

Also, I should point out here that Express VIs as we know them today do not exist in LabVIEW NXG...instead, the configuration pane (on the right side of the editor window) is the universal mechanism by which all node-level configuration is provided.

[altenbach]

---

@JÞB wrote:

"Why the F Cluster to Array isn't an Express.vi with the primitive depreciated?" 

---

I assume that you actually mean "array to cluster". Forgetting to set the cluster size is a very common mistake.

All that said, I was using the classic file dialog way before the express version came out but switched to the express VI for no good reason except to save a few clicks finding the classic version. 😄

(Similarly, in the kitchen I prefer a big butcher block board and nice set of chef's knives over a closet full of single-purpose tools and small appliances any time. (The espresso machine is an exception!) The cutting time you save with a banana slicer is paid back several times in first trying to find it and then in cleanup time. The time limiting step is the peeling anyway, but a banana peeler is an entirely different tool again, not be used on bananas. :D).

[Hooovahh]

---

@JÞB wrote:

---

@aputman wrote:

---

@Darren wrote:

The only reason I've seen for using the function instead of the Express VI is for developers who have an irrational hatred of Express VIs. 😉

---

Those irrational developers account for 85% of the Active Participants on the forums.  

---

Eventually the remaining %15 of the rational Active Participants may become Proven Zealots.  Go ahead and take a poll on these 12 individuals:

---

Is the question "Do I have an irrational hatred of Express VI"?  If so, the answer is no, but I do only use File Dialog and Elapsed Timer.  And actually I've taken the Elapsed Timer and turned it into a normal VI (removing the crap I never use) and have been using that since all the stinkin time it goes missing for some reason.