LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
muks

Default Browse button on File Path control

Status: New

When i create a file path control in say a read image.vi I have to manually right click and select view "Browse button". It will be helpful if this is made as a default thing.

 

id1.PNG id2.PNG

 

to get this

 

id3.PNG

13 Comments
Knight of NI
I'd guess you're right-clicking on the connector terminal and selecting Create -> Control. In this case, LabVIEW will create the same control (in the same style) as what's on the subVI. So, are you asking to change the subVI, or LabVIEW's behavior? If it's the latter, in what way? How should it behave for other controls?
muks
Proven Zealot

I guess my point was a real simple one. A file path control without a browse button doesnt make sense. All I want is to eliminate clicks by keeping the browse button visible all the time.

 

And I have indeed modified the subvi to show me the browse button but tweaking with subvi for whatever reason isnt actually ok for me personally.

AristosQueue (NI)
NI Employee (retired)

Someone turned off the browse button on this control. Since it is there by default, they must have done it deliberately. I don't know why, but the design of controls on a front panel is up to the designer of that front panel, and when a caller does "Create Control/Indicator" from the terminal, we replicate the chosen design. You should find the author of this subVI and ask them why they wanted the browse button removed for callers. I don't actually recognize those subVIs... if those are subVIs from National Instruments, you should post a question to the dev forums asking for either a good explanation or that the browse buttons be restored in a future version.

 

I do think that the policy of "we take what the subVI designer chooses" is a good one as it has allowed many good API customizations. I don't think we want to change this for one control type. 

Lavezza
Active Participant

There are some common NI VIs that do this. I'm thinking about the read/write spreadsheet and the read/write JPG/PNG/BMP VIs. (At least in 8.6.1. I"m not at a 2009 machine right now)

AristosQueue (NI)
NI Employee (retired)

CAR filed to review vi.lib VIs. I made it a general "review for this issue" CAR, but I noted the spreadsheet and graphics file VIs specifically. No guarantees that it'll be fixed in the next version, but at least it is being tracked as a bug issue now.  CAR# 197449

muks
Proven Zealot

>>if those are subVIs from National Instruments, you should post a question to the dev forums asking for either a good explanation or that the browse buttons be restored in a future version.

 

The "Imaq Read" is indeed an ni sub vi

parthabe
Trusted Enthusiast

I can say almost(for my safety) all the (Sub)VIs of NI that use the Classic File Path Control have this behaviour Muks has mentioned.

 

If you see the Open/Create/Replace File VI, it works fine (with the Browse button visible) as back as LV 7.0 as I can remember.

Message Edited by parthabe on 11-25-2009 06:43 AM
- Partha ( CLD until Oct 2024 🙂 )
muks
Proven Zealot
>>

I can say almost(for my safety) all the (Sub)VIs of NI that use the Classic File Path Control have this behaviour Muks has mentioned.

 

If you see the Open/Create/Replace File VI, it works fine (with the Browse button visible) as back as LV 7.0 as I can remember.

 

I can say from 6.0 (My first lv version). I working on image processing have got used to this. It is actually like an automatic thing i follow all these years. Want to read a image then use imaq read-->Create control--> Right click browse button--> open the image. 

 

Not much of a difficulty but some clicks which can very well be avoided.

Knight of NI
So... I'm still confused, muks. Are you asking to change LabVIEW's behavior, which copies the control as the VI set it up, or are you asking to update the VIs/functions? I disagree with the former. Don't really have an opinion on the latter, but a CAR has been opened to look into this. My own personal opinion is that I don't think it should be a high priority given NI's limited engineering resources.
muks
Proven Zealot
We are not talking about priorities here. Are we? Let it get changed after 10 years. I def not asking the labVIEW's behavior to be changed. It is fine in just creating what the subvi is creating. If there is a slight improvement that can be made within ni subvis then I suppose it can be asked to. I dont see a problem here.......