Just a file dialog ?

hi, how can i select a directory using "file dialog" function in "windowsNT"
environment ?
non of the options allows to select a directory, just open it.
the file dialog for w98 has a button to select the directory ,"select
current directory ".
but for windowsNT, it doesn't exist
thanx.
ozan...
ps : please look at attach.
[Attachment file dialog.zip, see below]
[See first answer for additional information]

to point out the obvious, you could have the user select a file int he
directory, then strip the path...
not beuatiful, but functional
torleiv
Ozan ONER wrote:
>
> Robert Luftensteiner wrote in message
> news:385794e8$0$[email protected]..
> > Ozan ONER schrieb in im Newsbeitrag:
> > <[email protected]>...
> > > hi, how can i select a directory using "file dialog" function in
> > "windowsNT"
> > > environment ?
> > > non of the options allows to select a directory, just open it.
> > > the file dialog for w98 has a button to select the directory ,"select
> > > current directory ".
> > > but for windowsNT, it doesn't exist
> > > thanx.
> > > ozan...
> > >
> >
> ps : please look at attach.
> >
> > Hi!
> >
> > If you only want to select a directory
> > don't use Open/Create/Replace File.vi .
> > Try the "File Dialog" Advanced File Function.
> > (select mode = 3)
> >
>
> hi robert,
>
> as i sad earlier, i am trying to select a directory using "File Dialog" in
> advanced functions in the winNT.
> and the select mode ==3;
>
> i am not using a function related to file opening or stg else.
>
> therefore, i am asking again, how can i select a directory? i think, it is
> impossible
> i dont want to write a new file dialog function for winNT to select a
> directory.
>
> the problem is related with winNT, i think.
>
> thanx.
> ozan...

Similar Messages

  • Images just a dot in local files dialog box

    My image files are just a dot in the local files dialog box
    and I can't select them. It's just the little thumbnail. All the
    following info shows fine. The html files show up fine.

    Hi Alan,
    store the path\filename in the 1st argument:
    FileNameVal = Application.GetSaveAsFilename("C:\*.xlsm", "Excel Macro-Enabled Workbook (*.xlsm), *.xlsm")
    Andreas.

  • 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!

  • 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

  • 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-trimmi​ng-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

  • File dialog box: how get full path and filename (firefox 3.0 problem)

    Hi,
    I have a smilar problem then discussed in this thread: file dialog box: how get  full path and filename
    Now this solution doesn't seem to work in firefox 3.0,I only get the filename but not the full path.
    I have tried to solve this problem by adding *"netscape.security.PrivilegeManager.enablePrivilege("UniversalFileRead");"* in a javacript function but that doesn't do the trick
    Although when i tested it local it does work.
    Any idees how to solve this?
    Best Regards
    Stijn

    Actually, that is strange and scarry. With 20% of the browser market share they decide to behave like Microsoft did in the past - they want to decide what users need and what they do not need. With 3.0 I have a real problem with some of my applications. They are all tested in IE6, IE7, FF2.0 and they all work the same way (they even work with Opera and Safari). Now, I will for sure not go there and make it work for 3.0, just because 2 out of 200 users use FF3.0. Up to now I have always recomended FF as the best browser. 3.0 causes my opinion to change completely. Competition is always good but it is a question if it is good if we have 20 different browsers out there with equal market shares.
    Denes Kubicek
    http://deneskubicek.blogspot.com/
    http://www.opal-consulting.de/training
    http://apex.oracle.com/pls/otn/f?p=31517:1
    -------------------------------------------------------------------

  • Finder in Save file dialog Safari crash

    Ever since I upgraded to Snow Leopard at launch, Safari 4 doesn't seem to like me searching in the save file dialog box. It doesn't seem to matter whether or not I actually save the file, and I made a screen recording to show what happens here:
    http://www.youtube.com/watch?v=YFKkPI2vGr8
    I've reset Safari, and I repaired my disk permissions after loading up Snow Leopard. What gives? This is really annoying when I want to get to a folder fast, and dragging and dropping image files to folders seems to cause them to open in different Preview windows (or not even open at all).
    Any help would be much appreciated. This is seriously making me consider going back to Firefox or just going with Chrome - this crash doesn't happen with either of them!

    The problems are caused by third party input managers/enhancers that have not yet been updated by their developers to comply with the standards used by Safari 3.2.1. and/or Safari 4.
    In your case these are:
    com.zang.RegexKit 0.6.0 (0.6.0) <71374A4A-3B24-4759-E994-AB9E135345CB> /Library/InputManagers/Safari AdBlock/Safari AdBlock Loader.bundle/Contents/PlugIns/Safari AdBlock.bundle/Contents/MacOS/../Frameworks/RegexKit.framework/Versions/A/Regex Kit
    You fill find them in one or either of these folders:
    Home/Library/Input Managers
    Hard Disk/library/Input Managers
    Hard Disk/Library/Application Support
    although the exact location is indicated in your crash report as quoted above - look under 'Binary Images'.
    Close Safari and delete them, then restart Safari and it should be working normally. Alternatively drag them to the desktop and restart Safari. then add them back one at a time, restarting Safari every time, until you find the one (or more) causing the crash.
    Check with the developers of the plug-ins in question for updates that are Safari 4 compliant.

  • File Dialog not appearing in web form after Note:74140.1

    Hello, I have implemented the source given in Note:74140.1 to replace the get_file_name function that displays the file dialog box. However I still am not able to see the dialog that the JavaBean should display. I am relativly new at linking JavaBeans with forms, so there might be something that I am missing.
    I have created the class files for FDialog and FDialogPJC and put them in an ear file. I have also modified the fiels server.xml and default-web-site.xml to include the ear file. The respective code for a button has been added to the button trigger in the form, as well as the code for the JavaBean.
    So far this has been unsuccessful. If you have a suggestion, your help is much appreciated.
    Justin.

    the problem is that when I type JDialogPJC in the implementation class property of the java bean when working in JDeveloper, it cannot locate the java class file JDialogPJC.class. This happens when I put both the JDialogPJC and JDialog classes in the jar file and put the jar file in the forms90/java directory.
    However, if I just put both class files (not contained in a jar file) in the forms90/java directory, and I specify the JDialogPJC in the implementation class property of the java bean, it works fine.
    I would like to be able to use the jar file instead of a whole load of class files sitting in the directory.

  • Folder appears in Windows Explorer, but not in the Open File dialog

    Hello,
    I hope this is the right place to post this. If not, please let me know where is.
    A friend just showed me a weird problem he is having with his computer. He is using Windows 7 pro, and has a folder under My Documents, in which he keeps his work files. He emails these files using Gmail, which he accesses via Internet Explorer.
    All worked fine until a few days ago, when he noticed that when he clicked the link in Gmail to attach a file, his folder wasn't listed in the Open File dialog. He looked in Windows Explorer, and could see the folder OK. I tried opening Word and using the Open
    File dialog there, and the folder wasn't visible.
    If he clicks in the address bar, and adds the folder name to the path, it opens the folder, but shows it as empty. I actually has two subfolders. If he adds the name of a subfolder, then the Open File dialog shows the files in that folder.
    I checked the permissions on the folder, and couldn't see anything odd. What I don't understand is how the folder can be visible in Windows Explorer, and not in the Open File dialog.
    Anyone any ideas? Thanks
    FREE custom controls for Lightswitch! A collection of useful controls for Lightswitch developers.
    Download from the Visual Studio Gallery.
    If you're really bored, you could read about my experiments with .NET and some of Microsoft's newer technologies at
    http://dotnetwhatnot.pixata.co.uk/

    I can confirm - I'm having the exact same problem.
    When I try to lookup or save a file from an IE file dialog some folders do not show up. I can type the folder name into the directory field and it then goes there, but this assumes you know the directory name and it's a PITB.
    Firefox can browse to the directory directly.
    It would be interesting if anyone else found a fix for this - I'll post here again if I find out more somewhere else, but there are not too many threads out there as far as I have found for now.
    Found a solution over at answers at Microsoft dot com. (can post links here yet - will update once I can)
    In short: There's a fast fix for this issue by resetting a hidden flag that IE sets for some folders. I believe this part of the "protected mode" feature, though I can't confirm and also have no idea how this would protect me from any intruders,
    if only (unimportant) subfolders are protected ...
    Anyway - if you know the name of the missing folder (e.g. from browsing the directories form windows explorer): in the parent directory that has the folder missing do a Search (in box at top right) for the missing
    folder name. In my case the hidden folder shows up in the search - now right click -> Properties -> clear hidden flag. Note: this "hidden" flag is independent of the flags set in windows explorer - that's why you have trouble going there with IE and not
    the file explorer from the desktop.

  • File dialog in Forms 9i

    Although I may find the get_file_name function in the online help just like I know it from Forms 6.0 (and it worked well with that one in client-server), at runtime this wonderful function doesn't seem to do anything.
    Furthermore, there's no more d2kwutil.pll, nor d2kwutil.dll.
    How do I then get a file dialog from Forms 9i?

    The function does not wrok when web deployed (9i or 6i) you will have to write a JavaBean to do this (see the FileUpload sample in the demos which actually contains this code)

  • How do I get back to the newest file dialog box style in LabVIEW?

    I have LabVIEW 7.1 and LabVIEW 6.0.2 installed on the same machine.  When I doubleclick a .vi file it tries to open in LV602.  Of course, if it is a LV71 VI I get an error and it doesn't open.  Then I run LV71 and load the desired VI--in this case by using the Open arrow to find it in the "recently opened" list.  Now, I've made this mistake before, especially when I don't remember whether I used LV602 or LV71 to create the VI, and nothing bad has happened.
    But this time something undesirable did happen:  all Open File dialog boxes are of the old funky style.  How do I get the file dialog boxes back that I've grown used to seeing when I use LV71?
    CLUES:
    1.  I get the old style dialog box even when I try to open a VI--not just when a running VI invokes it.
    2.  The built version of the VI brings up the correct, new style, file dialog box--unlike the development environment.
    I haven't found any settings in the options area that would appear to affect the file dialog box style.  Has anyone ever seen anything like this?

    RudyRed wrote:
    Thanks for the response,
    Warren.  I think all my problems with LV versions coexisting
    peacefully have been related to NIDAQ--and I think the workaround (for
    supporting the different levels of LV DAQ VIs--see my response to
    Benoit, above) shows that it is not NECESSARY for NI to orphan old LV
    versions' DAQ functionality on the development computer, though it is
    still painful to be able to have only one version of NIDAQ available on
    a given target computer.  It's probably a marketting decision
    meant to encourage users to stay on the straight-and-narrow upgrade
    path.
    NI-DAQ has usually been working fine in
    several different installed LabVIEW versions on my computer. What is
    important is the order of installation. Start first with the lowest
    LabVIEW version and install the latest NI-DAQ that supports that
    LabVIEW version. Then go to the next LabVIEW version and install again
    the latest NI-DAQ version that supported this LabVIEW version and so
    on. I'm regularly working with 6.1 up to 7.1 and starting with 8.0
    slowly and haven't had real show stoppers yet.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Event handling in file dialog box

    I want to make the test bed for testing event-based stand alone application.
    I can transfer some values to filename or others.
    However, How can I handle (Value signaling) the Okay or Cancel button in file dialog box popped up from my test bed?
    What is the reference for the dialog box? 
    Of course, I can transfer the file name explicitly but don't want to change current application.
    Labmaster.

    Are you talking about the file dialog express vi? The vi returns a boolean for canceled. It will also return error 43 which is normal for canceled by user. You can not register an event on the express vi. Just look at the outputs and generate a user event based on that. Look at the example finder for user defined events as Gak pointed out.
    =====================
    LabVIEW 2012

  • Open file dialog hangs

    I have some raw video files dumped from a Sony HD camera. The files are in some MPEG format (VLC just reports mpegv, mpega), the resolution is 1440x1088, and they are about 10 GB for 1 hour of video. My Quicktime wont play the video, but VLC plays it fine.
    When I try to "Import video from file..." in iMovie '08, and navigate to the folder where the files are, the open file dialog hangs and iMovie beachballs - so far I have only had patience for 30 min, then a Force Quit is the only option.
    Edit: OK, so it took 45 min then I could interact. The .mpeg is greyed out and as soon as I touch anything, iMovie beachballs again.
    Any idea of the reason for this and how to circumvent it? Is iMovie trying to extract info from the files beforehand? Is it due to the file size (10 GB)?
    Presently, I am trying to transcode the files using VLC, but I am having some trouble finding the best settings so not to loose too much quality, get rid of the interlace, etc. Any pointers on how to optimize setting for processing afterwards in iMovie HD and/or '08 are appreciated.
    Message was edited by: Dalle

    I don't understand how iMovie works with those thumbnails.
    I imported some DV footage from an old iMovie HD, 2 clips. The files generated by iMovie'08 looks like this:
    clip1.dv is 768x567 and is 118 MB on disk (although Quicktime reports 238 MB) and clip2.dv is 768x567 and 53 MB on disk. iMovie'08 creates a folder iMovie Cache with a file Cache.mov, 720x576, 12 kB on disk. In the folder iMovie Thumbnails is the file clip01.mov, 160x90, 10 MB on disk and clip02.mov, 160x90, 4.5 MB on disk. In the subfolder iMovie Cache is the file Cache.mov, 160x90, 16 kB.
    Now, the HD footage I had to process differently. In order to get it into iMovie'08, I used VisualHub to convert the 1 hour video at 1440x1088, 10 GB on disk, file HD.mpeg to AppleTV format (720p) as HD.mp4, now 1280x720, 1.5 GB. I import this in iMovie, goes fine, takes a minute or so. Then iMovie starts creating its thumbnails. It took 4 hours 9 minutes!
    The clip is in there as one 1 hour clip. The file structure is as follows: HD.mp4 is 1280x720, 1.5 GB on disk. In the folder iMovie Cache is cache.mov, 1280x720, 2.1 MB. In the folder iMovie Thumbnails is HD.mov, 160x90, 980 MB on disk - ie. two-thirds the size of the original file, in 1/64 the resolution! In the subfolder iMovie Cache is cache.mov, 160x90, 590 kB.
    Skimming is hardly possible on the HD clip, especially moving the cursor backwards, and it is hard to trim selections. It plays fine, though. For the DV clips skimming it works fine.
    Any ideas what is going on here, and how to work around? Is the inefficiency due to the very large clip? I tried to trim of a 2 min clip from the original file and put it through the same conversion, but the result was more or less the same, skimming-wise - very inefficient.

  • 'Open a File' dialog box doesn't show 'Favorites'

    InDesign CS6, Windows 7:
    File/Open gives me this:
    Notice there are no 'Favorites' on the left.  I have to 'browse' for my file each time.  I have a ton of files on the network, and it takes several clicks to get to them.  Annoying when I'm opening several files a day.  The 'Recent Places' isn't too helpful here either.
    Now look at what happens in InDesign CC, Windows 7 with a File/Open:
    Look at all the 'Favorites' and easy browsing on the left side.  Why are the 'Open a File' dialog boxes so different in CS6 and CC?  I want the CS6 'Open' dialog to be just like the CC one.  (I prefer to use CS6, CC is buggy on my system.)

    Not helpful.
    What it is... is cumbersome and un-necessary.  Every other program in Windows  (even Word Pad) opens with the 'standard'  dialog with Favorites on the left.  Why did Adobe program it differently?  There has to be a fix in Preferences or something...

Maybe you are looking for