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'?>

<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'?>

<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.

Similar Messages

Framemaker uses $filename for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen?

Framemaker uses <$filename> for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen? In compiling our books it would be helpful to not have this extension appear as it then requires us to create extra files without them.

See: System Variables

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

FileDialog (filtering for certain file extensions)

I have used JFileChooser in the past and was modifying my code to use FileDialog instead as it looks better, looks like the one used by every other Windows program and takes less code to get the job done. My
question is how to filter for certain file extensions in FileDialog as you can in JFileChooser. I cannot seem to figure out how to, so any help would be highly appreciated. Thank you.
P.S. Also if you know how to turn off all files like you can in JFileChooser, that would also be extremely helpful.

Go to the JFileChooser tutorial at http://java.sun.com/docs/books/tutorial/uiswing/components/filechooser.html and skip to the section entitled "Filtering the List of Files". That sounds like it should answer your question.

Is there a way to hide ALL file extensions?

Hi
I am looking for a way to get OS X to hide ALL file extensions on the entire computer. I don't know why, but they really annoy me! I liked OS 9 and earlier because they didn't have them, and including them in OS X seems like a step backward to me. Wherever I can I simply don't save with file extensions (MS Office still retains this ability), and most applications will still open their files if you delete the file extension, but I do have a number of applications that require a file extension (such as OmniGraffle Pro), and it is very laborious to have to go through every file in order to hide the file extension. Is there some kind of master setting that you can apply to a volume in order to hide every file extension in it?

Hi All,
I have found this tutorial that partially solves the problem. http://www.youtube.com/watch?v=_NhRFxJCAQw
It is a quick way to hide the extensions of all files that have them in a given folder and the folders inside it, using automator. It does not hide the extensions of any file you add to the folder subsequently, and you can not apply it to a volume or a home folder. It is more of a labour-saving tool than an actual solution, but it is vastly better than having to get info for every single file.
As the author of the tutorial notes in his video, this is an option that apple could fix by just adding one more check-box to the finder preferences window. Or better still they could have just left things the way they were before and not introduced them in the first place... does anyone even know what they are for anyway? (Apart from to annoy you with a random bit of text at the end of a filename that you didn't place there.)

Hide all file extensions

Is there any way (without having to run scripts) to hide all file extensions by default? I am aware of the 'show all filename extensions' option in Finder's preferences, and how it only force shows all the extensions that have been turned off individually (file -> get info -> hide extension), however, I am looking for a 'force hide' option. Even on a per file type basis. Why isn't this in the finder preferences?
Cheers.

Google search for *"hide all file extensions"* yields many hits, including this one http://forums.macosxhints.com/showthread.php?t=58607 which has a simple two-line AppleScript that does the job.
As to why it isn't in the Finder's prefs, ask Apple. You can do that by either sending Feedback or sending bug reports and enhancement requests to Apple via its Bug Reporter system. To do the latter, join the Apple Developer Connection (ADC)—it's free and available for all Mac users and gets you a look at some development software. If you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report/enhancement request. You'll get a get a Bug/ER ID number; thus, starting a dialog directly with engineering.

Dreamweaver CC and Windows 8.1 - Can't Find A Valid Editor For This File Extension

Was running the latest version with no issues and then I loaded Office 2013 .. Now when I am in the remote site and try to double click on a .cfm file, I get a dialog box..Can't Find A Valid Editor For This File Extension..
I tried the support chat and they said Dreamweaver support was not available, try again later???
So I thought I would reinstall the CC version and now I can see the Dreamweaver icon next to the files but still ... can't open the file..
Any assistance would be appreciated?
Leo

The issue is only in Windows 8.x where when Dreamweaver CC is installed, it is not able to turn on the file type associations by default. The workaround for now is to manually add the extensions both within Windows and then within Dreamweaver CC itself.
Go to Control Panel > Programs > Default Programs > Set Your Default Programs and select Dreamweaver CC and then select 'Choose defaults for this program' and Select All or the extensions you want to open in Dreamweaver CC
Start Dreamweaver CC and go to Edit > Preferences > File Types/Editors and add '.cfm .cfc' to the extensions and then add C:\Program Files (x86)\Dreamweaver CC\Dreamweaver.exe then click on Apply and Close
That should be it.
James

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

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

Sender file adapter - Can I use *.xml for the file name

Hi Gurus,
I have some interfaces where I need to pick the file from a directory. The name of the file will have Data<i>time stamp</i> as the naming convention. Can I use *.xml to pick up my files from this directory?
The help.sap.com documentation says that we can use this naming convention.
<b>
● File Name
Specify the name of the file that you want to process. The name can contain placeholders (*, ? (placeholders for exactly one character)) so that you can select a list of files for processing.
</b>
I tried using *.xml for my file name in the communication channel, XI is not picking up this file.
Please let me know if you have the solution.
Thanks
Kalyan

Murthy,
Thanks for the reply.
I am using GuildFTP tool as my FTP server. In this tool, all the permissions were given for the file to pick up.
The status of the file is good.
Where in the file adapter configuration I have to select 'Read-only'?
The file adapter is working perfect with the exact name of the file.
Thanks
Kalyan

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?

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

DW CC: Can't find a valid editor for this file extension

Hi,
I am using dreamweaver cc for 1 month now. I have been having difficulty opening .asp file.
In the File panel, when i click on one of the asp files, the error message is 'Can't find a valid editor for this file extension'.
To solve this problem, I will right click on the file and choose Open with > Dreamweaver.
However, this is very inconvenient. Someone pls help!

You can configure that in your Operating System. In my version of Windows XP, open any folder and select TOOLS/FOLDER OPTIONS/FILE TYPES then scroll to the asp file type and select DW as the editor.

"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

I have 3 computers...Window PC, PowerBook G3 (old) and MacBook Pro. I use firefox for all of them and have for quite some time. Is there a way for them all to use the same toolbar? Each of them have differnet bookmark/ settings etc.,

I have 3 computers...Window PC, PowerBook G3 (old) and MacBook Pro. I use firefox for all of them and have for quite some time. Is there a way for them all to use the same toolbar? Each of them have differnet bookmark/ settings etc.,

Open Media Encoder and add your Sequences:
File > Add Premiere Pro Sequence
Navigate to your Premiere Project and select it in the list.
You can then select multiple Sequences from the Project (Ctrl+Click)
and load them all at once into Media Encoder and apply
the same encoding preset to all Sequences at the same time.

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

Similar Messages

Maybe you are looking for