File Dialog

Dear all,
I have developed a screen and wish to let user to invoke a file dialog. I know the following code can display a file dialog button at selection screen level. How can i define the same thing by screen painter?
DATA: v_rc TYPE i.
DATA: lt_filetab TYPE filetable.
DATA: ls_filetab LIKE LINE OF lt_filetab.
PARAMETERS: p_file TYPE localfile.
AT SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
CHANGING
file_table = lt_filetab
rc = v_rc
EXCEPTIONS
file_open_dialog_failed = 1
cntl_error = 2
error_no_gui = 3
not_supported_by_gui = 4
OTHERS = 5.
READ TABLE lt_filetab INTO ls_filetab INDEX 1.
IF sy-subrc = 0.
p_file = ls_filetab-filename.
ENDIF.
Regards,
KK

Hi,
Thats good.
In your screenpainter flow logic.
lets say the button you are prompting is FILE_BUTTON.
PROCESS AFTER INPUT.
Field: FILE_BUTTON module get_f4_help.
in your program. between module and endmodule, paste your code to trigger the dialogue.
module get_f4_help input.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
CHANGING
file_table = lt_filetab
rc = v_rc
EXCEPTIONS
file_open_dialog_failed = 1
cntl_error = 2
error_no_gui = 3
not_supported_by_gui = 4
OTHERS = 5.
READ TABLE lt_filetab INTO ls_filetab INDEX 1.
IF sy-subrc = 0.
p_file = ls_filetab-filename.
ENDIF.
endmodule.
Thanks & Regards.
Sridhar Kasthuri

Similar Messages

I am trying to open CR2 files from a Cannon EOS 1DX camera in Photoshop CS6 and I have already updated the Camera Raw Plug in but Photoshop is still giving me the cannot open files dialog box? Help?

I am trying to open CR2 files from a Cannon EOS 1DX camera in Photoshop CS6 and I have already updated the Camera Raw Plug in but Photoshop is still giving me the cannot open files dialog box? Help?

Canon 1DX support was added to ACR in version 6.7, 7.1. An updated CS6 should be at level ACR 8.6. If your ACR is not at level 8.6 try using CS6 menu Help>Updates. If that does not install ACR 8.6 try downloading the ACR and DNG 8.6 converter and see if ACR 8.6 will install into your CS6.
Adobe - Adobe Camera Raw and DNG Converter : For Windows
Adobe - Adobe Camera Raw and DNG Converter : For Macintosh

File dialog with multiple custom patterns

I am in need of being able to user select multple file patterns (*.bin, *.exe...) in a file dialosg similar to the express File Dialog VI where it lists the directory and allows the user to select multiple files from a windows dir listing. The express VI has a patterns input that takes multiple patterns separated by a semimcolon but there appears to not be a way of providing a ring control for file type and letting the user select the pattern that he wants to filter the directory listing with. I.E> > If the user wants to only load files that are *.bin, he only wants to view them in the listing. How can I do this without mutliple dialog boxes?
Solved!
Go to Solution.

Off-the-shelf might be something like a list box that allows multiple selections. Or you could drop a cluster of booleans on the FP and parse the selected file types and place ;'s between them. You could have multiple string controls that the user inputs the file extension and then you programmatically insert a ; I can't think of something off-the-shelf that easily does what you are looking for, these suggestions require a little bit of programming but should get you off to a good start at least.
This is the approach for choosing any desired types from a list. If you want to choose only one, use a ring or combo box or enum... Much simpler when only choosing one of many.
Nathan - Certified LabVIEW Developer

Open File dialog in 1.1.0.21

This is an old issue which I thought was supposed to be resolved in 1.1, but whenever you go to the open file dialog, it still always starts in the installation directory. It does not remember the last directory used and I cannot find anything in the global preferences that enables you to specify a preferred default location. There is a feature request that is marked as complete in 1.1 which kind-of covers this issue but relating to saving files, but the behaviour of both the save file and open file dialog is the same as it was.
Using build MAIN-21.41 on windows xp.

I too was disappointed that this promised enhancement was left out of version 1.1. However, I found a workaround that helps minimize the problem.
If you have a Windows Explorer window open to the folder where your SQL file resides, you can drag-and-drop the file into SQL Developer to open it. The trick is that you must drag your cursor to the tab bar area of the SQL Developer window to get the file to open in a new tab. Dragging it to the editor section of the SQL Developer window will not open the file.
Paul

Open File dialog window when setting the value of a path type input argument in a VI call

Hi,
I am new to TestStand (running 4.0) and I want to create a sequence of VIs to turn on, setup and measure a device. One of my VIs sends a configuration file to my device. An input argument to this VI is the path of the config file. I would like to make it simple to modify this path when setting up the sequence by popping up the File Open dialog window and choose my file. Is this possible? I do not want to manually change the file during execution, just to have multiple calls of one VI, each call opening a different file according to the path given to it during the setup.
So far I have only succeeded in manually entering the absolute path each time I add this step. What makes it even more annoying is the fact that LabVIEW interprets the path with the escape codes, rendering the path unusable. Manually adding a 2nd backslash at each '\' occurence adds another step to the process. I tried both String and Path type of inputs, and the SearchandReplace() or ToUpper() (trying to bypass the escape codes) functions in TestStand don't seem to help m.
Your help is very much appreciated,
Fred

Eudaemonic,
If you want to create a series of easy to configure step types so others can develop sequence files easily, you could use custom step types. When you create a custom step type you implement your own configuration dialog. Since you have control over what controls you expose in your configuration dialog, you can design it so the desired path is selected using a open file dialog. Refer to chapter 13 of the TestStand reference manual for more information about custom step types.
If you do not want to create a custom step type but you still want to give access to your sequence developers to pre-configured steps, you can use templates. A step template is a snapshot of a step that you can reuse later. Let's assume that instead of asking your users to edit the step to enter the desired path, you create several step templates with different pre-configured paths and based on their applications requirements they could use the appropriate template. Refer to the NI TestStand Help for more information about the Templates list on the Insertion Palette.
Hope it helps.
Antonio Lie.

Please fix: Common Open File Dialog Box to support Favorites (Follow-up: Better provisioning in the Windows client)

One more thing:
What's missing is favorites is a way to use the favorites space in the Common Open File Dialog Box.
Please obsolete or (re)develop components in Windows, so those components support any new workflows in Windows!
On example of an application where you cannot use Favorites is Adobe Photoshop. It uses the Common Open File Dialog Box in Windows (which does not support Favorites).
Comparing Finder (MacOS) with Windows Explorer - you "seem" to have the option of using favorites to pin folders.
Well, if your application calls Windows to use the Common Open File Dialog Box - it's actually NOT POSSIBLE AT ALL to navigate to the user concepts (user folders) pinned to favorites.
Again, the favorites namespace is completely unused (not provisioned) out-of-the-box. That's may be ok, however it's not fully implemented across Windows and just another example of stuff accumulating up to being unusable.
What's missing is favorites is a way to use the favorites space in the Common Open File Dialog Box.
Ref.: Better provisioning in the Windows client
https://social.technet.microsoft.com/Forums/en-US/dbb2102f-00b7-47ca-88f2-4f88cd9d3409/followup-starting-launching-and-switching-?forum=WinPreview2014Feedback#2aba34e9-6074-4750-8f66-425bdeacc705
https://social.technet.microsoft.com/Forums/en-US/168bb9f9-ab18-42e6-9f20-5e36e71f742c/merging-the-task-bar-and-the-start-screen-area?forum=WinPreview2014Feedback#168bb9f9-ab18-42e6-9f20-5e36e71f742c
https://social.technet.microsoft.com/Forums/en-US/59a5bb6a-0368-4f34-bea4-b9811ac0bf8c/dont-forget-development-of-the-start-screen-remember-virtualization-of-it-too-purpose-is-hud?forum=WinPreview2014Feedback#59a5bb6a-0368-4f34-bea4-b9811ac0bf8c
https://social.technet.microsoft.com/Forums/en-US/c10168fe-a534-44aa-a0ec-e9defc71da5f/better-provisioning-in-windows-client-remember-templates-for-the-start-screen-like-the-need-for?forum=WinPreview2014Feedback#c10168fe-a534-44aa-a0ec-e9defc71da5f

Congrats to Carmelo!
Windows Phone and Windows Store Apps Technical Guru - February 2015
Carmelo La Monica
Windows Phone 8: control Nokia Maps (Part 3)
JH: "Part 3 of the series how to work with the Nokia maps control. As the previous articles this one contains a lot of code snippets and some pictures. Good work!"
Ed Price: "A great topic, a fantastic breakdown of sections with clear descriptions, and a nice mix of code formatting and helpful images! Another stellar article from Carmelo! Great job including the link back at the end to the portal
article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Open File Dialog - JSP pages

If I create a jsp page with an open file dialog will it work no matter what OS people are running? What I want to do is attach a file. It would be preferrable if I could set a "working" directory and when I open up the dialog it starts in that directory. It has to work with Windows, Macs, and Linux . If there is no way to set the "working" directory, can a cookie be created that remembers the last directory accessed from the page so that when they open up the dialog it opens up under the last directory accessed?

there is a html input type that sparks up the OS native filechooser. Thus, it should be platform independent. You should look into Apache Commons FileUpload, as it makes the process of uploading/sending files ridiculously easy.

File Dialog and Report Generation Toolkit

Hi,
I designed a VI for an electrometer calibration and it works quite well The only problem I have is the following:
I used the Report Generation Toolkit to put the measurement data in an Excel file. When I run the VI I'd like a window to pop up to define the location and name of the Excel report file. If these two things are done LabVIEW should create the specified Excel file and run the rest of the code.
So i tried this with the "File Dialog" Vi and all the needed low-level File I/O VIs and it worked.
But when i connect the "File Dialog" VI with the "New Report" VI of the Report Generation Toolkit I get an error message.
Is there any solution to get this file dialog pop up window with the Report Generation VIs?
thx for any help...!
Message Edited by Flea on 12-15-2005 03:58 AM

Wow, thanks for your fast and very helpful reply devchander!
I already tried this and it works fine
thx!

What does the open file dialog do 'under the hood' and is there a way to simulate it

What does the open file dialog do 'under the hood' and is there a way to simulate it?
I have a bug in my code (that I've posted about before, here) which I can't fix at the moment, but I do have a workaround.
Briefly, the bug:
I call a dll from a function node, to initialise and run a spectrometer. If I start up the PC, LabVIEW and run my vi the code runs without complaint, the first call to the dll to initialise the spectrometer doesn;t return an error but the spectrometer is not detected either.
I've tried various solutions, see the link above, and none work
The workaround:
If, at any time before running the code containing the function node I open an 'open file' dialog window, select the dll and click ok/hit enter then everything is fine. When I run the main code the spectrometer is detected.
I use an express vi to open the file dialog, I specify the start path and file name as constant inputs and just click ok/hit return when the dialog pops up. I don't do anything with the dialog outputs. In fact the vi that contains the open file dialog can be run before the project containing the bug is even open.
I have to do this everytime I turn the PC on.
So, either
1) Can somewone suggest a fix for the original bug?
2) What is the easiest way to simulate the enter keypress when the open file dialog pops up
or
3) Can someone tell me what the open file dialog does under the hood that somehow causes the dll to work and can it be simulated in straight LabVIEW
I suspect that the dll itself is dodgy ( I have in the past talked to the supplier but not got very far, and I will try again but I would like a quick, temporary solution too). I'm guessing that the file dialog is making some kind of check on the file, and possibly registering its presence with the OS (winXP). I tried using the file/folder exists vi to see if checking the file like that worked but no luck.
Any help greatly appreciated.
Dave

Hi David
I am very conscious about thread hijacking but this sounded like my issue so I hope you dont mind me asking about your issue. I am hoping that you have a spectrometer from the same vendor as me and its not just me seeing an Error 1097 issue. My spectrometer is from a company called Stellarnet.
So far I have unable to get it to work with other VIs. There is one condition where I can get it to work but its no good for me.
Case 1
I open the VI in a fresh labview environment with no other VIs in memory. The code runs with no issue.
Case 2
Labview is not opened. I double click the spectrometer VI in windows explorer. The VI opens but it fails to run resulting in Error 1097. Personally, I dont see the difference between this and Case 1 above and yet it fails.
Case 3
If I already have other VI's in memory and try to load the spectrometer VI and run it fails with Error 1097. This case is the one that most important to me. I have a test executive that will load test VIs dynamically and I can't get this to work. Same problem Error 1097.
I wanted to share what I have seen with you and to let you know that maybe somebody else has the same issue. I am convinced its the DLL but the vendor dis-agreed saying it was LabVIEW. I couldn't convince him otherwise.
Thanks in advance
David

Error 7: File not found occurs in 8.2 from transition of 4.1. Specifying the file in file dialog returns error although file is in the directory.

Copied a program from 4.1 to 8.2 recently and receive an error 7: File not found at open file+.vi. The program is built so a file dialog will pop up and ask for the destination of the file. Eventhough there is a file in the specified directory, an error is returned. Running open file+.vi by itself returns no error with the same file designation. Any clues?

noviceak,
Welcome to the NI Discussion Forums.
I created a quick VI in LabVIEW 4.1 that displays a file dialog and then passes that file path to "Read Characters from File.vi" (which in turn calls Open File+.vi). I then opened this file in LabVIEW 8.2 and ran it successfully (see code screenshot below).
When you say there is a file in the specified directory are you using the file dialog to browse to the directory or to select the specific file? Open File+.vi expects the path to a file rather than a directory - that is C:\folder\file.txt rather than C:\folder. You might also want to create an indicator or probe to see what path is being passed to Open File+ to ensure it is what you expect.
I feel like I should also say that in the days (years) inbetween LabVIEW 4.1 and 8.2 the file operation VIs have changed significantly. While the old Open File+.vi still lives in vi.lib for compatibility purposes we no longer recommend using it for new applications.
I hope this helps and again, welcome to the community.
Regards,
Simon H
Applications Engineer
National Instruments
http://www.ni.com/support/
Message Edited by Simon H on 01-18-2007 08:01 PM
Message Edited by Simon H on 01-18-2007 08:03 PM
Attachments:
LV4 File Dialog.png ‏3 KB

How do I stop the error message coming up when I press cancel on file dialog

I am using the file dialog and if I press cancel an error box pops up with error 43 operation cancelld by user. Can we get rid of this, as it is bloody enoying, any ideas
cheers

Contrary to the rest of the nice folk here, I say do NOT turn off automatic error handling!
You will regret it if a day comes where you forgot to handle an error properly and you have a hard time determining its source.
If you truly want to ignore the error in this mode, you can wire the error out terminal into anything (even a wall). Once an error out terminal is wired, the error will not pop up automatically. This does not mean you should use this as a standard course of action. You should normally handle your errors properly.
Try to take over the world!

File Dialog Box often takes a long time to execute

Hi all
The Labview File Dialog Box Express VI sometimes takes 5 to 10 seconds to execute. On other occasions, it executes in a blink of an eye. Why is that so?
I have tried to use the older Open/Create/Replace File VI as suggested in one of the forum's posts...but it behaves exactly the same way. Another problem is the trimming of the filename, which has also been reported and has NOT YET been solved.
(By the way...Recently, I updated to LV 2012 SP2 by suggestion of the NI Update Manager, only to find out that I was not entitled to this SP (which apparently only includes bug fixes) and I will have to roll back to LV 2012. Still, in the evaluation version I can see that the bug is not fixed. Labview must have a lot of serious bugs for NI to ask for a paid bug fix, in which some bugs remain after having been reported a long time ago..well...)
What worries me now is that intermittent lag in the execution of the File Dialog (such a basic basic function of a program...). Anyone have any idea about this? The support menu said "Ask an engineer"...any of the NI engineers has any suggestion?
Regards
Helder
Attachments:
FileDialogTest.vi ‏26 KB

First of all: Thank you very much for the objective answer. I suppose that yor actually ARE a NI engineer, as I had hoped for.
lease find my comments above (helder---------------------)
helder wrote:
The Labview File Dialog Box Express VI sometimes takes 5 to 10 seconds to execute. On other occasions, it executes in a blink of an eye. Why is that so?
What worries me now is that intermittent lag in the execution of the File Dialog (such a basic basic function of a program...). Anyone have any idea about this?
The file dialog is provided by the OS, so if it is slow it is not LabVIEW's fault.
What kind of computer do you have? Is this a laptop that spins down the HD to save power? In this case it needs to wait for the HD to spin up. (You can change the windows power profile or you can spend more money and get an SSD).
Are you very low on memory?
Does your LabVIEW program waste 100% CPU in parallel doing nothing due to bad coding?
Are you pointing to a location that has millions of files?
Are you pointing to a network location?
helder:---------------------------------------
I understand that the File Dialog is provided by the OS. But I have other applications on my PC and this doesn't happen - just in Labview. Sorry! And sometimes it
doesn't happen. Every 10 times I open the File dialog Box, 5 times it takes long and 5 times it is immediate.
(I am not low on memory, my coding is not bad>-look at the VI I sent, it just contains the fragment which uses the File Dialog Box and it behaves the same way! I am pointing to the same location that the other applications point to, I am not pointing to a network location, the PC is not spinning the disk down, etc etc.)
But yes, I will try it on another PC
(There was another post on the forum on this issue, but can't seem to find it now, just find my own post )
I attach a video demo of what happens.
helder wrote:
Another problem is the trimming of the filename, which has also been reported and has NOT YET been solved.
What problem is that? Can you elaborate? There is a known bug in the windows dialog box that sometimes the pre-filled file names are shifted and not fully visible. This is a windows bug documented by Microsoft and LabVIEW has no control over it. It is not NIs job to fix OS problems.
helder:-------------------------------------------
Of course you can't fix the OS.
If it is a windows bug, we will have to live with it.
A previous post on your forum did not provide me with that information (http://forums.ni.com/t5/LabVIEW/File-dialog-trimming-the-default-name/td-p/2189874). The fact that it is a windows bug was not mentioned there.
helder wrote:
Hi all
(By the way...Recently, I updated to LV 2012 SP2 by suggestion of the NI Update Manager, only to find out that I was not entitled to this SP (which apparently only includes bug fixes) and I will have to roll back to LV 2012. Still, in the evaluation version I can see that the bug is not fixed.
Patches are included, service packs are not included. I think this is well documented. Most users are on SSP, this way you are always entitled to the newest version.
As with anything else, software has bugs. It is impossible to test a huge, complex system like LabVIEW under all scenarios. The possible number of combinations of hardware and other installed software on any particular computer probably exceeds the number of atoms in the universe. It is actually amazing how few bugs there are and how well it works. What "bug" are you talking about? Bugs are prioritized according to rules. Critical bugs are typically fixed very quickly. A cosmetic issue that only affects you and nobody else will take longer or might not even get fixed. Are you talking about a confirmed bug that could be reproduced by NI? Do you have a CAR#?
helder:----------------------------------------
I was referring to the file-name-shifting-cosmetic-bug that the October-2012 post had indicated. But if it is a Windows-bug, NI does not have any responsibility, of
course.
Regarding the bugs, of course they are unavoidable.
helder wrote:
Labview must have a lot of serious bugs for NI to ask for a paid bug fix, in which some bugs remain after having been reported a long time ago..well...)
That sentence makes no sense! Why would the number of serious bugs depend on the cost of upgrading?? You are just rambling here....
In an ideal world, NI would have an unlimited number of programmers that can work 24/7 to immediately fix any discovered bug. This would only be possible if all users are willing to pay an unlimited amount of money for the software. As I mentioned, bug fixes are free in the form of patches, and they come out regularly. Service packs include new features and are not free.
helder:---------------------------------------
"....include new features"..????
---->>From http://www.ni.com/labview/release-details/
"LabVIEW 2012 Service Pack 1 is an exclusive update to LabVIEW 2012 for NI Standard Service Program (SSP) customers. There are no new product features introduced in service pack releases; instead, these releases provide bug fixes and improved stability for LabVIEW 2012. For a list of these bug fixes, click here."
No new features, just bug fixes!"
Moreover: If it isn't free, it shouldn' have let me update if I am not a SSP costumer.
Now I have a 45 days evaluation version. After that, I have to uninstall and reinstall everything.That takes some time and effort.
If there is a more direct way of rolling back t the previous version, please let me know.
Thank you

How to create a custom file dialog box/vi (win)??

Hello,
I'd like to create a custom file dialog box to handle the reading of my tdms files. Basicly I want to extend the existing file select dialog box with a graphical preview of the data in the selected file. I know I can create all the logic for file selection by hand and use a list box to display the filelist, but I would rather prefer to somehow use the existing windows controls. So is it possible to get the windows file selector on the front panel of a vi and react to the user selection? If so, is there any example available on how to do this? Any other options? I'm using labview 8.2
thanks for your input!
klaus

Klaus,
I wouldn't know that Microsoft provides access to the controls that Explorer and file dialog consist of.
There might be a different and more powerful solution though. The
WINDOWS Explorer / file dialog have a plugin API that allows you to
associate your own application for thumbnail creation with a particular
file extension. That way, TDMS thumbnails will show in any instance of
Explorer and
File Dialog without you having to make your own dialog. Basically, you
would need to compile the VI that creates the thumbnail into a
LabVIEW-built DLL and then wrap this DLL with some C++ boilerplate code
that Microsoft provides. You might want to have a look at the bottom of
this article to get an idea of how the whole thing works:
http://msdn.microsoft.com/msdnmag/issues/0600/w2kui2/default.aspx.
Hope that helps,
Herbert

How to open a save file dialog box in form

hi
all
I have prob in form desing , i have open the save file dialog box , how to open a save dialog box
and path of the select file to save in disk
help
thx

hi
user this query when-button-pressed trigger
:txtfile := GET_FILE_NAME(directory_name =>'d:\ali_raza\backup\', file_filter=> 'DMP Files (*.dmp)|*.dmp|');
Rizwan

Some qt only programs are crashing opening the "Open File" dialog

Hello Archers,
I'm having some trouble to find out what's crausing the crashes, so i can properly fill a bug report upstream.
Here is the issue:
* After an upgrade from glibc 2.13-5 to glibc 2.14-4, some qt-only apps are crashing when i open the "Open File" dialog. This only happens when using specific KDE 4.6.4 or KDE 4.6.5 styles, like Oxygen and QtCurve.
* Before i upgrade KDE from 4.6.4 to 4.6.5, i downgraded glibc and its dependencies to glibc 2.13-5 and the bug was gone. After upgrading KDE to 4.6.5, i didn't try the downgrade again because KDE 4.6.5 requires glibc 2.14 and the process of downgrading become unsustainable.
* I tried removing the crashing apps data from my home directory and the crash still exists. I also tried to create a new user and start the apps from that new environment and the apps crashes, so the bug is not user-specific.
* I tried replacing the binary nvidia driver with xf86-video-nouveau but the issue persists.
* The apps crashing (and not applying the kde theme) are the following:
=> opera 11.50
When opening the "Open File" dialog, it crashes with the following message:
------------- begin ---------------------------------
$ opera --sync
(operapluginwrapper:2349): Gdk-WARNING **: GdkWindow 0x7400034 unexpectedly destroyed
(operapluginwrapper:2349): Gdk-WARNING **: GdkWindow 0x7400033 unexpectedly destroyed
(operapluginwrapper:2349): Gdk-WARNING **: GdkWindow 0x7400032 unexpectedly destroyed
(operapluginwrapper:2349): Gdk-WARNING **: GdkWindow 0x740001c unexpectedly destroyed
The program 'operapluginwrapper' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 547 error_code 3 request_code 18 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
------------- end ---------------------------------
=> vlc 1.1.10
When opening the "Open Directory" dialog, it crashes with the following message:
------------- begin ---------------------------------
$ vlc
VLC media player 1.1.10 The Luggage (revision exported)
Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS")
Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE")
[0x9884a7c] main interface error: no suitable interface module
[0x97e28fc] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Blocked: call to setlocale(6, "")
Blocked: call to setlocale(6, "")
Segmentation fault
------------- end ---------------------------------
* Using other qt-only apps, like qmmp or UMPlayer the bug doesn't occur.
So, what do you thing of this? Am i the only one with this issue? I already reported the bug report on https://bugs.archlinux.org/task/24991 and https://bugs.opera.com/wizard/, but since i latter found out that this is not opera specific, i don't know where to fill the report.
Thanks in advance.
Last edited by eldarion (2011-07-09 15:15:13)

kachelaqa wrote:
eldarion wrote:kachelaqa, can you please confirm if it happens with vlc or opera too? Thanks for helping.
i had to install vlc and opera to test - but i'm afraid i don't get the errors you are seeing.
so far, qt designer is the only application i've found that crashes when opening file dialogs.
Ok, thanks for helping.

After clicking "Save" in "Save as" file dialog, the dialog disappears but no download is started. Is this a Windows 7 64 bit issue? It works fine in Windows XP.

I am trying to download the iTunes installer for Windows 7 64 bit.
I have "Always ask me where to save files" checked in Firefox's download options.
Steps to reproduce the problem:
1) In the iTunes download page I click the "Download now" link and Firefox shows me a "Opening iTunes64Setup.exe" dialog with a "Save File" button.
2) I click the "Save File" button. Sometimes the dialog disappears but nothing else happens. Other times I get the Windows 7 "Save as" dialog.
3) I click the "Save" button in the save file dialog (I'm using the default user documents folder). The dialog disappears and nothing happens.
If I uncheck "Always ask me where to save files" then the download works fine.
I also have a Windows XP 32 bit with the same configuration where everything works fine which makes me think that this problem only happens in Windows 7 or in the 64 bit version.

It is possible that anti-virus software is corrupting downloaded files or is otherwise interfering with downloading files.
Try to disable the real-time (live) scanning of files in your anti-virus software temporarily to see if that makes downloading work.
See:
*http://kb.mozillazine.org/Unable_to_save_or_download_files
*browser.download.manager.scanWhenDone

File Dialog

Similar Messages

Maybe you are looking for