File browse functionality for all files within a directory

I have an app where you use file browse to select a file on the file system. Then, I parse the file name to determine other attribution to record in database, which may result in more user interaction before creating the database record.
So, currently users can do this one file at a time. Anything available to let me loop through all files within a user-specified directory?
Thanks,
Steve

I have an app where you use file browse to select a file on the file system. Then, I parse the file name to determine other attribution to record in database, which may result in more user interaction before creating the database record.
So, currently users can do this one file at a time. Anything available to let me loop through all files within a user-specified directory?
Thanks,
Steve

Similar Messages

  • How to make a category required for all files created within a folder

    I've defined a category. It has attributes which have been flagged as required.
    When I view the properies of a particular workspace (library), the category is shown as available to the workspace. However, the category is not shown as required. And the "required" checkbox is not clickable.
    So .. how, from the OCS DHTML applet, do I make a particular category a required category for all files in a folder?

    Perhaps the Category Attribute is not marked as "configurable" when it was created. You can check this by "switching into Admin Mode" and drilling down the Categories using "Manage Categories" link. Check if the category attribute is marked as configurable or not.
    Ravikiran

  • "Date Modified" for all files being changed if "Automatically write to XMP" is on

    Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
    When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
    This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
    If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
    Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
    Is anyone else seeing this? Any ideas would be greatly appreciated!
    -- David
    diff Exif5609_original Exif5609_update
    2c2
    < FileName: DSC_5609_original.JPG
    > FileName: DSC_5609_update.JPG
    5,6c5,6
    < FileModifyDate: 2009:11:27 21:32:54-08:00
    < FilePermissions: rwxr-xr-x
    > FileModifyDate: 2011:08:07 22:06:47-07:00
    > FilePermissions: rw-r--r--
    27a28,29
    > ShutterSpeedValue: 1/200
    > ApertureValue: 7.1
    55d56
    < SerialNumber: 3209521
    75d75
    < Lens: 18-200mm f/3.5-5.6
    185,188d184
    < UserComment:
    < SubSecTime: 00
    < SubSecTimeOriginal: 00
    < SubSecTimeDigitized: 00
    211a208,299
    > XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
    > CreatorTool: Ver.1.00
    > MetadataDate: 2011:08:07 22:06:47-07:00
    > SerialNumber: 3209521
    > LensInfo: 18-200mm f/3.5-5.6
    > Lens: 18.0-200.0 mm f/3.5-5.6
    > ImageNumber: 26634
    > RawFileName: DSC_5609.JPG
    > SavedSettingsName: Import
    > SavedSettingsType: Snapshot
    > SavedSettingsParametersVersion: 6.4.1
    > SavedSettingsParametersProcessVersion: 5.0
    > SavedSettingsParametersWhiteBalance: As Shot
    > SavedSettingsParametersIncrementalTemperature: 0
    > SavedSettingsParametersIncrementalTint: 0
    > SavedSettingsParametersExposure: 0.00
    > SavedSettingsParametersShadows: 0
    > SavedSettingsParametersBrightness: 0
    > SavedSettingsParametersContrast: 0
    > SavedSettingsParametersSaturation: 0
    > SavedSettingsParametersSharpness: 0
    > SavedSettingsParametersLuminanceSmoothing: 0
    > SavedSettingsParametersColorNoiseReduction: 0
    > SavedSettingsParametersChromaticAberrationR: 0
    > SavedSettingsParametersChromaticAberrationB: 0
    > SavedSettingsParametersVignetteAmount: 0
    > SavedSettingsParametersShadowTint: 0
    > SavedSettingsParametersRedHue: 0
    > SavedSettingsParametersRedSaturation: 0
    > SavedSettingsParametersGreenHue: 0
    > SavedSettingsParametersGreenSaturation: 0
    > SavedSettingsParametersBlueHue: 0
    > SavedSettingsParametersBlueSaturation: 0
    > SavedSettingsParametersFillLight: 0
    > SavedSettingsParametersVibrance: 0
    > SavedSettingsParametersHighlightRecovery: 0
    > SavedSettingsParametersClarity: 0
    > SavedSettingsParametersDefringe: 0
    > SavedSettingsParametersHueAdjustmentRed: 0
    > SavedSettingsParametersHueAdjustmentOrange: 0
    > SavedSettingsParametersHueAdjustmentYellow: 0
    > SavedSettingsParametersHueAdjustmentGreen: 0
    > SavedSettingsParametersHueAdjustmentAqua: 0
    > SavedSettingsParametersHueAdjustmentBlue: 0
    > SavedSettingsParametersHueAdjustmentPurple: 0
    > SavedSettingsParametersHueAdjustmentMagenta: 0
    > SavedSettingsParametersSaturationAdjustmentRed: 0
    > SavedSettingsParametersSaturationAdjustmentOrange: 0
    > SavedSettingsParametersSaturationAdjustmentYellow: 0
    > SavedSettingsParametersSaturationAdjustmentGreen: 0
    > SavedSettingsParametersSaturationAdjustmentAqua: 0
    > SavedSettingsParametersSaturationAdjustmentBlue: 0
    > SavedSettingsParametersSaturationAdjustmentPurple: 0
    > SavedSettingsParametersSaturationAdjustmentMagenta: 0
    > SavedSettingsParametersLuminanceAdjustmentRed: 0
    > SavedSettingsParametersLuminanceAdjustmentOrange: 0
    > SavedSettingsParametersLuminanceAdjustmentYellow: 0
    > SavedSettingsParametersLuminanceAdjustmentGreen: 0
    > SavedSettingsParametersLuminanceAdjustmentAqua: 0
    > SavedSettingsParametersLuminanceAdjustmentBlue: 0
    > SavedSettingsParametersLuminanceAdjustmentPurple: 0
    > SavedSettingsParametersLuminanceAdjustmentMagenta: 0
    > SavedSettingsParametersSplitToningShadowHue: 0
    > SavedSettingsParametersSplitToningShadowSaturation: 0
    > SavedSettingsParametersSplitToningHighlightHue: 0
    > SavedSettingsParametersSplitToningHighlightSaturation: 0
    > SavedSettingsParametersSplitToningBalance: 0
    > SavedSettingsParametersParametricShadows: 0
    > SavedSettingsParametersParametricDarks: 0
    > SavedSettingsParametersParametricLights: 0
    > SavedSettingsParametersParametricHighlights: 0
    > SavedSettingsParametersParametricShadowSplit: 25
    > SavedSettingsParametersParametricMidtoneSplit: 50
    > SavedSettingsParametersParametricHighlightSplit: 75
    > SavedSettingsParametersSharpenRadius: +1.0
    > SavedSettingsParametersSharpenDetail: 25
    > SavedSettingsParametersSharpenEdgeMasking: 0
    > SavedSettingsParametersPostCropVignetteAmount: 0
    > SavedSettingsParametersGrainAmount: 0
    > SavedSettingsParametersLensProfileEnable: 0
    > SavedSettingsParametersLensManualDistortionAmount: 0
    > SavedSettingsParametersPerspectiveVertical: 0
    > SavedSettingsParametersPerspectiveHorizontal: 0
    > SavedSettingsParametersPerspectiveRotate: 0.0
    > SavedSettingsParametersPerspectiveScale: 100
    > SavedSettingsParametersConvertToGrayscale: False
    > SavedSettingsParametersToneCurveName: Linear
    > SavedSettingsParametersCameraProfile: Embedded
    > SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
    > SavedSettingsParametersLensProfileSetup: LensDefaults
    > SavedSettingsParametersToneCurve: 0, 0, 255, 255
    > IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
    228,230d315
    < SubSecCreateDate: 2009:11:27 21:32:54.00
    < SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
    < SubSecModifyDate: 2009:11:27 21:32:54.00
    http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

    clvrmnky wrote:
    davidpope007 wrote:
    Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
    Yuck. As a former software engineer, this is very bad software engineering.
    It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
    Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
    Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
    The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
    As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
    [Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
    From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
    But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
    The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
    Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
    You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
    * Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
    * However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
    * Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
    * Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
    * A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
    * So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
    * Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
    Here's a screenshot from Finder of what I see everytime I look at this folder:
    * So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
    * What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
    * Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
    I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
    You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
    I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
    I am really at a loss as to what to do and would welcome your suggestions.
    Thanks again and kind regards,
    -- David

  • Can't export as Html (Waiting for all files to be ready...)

    Made a bunch of updates last night to a client site.  Everything looks great except I can't export as Html. Had my sister try to export on her computer and we both get to 87%, then it permanently stalls, saying "Waiting for all files to be ready" (See screenshots). We've ensured that no files are open or being previewed. We've rebooted and tried saving to a different location, all with no change, we still get to the 87% mark and stop. Please help. I have a client waiting for this site update.
    Details:
    Windows 7
    Sony Vaio
    Muse Version - 4.1 Build 8 *see screenshot
    ****Update:
    I can preview the entire site in a browser as well as preview each page individually, but cannot finish a html export past 87%.

    Odd are if you wait long enough, potentially a few hours, it will complete.
    This huge performance hit sounds exactly like a bug that's fixed for the Muse CC 5.0 release due out next week. Sorry for the inconvenience.

  • File Browser capabilities for V1.6

    Hello,<br>
    I am using a File Browser to add/upload files to my reports just like the How To: Build File Upload/Download App. The reports are working fine and so are the files until I want to edit/update individual records. When the FETCH ROW is executed, all fields for that record are returned except for the File Browse field. My question is, can the File Browser be used to recall the file that was attached, so that the user can decide if they would like to edit/update that record with another file?
    <br>
    <br>
    Right now I have all the records fields returning data except for File Browser field that remains blank. When I click it, select a different file, then save, all the other fields are updated except for this one that continues to display the original attached file.
    <br>
    <br>
    The File Browser's setting are:<br>
    HTML Form Element Attributes:onchange="htmldb_item_change(this)"<br>
    Source Used:Always, replacing any existing value in session state<br>
    Source Type:Database Column<br>
    Maintain Session State:Per Session<br>
    Source value or expression:FILE_NAME<br><br>
    Thanks,<br>
    Leo

    Try this parameters....<PARAM NAME=cache_version VALUE=0.0.0.1><PARAM NAME=cache_option VALUE=Plugin><PARAM NAME=cache_archive VALUE=AnalyzerClient.jar>Comment first the ARCHIVE VALUE line parameter.Use this link for more information...http://java.sun.com/j2se/1.3/docs/guide/misc/appletcaching.html

  • It should be possible to set default behavior for all file types

    It should be possible to set a default action for all file types. I'm so tired of having to manually sit and say "save this file" because Firefail always defaults to "open with" and has disabled the "Do this automatically for files like this from now on."
    And spare me the zealotry religious excuses for why its the fault of websites and not Firefail
    ''edited to remove swearing''

    I do want users to have full control to be able to set any folder view they want by using Apply to Folders; I just want to set the initial/default view to Detail because that matches what the majority of my users want.
    That is, what registry setting changes when I go to a picture folder, change the view to Detail, and click Apply to Folders? Having done that, I still retain the ability to change it to some other view and apply that to folders. But what registry setting
    represents the change I just made when applying Detail view to all Picture folders.?
    This settings is simple via GUI, but it is related a lot of registry keys, I made a test in my machine, capture the "Apply to Folders" process using Regshot tool (this is a small tool which can compare the regsitry changes after you change some
    settings), and this is the result:
    this is part of the registry changes, a plenty of registry keys and values need to be changed. hard to list them here. if you have interests, I recommend the tool Regshot, it can help you capture the regsitry changes.
    NOTE: Please Note: The third-party product discussed here is manufactured by a company that is
    independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's
    performance or reliability.
    Yolanda Zhu
    TechNet Community Support

  • Using an * for all file extensions in a class selection parser

    Using iFS 1.1.9....
    I have successfully gotten a custom document class created using
    xml. I have used the following code to set up the parser, etc.
    If I use a specific file extension like txt the parser will
    upload the file as my custom class. However, if I use * for all
    file extensions the parser uploads all files as Document class.
    Here is what I am using:
    <?xml version='1.0' standalone = 'yes'?>
    <!--RegisterQualParser-->
    <PropertyBundle>
    <Update
    Reftype='ValueDefault'>ParserLookupbyfileExtension</Update>
    <Properties>
    <Property Action = 'add'>
    <Name>*</Name>
    <Value Datatyupe = 'String'>
    oracle.ifs.beans.parsers.ClassSelectionParser
    </Value>
    </Property>
    </Properties>
    </Propertybundle>
    When the above is uploaded I can go into iFS Manager and see
    that the parser has been registered with * as the file extention.
    I then upload this:
    <?xml version='1.0' standalone = 'yes'?>
    <!--RegisterCustomClass-->
    <PropertyBundle>
    <Update
    Reftype='ValueDefault'>IFS.PARSER.ObjectTypeLookpByFileExtension
    </Update>
    <Properties>
    <Property Action = 'add'>
    <Name>*</Name>
    <Value Datatype='String'>QualDocument</Value>
    </Property>
    </Properties>
    </PropertyBundle>
    If I have txt or some other extension for the Name in place of
    the * and upload a document it will put the class as
    QualDocument. If I have the * it defaults to Document.
    Is there a way to have the parser make all uploaded documents
    QualDocument instead of Document without doing this for each and
    every possible file extension?
    Thanks.

    Using iFS 1.1.9....
    I have successfully gotten a custom document class created using
    xml. I have used the following code to set up the parser, etc.
    If I use a specific file extension like txt the parser will
    upload the file as my custom class. However, if I use * for all
    file extensions the parser uploads all files as Document class.
    Here is what I am using:
    <?xml version='1.0' standalone = 'yes'?>
    <!--RegisterQualParser-->
    <PropertyBundle>
    <Update
    Reftype='ValueDefault'>ParserLookupbyfileExtension</Update>
    <Properties>
    <Property Action = 'add'>
    <Name>*</Name>
    <Value Datatyupe = 'String'>
    oracle.ifs.beans.parsers.ClassSelectionParser
    </Value>
    </Property>
    </Properties>
    </Propertybundle>
    When the above is uploaded I can go into iFS Manager and see
    that the parser has been registered with * as the file extention.
    I then upload this:
    <?xml version='1.0' standalone = 'yes'?>
    <!--RegisterCustomClass-->
    <PropertyBundle>
    <Update
    Reftype='ValueDefault'>IFS.PARSER.ObjectTypeLookpByFileExtension
    </Update>
    <Properties>
    <Property Action = 'add'>
    <Name>*</Name>
    <Value Datatype='String'>QualDocument</Value>
    </Property>
    </Properties>
    </PropertyBundle>
    If I have txt or some other extension for the Name in place of
    the * and upload a document it will put the class as
    QualDocument. If I have the * it defaults to Document.
    Is there a way to have the parser make all uploaded documents
    QualDocument instead of Document without doing this for each and
    every possible file extension?
    Thanks.

  • How to get the file size (in bytes) for all files in a directory?

    How to get the file size (in bytes) for all files in a directory?
    The following code does not work. isFile() does NOT recognize files as files but only as directories. Why?
    Furthermore the size is not retrieved correctly.
    How do I have to code it otherwise? Is there a way of not converting f-to-string-to-File again but iterate over all file objects instead?
    Thank you
    Peter
    java.io.File f = new java.io.File("D:/todo/");
    files = f.list();
    for (int i = 0; i < files.length; i++) {
    System.out.println("fn=" + files);
    if (new File(files[i]).isFile())
         System.out.println("file[" + i + "]=" + files[i] + " size=" + (new File(files[i])).length() ); }

    pstein wrote:
    ...The following code does not work. Work?! It does not even compile! Please consider posting code in the form of an SSCCE in future.
    Here is an SSCCE.
    import java.io.File;
    class ListFiles {
        public static void main(String[] args) {
            java.io.File f = new java.io.File("/media/disk");
            // provides only the file names, not the path/name!
            //String[] files = f.list();
            File[] files = f.listFiles();
            for (int i = 0; i < files.length; i++) {
                System.out.println("fn=" + files);
    if (files[i].isFile()) {
    System.out.println(
    "file[" +
    i +
    "]=" +
    files[i] +
    " size=" +
    (files[i]).length() );
    }Edit 1:
    Also, in future, when posting code, code snippets, HTML/XML or input/output, please use the code tags to retain the indentation and formatting.   To do that, select the code and click the CODE button seen on the Plain Text tab of the message posting form.  It took me longer to clean up that code and turn it into an SSCCE, than it took to +solve the problem.+
    Edited by: AndrewThompson64 on Jul 21, 2009 8:47 AM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How to update managed metadata column for all file in document library using powershell

    Hi,
    How to update managed metadata column for all file in document library using powershell?
    Any help on it.
    Thanks & REgards
    Poomani Sankaran

    Hi TanPart,
    I have changed the code which you have give in order to get the files from SharePoint 2010 Foundation  Document Library.But i am getting below error in powershell.
    Property 'ListItemCollectionPosition' cannot be found on this object; make sure it exists and is settable.
    Could you tell me which is the issues in it?
    See the code below.
    $web = Get-SPWeb http://ntmoss2010:9090/Site
    $list = $web.Lists["DocLib"]
    $query = New-Object Microsoft.SharePoint.SPQuery
    $query.ViewAttributes = "Scope='Recursive'";
    $query.RowLimit = 2000
    $caml = '<Where><Contains><FieldRef Name="Title" /><Value Type="Text">Process Documents/Delivery</Value></Contains></Where>' +
            '<OrderBy Override="TRUE"><FieldRef Name="ID"/></OrderBy>'
    $query.Query = $caml
    do
        $listItems = $list.GetItems($query)
        $spQuery.ListItemCollectionPosition = $listItems.ListItemCollectionPosition
        foreach($item in $listItems)
            #Cast to SPListItem to avoid ambiguous overload error
            $spItem = [Microsoft.SharePoint.SPListItem]$item;
            Write-Host $spItem.Title       
    while ($spQuery.ListItemCollectionPosition -ne $null)
    Thanks & Regards
    Poomani Sankaran

  • How do I save my CMYK font settings & make it avaliable for all files ?

    How do I save my CMYK font settings & make it avaliable for all files ? (adobe PS indesign file)

    Could you explain what you want to do a little bit better? CMYK and fonts aren't really related to each other.
    Also, are you using Photoshop or InDesign?

  • The specified file or folder name is too long,the url path for all files and folders

    The specified file or folder name is too long,the url path for all files and folders must be 260 character or less
    can we increase this limit?
    MCTS,ITIL

    Hi,
    As I understand, you want to increase the length of URL path in SharePoint 2010.
    Per my knowledge, this limit cannot be increased. SharePoint limits URL length because all relative URL links are stored in the clear forms on the SharePoint content DB and often this links are used as primary keys to link one table with another. Fields
    which are used to store these links (for instance tp_DirName from the AllUserData table) allow storing only 256 characters.
    There are several ways that you can resolve or mitigate URL length problems in the SharePoint Server 2010 environment. The following list provides suggestions:
    1. Upgrade all the end-user browsers to Internet Explorer 8, which has a longer URL length limit.
    2. Use shorter names for sites, folders, and documents and control the depth of the site and folder structures to reduce the lengths of URLs.
    3. If possible or allowed, use ASCII names for sites, folders, and documents. This will avoid situations where the URL will be lengthened by being encoded.
    4. To reduce the risk that the SharePoint Server 2010 end-users will encounter problems because of URL length limitations, we recommend that you apply the following effective limits in the deployment:
    256 Unicode (UTF-16) Code units - the effective file path length limitation, including a domain/server name
    128 Unicode (UTF-16) Code units - the path component length limitation
    More reference:
    http://technet.microsoft.com/en-us/library/ff919564(v=office.14).aspx
    http://sharepointknowledgebase.blogspot.in/2013/04/url-path-length-restrictions-in.html#.VKJN53BJA
    Best regards,
    Sara Fan

  • Is xmp files only availble for RAW files?

    When we develop a RAW image with Camera Raw, we always get an xmp file with all the settings,
    But after I developed a JPG image, I saw the Camera Raw Settings icon appeared above the right upper corner of the image thumbnail in Bridge,
    however, I couldn't find the xmp file.
    Is xmp files only availble for RAW files? JPGs or TIFs don't have xmp files for their Camera Raw settings??

    Read-only didn't work for me, on a single jpg file, although it did lead to some interesting behavior.  Set the read-only attribute on a jpg file in Windows XP and then tried the following:
    1.  Opened in Bridge, then into ACR 5.4.  Performed some edits, then tried "Done", received permissions error and would not save edits.
    2.  Did the same except now invoked "Open", went into CS4 with edits intact and allowed saving out as different file.  However, the ACR edits were not saved within the jpg, as expected, nor was a xmp created.
    3.  Removed the read-only attribute, repeated (2).  Even though did not save file in CS4 the "Open" action did embed the edits into the jpg.
    So read-only doesn't really allow creation of a xmp file, other than perhaps temporarily for transfer to Photoshop.  It does lead to somewhat inconsistent behavior, in that I would have expected the "Open" to fail also since it could not bury the edits in the jpg.
    Richard Southworth

  • Encode Video Files not working for avi files

    Hi,
    I've been trying to convert some .avi files to apple format using Lion's native 'Encode video files' function however keep getting a 'avconvert: source file not found for source file://fileparthhere avconvert: failed to create an export session. Check setup
    I can't work out why as this has worked before in Lion and works fine for other video formats. The only thing I've done is remove Final Cut Express HD and can't add it again as I don't own it anymore
    Suggestions? Is there a encoder to make this work or should it work anyway?
    Thanks

    If you click Yes the project file will be updated when you save it. That has nothing to do with the media.
    Are the Lesson and Media folders still in the Book Files folder (or whatever it's called)?
    Select one of the clips in the browser and use Edit>Item Properties. One of the first lines is Source. That gives you the file path for where your media is supposed to be located. What does it say? If nothing is there, use the File>Reconnect function and point the application to where the media is located.

  • Sender File Adapter stop processing all files

    Hello all,
    the file adapter pick up all files in the directory by default.
    if  a large number of files are in the directory then this could slow down the pi processing.
    is there any way to process only one file per polling??
    regards

    >
    Ralf Zimmerningkat wrote:
    > Hello all,
    > the file adapter pick up all files in the directory by default.
    > if  a large number of files are in the directory then this could slow down the pi processing.
    > is there any way to process only one file per polling??
    >
    > regards
    I do not have any proble if you have got the answer. BUT this blog says how to exclude the other files from the same folder.
    Your Case: For example, Your Sender CC wants to pick up file ABC.txt from /xyz dir, now suppose there are 10 thousand files of same name in the dir and you want ABC.txt should be picked up one by one, So how this blog is going to help you. Can you Plz explain to me and others too?
    @Sachin may be you can throw some light on this... may be I am missing something.

  • File Browser doesn't show files

    I am trying to pull some of my pictures from my Media Hub but can't seem to do it.
    All of the pictures show in the Home view but when I go the the File Browser...no files show up in the folders. The folders are on the left but when I click to open any of them there is nothing in them. 
    I have checked my settings but can't figure out what I am doing wrong....

    Check under the "import" folder in the file browser, your pictures might be stored there if you used the import tool.
    Cheers.

Maybe you are looking for