Improved Metadata Handling?

The 1.1 PDF states:
Improved Metadata Handling
Mac OS X v10.4.6 includes support for EXIF metadata when exporting TIFF files with Aperture. You can view the EXIF information in exported TIFF files using other image editing applications, such as Adobe Photoshop.
OK, when I use Open with External Editor, I see the EXIF data in Photoshop (namely the IPTC) but when I instead use the Export command to a TIFF, no data. Bug?

Like William Lloyd posted earlier, I am not able to replicate this problem, at least on my PowerMac G5. Tried exporting the same image, loaded with IPTC data, in 16-bit and 8-bit TIF and PSD. Got the same results in all exports -- all the IPTC data showed up in Bridge Metadata panel and Photoshop Info window for all four images. Shoot only Canon Raw.
Wonder if there is a source data to output data bug specific to a camera make/model? Perhaps if the posters who are having this problem can state the source image type (camera make/model/file type) we can see if there is a pattern.
Mike
PowerMac G5 Dual 2.0GHz, Radeon X800XT Graphics Card; MacBookPro 2.0Ghz Mac OS X (10.4.6) iMac800 and Powerbook G4 also in household

Similar Messages

[svn:fx-3.x] 5526: User-submitted patch for SDK-19335 - DividedBox - improved includeInLayout handling

Revision: 5526
Author: [email protected]
Date: 2009-03-24 13:06:11 -0700 (Tue, 24 Mar 2009)
Log Message:
User-submitted patch for SDK-19335 - DividedBox - improved includeInLayout handling
Patch submission from Iwo Banas
QE Notes: n/a
Doc Notes: n/a
Bugs: SDK-19335, SDK-19334
Reviewer: None
tests: checkintests, mustella (DividedBox)
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19335
http://bugs.adobe.com/jira/browse/SDK-19335
http://bugs.adobe.com/jira/browse/SDK-19334
Modified Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/containers/DividedBox.as

Improved Metadata Storage option for Smart View

I have looked all through the manuals, but I cannot find any reference to the "Improved Metadata Storage" Smart View Option. Does anyone know what this option does and the Pros/Cons of using it?

Thank you for responding. I would like to resume having the "Save as PDF" option but the IE8 Browser is an older version and is unfortunately running slower and not well on some of the websites that need newer Browser versions. I checked out Chrome and don't like Firefox and still prefer the IE Browsers by comparison.
Is it very difficult for HP to add this handy feature back in a future HP SmartPrint release that is compatible with the IE Browser?
Thanks!

Metadata handling in ProxyElement (inconvenient)

Hello!
I've come across the inconvenience when working with metadata in ProxyElement.
1) Every element that is proxied gets ProxyElement metadata values (that have been set before) on permanent basis and not loses it after being unset as a proxied element:
public function set metadata(value:Metadata):void{
// Transfer all old values to new:
for each (var url:String in proxiedMetadata.keys){
value.addValue(url, proxiedMetadata.getValue(url));
proxiedMetadata = value;
proxiedMetadata.addEventListener(MetadataEvent.VALUE_ADD, redispatchEvent);
proxiedMetadata.addEventListener(MetadataEvent.VALUE_CHANGE, redispatchEvent);
proxiedMetadata.addEventListener(MetadataEvent.VALUE_REMOVE, redispatchEvent);
2) Consumer that is listening for METADATA_ADD of ProxyElement never gets informed of new values appearing in ProxyElement metadata after the proiedElement is set. Look at this code in creating ProxyElement:
proxy2 = new ProxyElement();
proxy2.addEventListener(MediaElementEvent.METADATA_ADD,
function(event:MediaElementEvent):void {
trace ("METADATA ADDED: " + event.namespaceURL);});
proxy2.addEventListener(MediaElementEvent.METADATA_ADD,
function(event:MediaElementEvent):void {
trace ("METADATA REMOVED: " + event.namespaceURL);});
And this, say, button click handler:
var e:MediaElement = new MediaElement();
if (null == proxy2.getMetadata("META1")) {e.addMetadata(
"META1", new Metadata());}
else {e.addMetadata(
"META2", new Metadata());}
proxy2.proxiedElement = e;
METADATA_ADD and METADATA_REMOVED are never called.
This is particulary inconvenied when using LoadFromDocumentElement. Imagine complex processing of loaded content with adding metadata to it - top level LoadFromDocument will never inform a listener of the addition of proxied metadata when its content is loaded and formed.
For now I'm using a temporary solution like this:
override public function set proxiedElement(value:MediaElement):void {
 super.proxiedElement = value;
 if (null == value) return;
 //Copy all proxied metadata
 var keys:Vector.<String> = value.metadataNamespaceURLs;
 for each (var key:String in keys) { addMetadata(key, value.getMetadata(key));
It does not fire METADATA_REMOVE events but OK for LoadFromDocuments.
I think it will be great if ProxyMetadata gets somehow rewritten in later releases - or may be I'm not getting a concept of ProxyElement?
What do you think?
Thank you!

Coorection on quick proxy remedy in my first post. The overriden func should look like this:
override public function set proxiedElement(value:MediaElement):void {
 super.proxiedElement = value;
 if (null == value) return;
 //Dispatch proxied metadata events ;O)
 var keys:Vector.<String> = value.metadataNamespaceURLs;
 for each (var key:String in keys) { metadata.dispatchEvent(
new MetadataEvent(MetadataEvent.VALUE_ADD, false, false, key, value.getMetadata(key))); }
I did not take into account the:
var oldValue:* = data[key];data[key] = value;
if (oldValue != value){
in Metadata code - so resetting values as in my first post does not fire events.
Worked for me because my own bug :O)

Quicktime Metadata handling in podcast producer batchs

Hi,
I'm wondering if there's a way to extend the amount of metadata that can be handled by the podcast producer batch so that it feets iTunes needs ?
I know that it depends of the workflow you use for the "common" metadatas (artist name, year, type, ) but what about the exotic ones : commentaries, lyrics and even illustration ?
Thanks in advance for your answer.
Nicolas

HAZAAR! Solved it for me, hope it's the same for you. Ensure your Server HOST name is identical to your service name. IT IS CASE SENSITIVE! I had to edit the /Library/PodCastProducer/Shared/Server/memberpreferencesUUID so it matched my hostname identically, and all is now working.
You'll notice you probably have errors in /Library/Logs/pcastserverd/apache_error.log referencing SNI name not matching hostname, this is the clue. Hope this resolves it for you also.
Pete

Photoshop and Metadata handling.

We have two related issues we're trying to solution.
(1) If we create a blank Photoshop file ("template") that is merely a size, resolution and color profile, when we add an image (that does contain metadata), the image's metadata is not retained in the template metadata. We need to be able to transfer that image's metadata, automatically, to the template. (We do not want to have to copy/paste.)
(2) Let's say we now have a template with 1 image and associated metadata. We now need to add another image(s) to this template and have the second image's metadata also transfer automatically. (This auto-transfer of metadata would occur for any subsequent image added.)
We are using CS4 v11.0.2.

You may want to also ask over at
http://forums.adobe.com/community/photoshop/photoshop_scripting
as I suspect achieving this in Photoshop may require Scripting.

Importing Metadata in Smart View

Dear All,
In Smart view when I migrate the metadata from one worksheet to other its is not getting migrated. I have followed the below steps still its not..
To import metadata to a copied worksheet :
1. Back up your work.
2. From the Smart View menu, select Options, then Advanced, and ensure that Improved Metadata Storage is
selected.
3. Use Excel to copy a worksheet. This operation copies the visible contents of the source worksheet but not the
metadata (connection information, POV selections, alias tables and the like) to the destination worksheet.
4. With the destination worksheet active, from the Smart View menu, select More, then Import Metadata to
display a list of all open workbooks and their corresponding open worksheets.
5. From the list, select the worksheet that contains the metadata that you want to import to the destination
worksheet.
6. Click OK. You will be asked to confirm your selection.
7. Refresh.
Help in solving this issue is highly appreciated.
Thanks,
Kamal

I don't know what back end you are connecting to, but when I follow the steps you outlined with Essbase's Good Old Sample.Basic, it works just fine -- the members that were selected in the POV are migrated across.
This is on Excel 2007 with Essbase 11.1.2.0.
Regards,
Cameron Lackpour

Smart View internal metadata error when creating SmartView reports

Hi all,
I have a really strange problem when trying to use HsGetValue -functions in Smart View (in Excel 2010).
The thing is that I can create a lot of formulas for a sheet that have links to other sheets. However, in some pont (I don't exactly when it happens), I quite randomly get an error in Excel saying "This workbook contains Smart View internal metadata that needs to be repaired. This will automatically be repaired but may take some time". This error box appears a few times, I just click it and then it disappears. Obviously, this is annoying and the Excel is unusable.
Usually it happens when I try to format the sheet or add, e.g., company logo into the sheet, or try to do a bit more difficult linking of the cells.
Any ideas what is going on here? Smart View version is 11.1.2.1.103 (Build 100).
Thanks in advance!

Please take a look at KB ID 1432526.1. I've copied the text below.
Applies to:
Hyperion Financial Management - Version: 11.1.2.1.102 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
The following message is displayed when opening the Smart View files:
This workbook contains Smart View internal metadata that needs to be repaired. This will automatically be repaired but may take some time.
It may take a long time to open or save the Smart View templates.
Changes
Smart View has been installed by a user different, than the one that is currently logged on the workstation, i.e. service account or installation account.
Cause
When the user accesses Smart View for the first time, on a workstation where the SmartView has been installed by another user, the following registry key will be missing in the user's profile:
HKEY_CURRENT_USER\Software\Hyperion Solutions\HyperionSmartView\Preferences]
"UseStorageCompression"=hex:01
"SelectedOptionTab"=hex:02
If SmartView is installed by a different user i.e. service account or installation account, then the user profile registry will be missing "UseStorageCompression" and "SelectedOptionTab", resulting in a incorrect saving of file metadata.
Solution
Follow the steps below to automatically create the required registry keys for the current user profile:
1.Open Excel and select Smart View menu.
2.Click the "Options" icon to open the Options window.
3.In the "Advanced" tab, under the "Compatibility" section make sure the "Reduce Excel File Size" option is selected and click OK.
4.The following Windows Registry keys will be created under user profile, enabling proper compression of the metadata:
[HKEY_CURRENT_USER\Software\Hyperion Solutions\HyperionSmartView\Preferences]
"UseStorageCompression"=hex:01
"SelectedOptionTab"=hex:025.Now the user should be able to open the smartview template without the error message.
6.Additionally it is also recommended to select the "Improve Metadata Storage" option in the Smart View Options window which will create the following registry key:
[HKEY_CURRENT_USER\Software\Hyperion Solutions\HyperionSmartView\Preferences]
"IgnoreShapes"=hex:01

Aperture 3.1 doesn't export lens metadata

When I export images from Aperature (File->Export->Version), they are missing lens metadata.
I exported a master version of an image and a version of the same image.
I open both the master and the version in DxO.
The master contains lens metadata with a value of "18-105mm f/3.5-5.6" and the version is simply blank.
This is a fresh copy of Aperature 3.1, with no plugins, and I can repeat this behavior for any master image that contains lens metadata.
Is this a bug that will be fixed in a Aperature update? This is a very frustrating bug.

I bought AP 3.1 after my metadata nightmares with iPhoto '09 (I wasn't going to pay for '11). AP 3 has some nice features (like iPhoto on steroids) and its metadata handling is much better than iPhoto. But this bug is really, really messing with my photo processing workflow.
I'm going to keep looking for a solution (I haven't had the time thus far) and will update the thread. Thanks for the confirmation of the bug, and the commiseration
-Elliot

Can the Metadata Browser be extended?

I am thinking of filtering according to 'Focal Length' or 'ISO Speed Rating' or eventually the aperture f-value (if only this were not shown together with the exposure time in 'Exposure').
Thanks
Stefano

Hoping, not only for extension but Metadata handling Module with more choices of handling Metadata than current two panes.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
http://donricklin.blogspot.com/

Big PDF Handling: Acrobat vs. Preview

I had the occasion to help out at the polls today. A coworker had a G4 iBook and a data CD with all the registered voters in our county on it, including name, address, precinct numbers, voting location, and birthdate. There were about 400,000 voters on the PDF file contained on this CD. We used it to determine if voters were on the master registration list and also to find out a voter's precinct number and voting place if he came in with just an ID and no voter registration card.
Anyway, my coworker only had Preview on his iBook, no Acrobat. Preview handled the big PDF but scrolling sometimes got brutally slow with lots of beachballing. We tried using the search feature in Preview and also Spotlight but had little success with that.
My question, would Acrobat have been as good, a little better, or way better to use if he had had it on his iBook? What else could we have done to improve our handling of the PDF?
P.S. We did drag the PDF off of the CD to the Desktop so that we were working from the HD and not the optical drive.
Thanks,
Steve M.

HI Steve,
"Preview handled the big PDF but scrolling sometimes got brutally slow with lots of beachballing. We tried using the search feature in Preview and also Spotlight but had little success with that."
Much of this depends on the size of the CD file, if there was sufficient hard disk space on the iBook, RAM, and if the owner of the iBook has performed any maintenance. If you saw the beach ball just viewing text in a PDF file, I'm more inclined to think that it was the iBook causing the slow down, rather then whether or not it was viewed with Adobe Acrobat or the Mac's Preview.
I use both Preview and Acrobat on my 60GB iBookG4, but I keep a lean machine plus I do maintenance weekly. Both Preview and Acrobat function as they should without the beachball syndrome..
Carolyn
Message was edited by: Carolyn Samit

Work around for writing out metadata to masters?

I am sure that the aperture community has dealt with this before.
Prior to purchasing aperture, I made sure that metadata like captions keywords, etc. could be written back out to the master file. This would allow one to not be held hostage to aperture. With various updates this ability has gone away. The statement from Apple less than a year ago, seems to indicate that aperture will not write metadata back out to the Masters.
Quote: http://support.apple.com/kb/TA23784?viewlocale=en_US
By Design: Aperture won't export metadata with RAW masters
Unlike applications such as Photo Mechanic, Aperture does not write IPTC and keywords to the original RAW file. Instead, Aperture stores this information in its library and attaches it when exporting versions in JPEG, TIFF, PSD, or PNG format. If you export the RAW masters, none of your metadata changes will come along with them. Unlike the issues listed above, this feature is by design.
If your goal is to archive RAW files outside of Aperture with metadata attached, you'll need a workaround to this aspect of Aperture's metadata handling. Because Aperture is designed to read added metadata at time of import (despite the current issue described above), the best long term solution (after issues are resolved) will be to add your metadata in Photo Mechanic (or similar) prior to importing them to Aperture and then refrain for the most part from using Aperture's metadata tools. If you don't like that workaround, a secondary workaround is to export JPEG versions to be kept alongside the RAW masters. To save disk space, the JPEG copies could be a minimal size."
I am sure that many community members have encountered this problem. Specifically, I have many slides to scan, so the raw input file is a tiff. Aperture does not support writing metadata to tiffs. And to depend on aperture to write out metadata to any master file is probably setting yourself up for disappointment.
Can the community recommend a way around this?
Thanks

You are referring to a very old document about Aperture 1, clearly marked as 'no longer updated'. Aperture 3 can export IPTC metadata with RAW files. You have the choice of embedding them into the RAW file, or write them in a separate xmp sidecar file. Just choose 'Export Master'. Aperture can also write back metadata into a RAW file without exporting them. Choose 'Metatadata - Write IPTC metadata to original'.

Weekly build notes listings

Since there are major changes going on in the TLF weekly builds, and the ASDocs aren't up to date, and the changes made are not searchable, I thought people might want the list dumped on here so changes to particular classes would show up in a forum search. To see the changes made in Build 360, check out the TLF Blog post on it ( http://blogs.adobe.com/tlf/2009/02/tlf_api_changes_in_build_370_1.html ).
Here's the list. Maybe this could become a common practice.
Build 432, Fri May 15 2009
Changes in build 437 (2009/05/22)
 * remove flashx.textLayout.edit.UndoManager and flashx.textLayout.IUndoManager
 * Fix 2330964 BackgroundColor Placed incorrectly from TextLineFactory. Actually was in 436.
 * Fix 2326588 TextContainerManager Does Not Support Background Color
 * Fix 2330946 Remove TextContainerManager.trunctationOptions property
 * Fix 2337918 Please expose the scrollToPosition() API in TextContainerManager
 * Fix 2336672 Preserve selection when switching editingMode in TextContainerManager
 * Setting editingMode to the current editingMode should do nothing in TextContainerManager
Changes in build 436 (2009/05/22)
 * Fix 2331711 TextContainerManager now sends a DamageEvent from setText().
 * Fix 2326543 bug where selection wasn't being extended on mouse drag.
 * add [RichTextContent] metadata to SpanElement and FlowGroupElement mxmlChildren properties
 * Fix 2337740 Flex bug SDK-20964 TCM rcycling bug
 * Partial fix 2330964 background color placed incorrectly from TextLineFactory
 * Remove vestigal experiment with Tables code
 * Fix 2321538. On the Mac, the keyboard shortcuts for cmd-A,C,V,X were not working.
 * Fix 2326543, "drag select of scrolling flows doesn't expand selection".
 * Fix 2329527. Content bounds being reported was slightly different between the factory and TextFlow composer.
 * Fix 2328695 TextContainerManager Stops Receiving FocusIn Events. This is a complete fix - previously this bug was worked around
 * Added TextLineFactoryBase.isTruncated
 * Fix 2315119 - Graphic will be redrawn when link applied.
Changes in build 434 (2009/05/22)
 * Fix 2323921: RichText truncation doesn't work in all cases
Build 432, Fri May 15 2009
Changes in build 432 (2009/05/14)
 * Fixed regression that broke truncation feature
 * Added TextLineFactoryBase.isTruncated
 * Changed text line factory behavior such that scrolling is turned off when truncation options are set
Build 427, Fri May 8 2009
Changes in build 427 (2009/05/07)
 * Fix bug - RTE in computeSelectinIndexInContainer
 * Namespace change -- mxml namespace for TLF was "library:adobe/flashx/textLayout". Now it is: library://ns.adobe.com/flashx/textLayout".
 * Fix bug - Scrolled TextContainerManager Can be Difficult To Create Point Selection
Changes in build 426 (2009/05/06)
 * Fix bug - TextFlow double-deletes text when pressing the backspace or delete key
Build 422, Fri May 1 2009
Changes in build 422 (2009/04/30)
 * API Changes: TextContainerManager now has a getContentBounds function, in place of individual getters for contentLeft, contentTop, etc. ContainerController also now has a getContentBounds function, in place of individual getters. Added functions to TextContainerManager to support custom classes for ISelectionManager and IEditManager (see createSelectionManager and createEditManager).
 * API changes for TextContainerManager:
 o getInteractionManager renamed to beginInteraction(), and added a new function endInteraction() which clients should use after beginInteraction() to signal that they are done with selecting/editing. This tells the TextContainerManager that it can go back to factory mode, which is more efficient.
 o invalidateInteractionManager() removed and replaced with two new functions, invalidateSelectionFormats() which clients should called when SelectionFormats have changed, and invalidateUndoManager which clients should call to change the undo manager.
 * API Changes for InputManager
 o InputManager renamed as TextContainerManager
 o IInputManagerClient removed, now you can subclass InputManager and override its methods
 * API Changes:
 o InputManager
 + damaged property renamed to isDamaged() function
 + focusSelectionFormat renamed to focusedSelectionFormat
 + container retyped to Sprite
 + compositionWidth and compositionHeight removed as constructor parameters, now you need to set the properties on the InputManager you create
 o ContainerController
 + container retyped to Sprite
 o ISelectionManager
 + focusSelectionFormat renamed to focusedSelectionFormat
 o IConfiguration & Configuration
 + focusSelectionFormat renamed to focusedSelectionFormat
 * API Changes:
 o ISelectionManager
 + setSelection deselects if negative numbers are passed in.
 + selectAll removed, you can call ISelection.setSelection() to get the same behavior, if you need to redraw the selection, call ISelectionManager.textFlow.flowComposer.updateAllControllers().
 + flushPendingEvents moved to IInteractionHandler
 + notifyInsertOrDelete moved to IInteractionHandler
 o IUndoManager
 + clear renamed to clearAll().
 + undoLastOperation renamed to undo()
 + redoLastOperation renamed to redo()
 * API Change: SelectionEvent now contains a SelectionState, not an ElementRange; this is much cheaper for us to provide. ElementRange is now tlf_internal. ElementRange.firstLeafPosition renamed to absoluteStart, ElementRange.lastLeafPosition renamed to absoluteEnd.
 * API Change: TextScrap.copyTextScrap renamed to clone.
 * API Changes to InputManager. defaultInputManagerConfiguration renamed to defaultConfiguration. composeToController renamed to compose(), and updateToController renamed to updateContainer().
 * API Changes:
 o ISelectionManager:
 + Event handling functions moved out of ISelectionManager into new interface, IInteractionHandler
 + selectionFormat renamed to currentSelectionFormat
 + selectionState renamed to function getSelectionState()
 + setSelection now takes default parameters to select the entire flow
 + noFocusSelectionFormat renamed to unfocusedSelectionFormat
 o SelectionFormat:
 + blockAlpha reanmed to rangeAlpha
 + blockBlendMode renamed to rangeBlendMode
 + blockColor renamed to rangeColor
 o IEditManager:
 + added get undoManager()
 + added changeElementID()
 + added changeElementStyleName()
 o SelectionManager:
 + activeMark and anchorMark are now private
 + selectionChanged is private
 + setSelectionState is tlf_internal
 o EditManager:
 + stage is private
 + ChangeElementIdOperation renamed to ChangeElementIDOperation
Changes in build 420 (2009/04/28)
 * API change: Removed the misleadingly named and superfluous TextFlowLine.textIndent. Documented and ensured consistent use of TextFlowLine.lineOffset as lhe line's offset in pixels from the appropriate container inset (as dictated by paragraph direction and container block progression), prior to alignment of lines in the paragraph.
 * API change: more changes to the factory classes. ITextLineCreator is now a property of the base class, so instead of passing it in the constructor you construct and then set the property in the factory. bounds property renamed to compositionBounds, and measuredBounds renamed to contentBounds. containerController property is now private.
 * API Change: moved ITextLineCreator interface from the elements package to the compose package.
 * PlainTextExporter is now public and has methods for controlling the paragraphSeparator and whether discretionary hyphens are included in the export. To use it, you can either construct it directly, or via the TextFilter class. Removed the newlineIndicator string from IConfiguration.
 * Fixed a bug where tabs in RTL text were being being offset by textIndent and marginRight values.
Changes in build 419 (2009/04/24)
 * Once a mouseWheel event has been handled, mark with preventDefault so client applications don't also try to handle it.
 * Don't start compose if text is already composed. Optimization for callers of composeToPosition.
 * Always call resetContentTopLeft, to give more accurate top left positions, particularly for cases where the text is outdented and left aligned.
 * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
Build 418, Fri Apr 24 2009
Changes in build 418 (2009/04/23)
 * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
Changes in build 417 (2009/04/22)
 * Fixed Vertical Justification behavior; it now increases the spacing between consecutive lines proportionally rather than spacing lines uniformly.
 * API Changes: Renamed DisplayObjectContainerController to ContainerController, and removed IContainerController and IInternalContainerController. Wherever you used to use "IContainerController" or "DisplayObjectContainerController" now just use "ContainerController".
 o Moved some functions that were public into the tlf_internal namespace: effectivePaddingLeft, effectivePaddingTop, effectivePaddingRight, and effectivePaddingBottom.
 o ColumnState.createColumnState removed. A ColumnState constructor now takes all the relevant values, so whereever you used to do this:
 + var columnState:ColumnState = ColumnState.createColumnState(...your values here...);
 o you can now do this:
 + var columnState:ColumnState = new ColumnState();
 o ColumnState.getColumnAtIndex(index) has been renamed to getColumnAt(index). So, once you have the columnState, you do, for instance:
 + var columnRect:Rectangle = getColumnAt(0);
 * Fixed bug where spaces at end of a line would "overflow" into neighboring columns. New code keeps drawing of cursor at the column boundary and limits block selection drawing to the same bounds.
 * Enhancement to cursor navigation for Right to Left text systems. Previous code moved cursor according to logical order vs. visual order. Result was that a right arrow key press in Arabic, Hebrew or other RTL languages meant that the cursor actually moved left. New code moves cursor according to the visual order of the text based on the direction of the entire text flow. Note that changing the direction on a paragraph will not alter the behavior of the cursor, nor will the presence of LTR text within a RTL text flow. This means that if a TextFlow is set to Right to Left and a given paragraph is entirely in English and the paragraph is set to be Left to Right, the cursor will seem to move in the wrong direction. TLF does not support customization of cursor movement based on the locale or direction of anything except the parent TextFlow.
 * Fixed a bug that caused undoing an ApplyFormatToElementOperation to have no effect.
 * API Changes:
 o DisplayObjectContainer event handling functions renamed:
 + processMouseOverEvent -> mouseOverHandler
 + processMouseOutEvent -> mouseOutHandler
 + processMouseWheelEvent -> mouseWheelHandler
 + processMouseDownEvent -> mouseDownHandler
 + processMouseUpEvent -> mouseUpHandler
 + processMouseMoveEvent -> mouseMoveHandler
 + processMouseDoubleClickEvent -> mouseDoubleClickHandler
 + processFocusInEvent -> focusInHandler
 + processFocusOutEvent -> focusOutHandler
 + processActivateEvent -> activateHandler
 + processDeactivateEvent -> deactivateHandler
 + processKeyDownEvent -> keyDownHandler
 + processKeyUpEvent -> keyUpHandler
 + processTextInputEvent -> textInputHandler
 + processContextMenuSelectHandler -> menuSelectHandler
 + eventHandler -> editHandler
 o ISelectManager & SelectionManager & EditManager renamings:
 + eventHandler -> editHandler
 * API Changes: renamed IContainerController.scrollLines to getScrollDelta, renamed InputManager.scrollLines to getScrollDelta, and removed constants for default container width and height.
Changes in build 412 (2009/04/10)
 * API CHANGE: DisplayObjectContainerController methods processCopyEvent, processCutEvent, processPasteEvent, processSelectAllEvent collapsed into a single processEvent that handles all these basic events. Added to ISelectionManager a new function, processEvent for handling these same events in the SelectionManager, and removed processSelectAll, which is no longer used. cutTextScrap and pasteTextScrap moved from ISelectionManager to IEditManager, since these are editing operations.
Build 411, Fri Apr 10 2009
Changes in build 411 (2009/04/09)
 * Fixed a bug where noFocus selection format was not being set on re-activation
 * API CHANGES. These functions in IFlowComposer were renamed:
 o updateContainer -> updateToController
 o updateAllContainers -> updateControllers
 o composeContainer -> composeToController
 o composePosition -> composeToPosition
 * API CHANGE: Changing name of TextFlow.hostTextLayoutFormat to hostFormat
Changes in build 410 (2009/04/08)
 * Fix bug where leading info used for composing the next line was being saved prematurely, causing incorrect layout if the current line needed to be composed in multiple passes.
Build 409, Tue Apr 7 2009
Changes in build 409 (2009/04/07)
 * Fix bug where clicking on container when height or width NaN doesn't work. When measuring, transparent hit detect region wasn't being redrawn to correct size after composition.
 * API CHANGE: Plain-text import/export changes. Newline indicators exported based on setting in IConfiguration.newLineIndicator. On import, LF/CR/CR+LF are all recognized as new line indicators.
 * Compose to container size with scrolling on -- previously was composing to double composer size. This may flush out some invalid line bugs.
 * Fixed a bug with blockProgression="rl" and compositionWidth=NaN, lines were getting improperly clipped out so that no text appeared.
 * API CHANGE: Renaming functions in IFormatResolver. invalidateAllTargets is now invalidateAll, and invalidateTarget is now invalidate. resolveTextLayoutFormat is now resolveFormat.
 * API CHANGE: eventMirror on FlowLeafElement and SubParagraphGroupElement is now tlf_internal.
 * API CHANGE: Moving TextRange from the edit package to the elements package.
Changes in build 406 (2009/04/02)
 * API CHANGE: Renaming DamageEvent.damageStart to damageAbsoluteStart.
 * API Change: IConfiguration.includePartialLine renamed to overflowPolicy. Defined new class OverflowPolicy that describes the different policies that can be used to control whether lines that fall at the end of the container are included in the container, or not.
Changes in build 405 (2009/04/01)
 * API CHANGE: IFlowComposer.firstDamagePosition renamed to damageStartPosition.
 * API CHANGE: Rename GeometryUtil.getRangeBounds to GeometryUtil.getHighlightBounds.
 * API CHANGE: ParagraphElement.getText now takes an additional optional parameter that specifies the terminator for the paragraph. By default, this is the Unicode paragraph terminator character (\u2029), but you can make it whatever you want, including a simple newline by passing a String for the paragraphTerminator. This change is backwards compatible for current callers of getText().
 * Fix clipping problem when text is placed above the container (6 lines aligned verticalAlign = bottom in a space that fits 4 lines).
Changes in build 404 (2009/03/31)
 * Updating typgraphic case --Markup and API Change-- Now uses a new class TLFTypographicCase, and has different options. Support for "title" and "caps" dropped. Use TLFTypographicCase with TLF in preference to flash.text.engine.TypographicCase. "smallCaps" renamed to "capsToSmallCaps". "capsAndSmallCaps" renamed to "lowercaseToSmallCaps". Also made AUTO the default setting for kerning, which matches FXG spec.
Changes in build 403 (2009/03/30)
 * format Markup Changes:
 o <TextLayoutFormat> now <format>
 o When referring to a format id, don't use brackets. So this:
 <TextLayoutFormat id="english" locale="en" fontFamily="Minion Pro"/>
 This text is supposed to be in Minion Pro via a named character attribute
 Is now this:
 <format id="english" locale="en" fontFamily="Minion Pro"/>
 This text is supposed to be in Minion Pro via a named character attribute
 * API Changes:
 o Rename FlowElement.textLayoutFormat -> format
 o Rename FlowElement.computedTextLayoutFormat -> computedFormat
 o Rename IContainerController.textLayoutFormat -> format
 o Rename IContainerController.textLayoutFormat -> computedFormat
 o Rename DisplayObjectContainerController.textLayoutFormat -> format
 o Rename DisplayObjectContainerController.textLayoutFormat -> computedFormat
Changes in build 402 (2009/03/27)
 * verticalAlign of "middle" or "bottom" will now align to the compositionHeight (or compositionWidth in vertical text) even if the height of the text exceeds the compositionHeight. This means that lines that don't fit may be get pushed above the box, or (for middle) pushed both above and below. It also means that all lines will forced to compose to the end, so it will be quite slow to use verticalAlign in large text flows. Made some corresponding fixes to scrolling to make it work with text off the start of the container. Added some new test cases to exercise this functionality in all the different alignment settings.
 * Scrolling fixes for next/previous line with arrow keys. Fix a bug where the arrow key would move to the end of the line if the line required composition (e.g., the line was not previously in view). Also fixed a bug when scrolling up by a line where it would scroll down instead.
 * doOperation used to return an SelectionState, but with the exception of two places that were using it internally, all external callers only checked to see if it was null or not. null was being used to indicate failure, or nothing changed, which means that the operation is not placed on the undo stack. Now it returns a Boolean, true for success, false for failure. There may be further changes in this area to make FlowOperations simpler.
Changes in build 397 (2009/03/20)
 * Made DisplayObjectContainerController's and FlowElement's TextLayoutFormat properties read/write (used to be write-only).
 * Merge ContainerControllerBase class into DisplayObjectContainerController.
 * Mark TextFlow class as final
Changes in build 396 (2009/03/19)
 * Fix RTE in StandardFlowComposer.releaseLines
 * Fix possible source of the RTE on null reference from findFirstAndLastVisibleLines in ContainerControllerBase.
Changes in build 394 (2009/03/17)
 * Fix issue with changes made in StatusChangeEvent to embedded graphics by blocking recursive composition. Bug 2298043
 * Add IFlowComposer.composeInProcess property.
 * Fixed problem where first part of a link could not be replaced by a new link. New code allows partial replacement of a link element with a selection which starts at the first character.
 * Fixed a problem where the cursor was getting set to the I-beam, and wouldn't set back.
Changes in build 393 (2009/03/16)
 * Fix a bug where keyboard navigation with linked containers was causing a scroll because it was trying to scroll to a position not in the container.
Changes in build 392 (2009/03/13)
 * Removed optimization that was preventing scrolling in the logical width direction if scrolling in the logical vertical direction was turned off.
 * Removed the container-level mouseMove and rollOver handlers which were changing the link state. These are now part of the LinkElement, and added only when they are needed.
Changes in build 390 (2009/03/11)
 * Fix for application of attributes to a point selection where only the last attribute would be applied. New code applies all attributes applied to the point.
 * IContainerController.contentWidth (or contentHeight in vertical text) is now based on the actual text width, not the unjustified text width. This fixes some problems where scrolling wasn't working correctly because the reported width of the text was greater than the compositionWidth, but lines were wrapped. It does mean that to get the unjustified width you will have to set the textAlign to something other than "justify", recompose, and then get the resulting width.
 * Fix for unintended scroll when at the end of a TextFlow.
 * Fix for RTE when dragging over text generated from a factory, or non-TLF TextLines.
 * Changes for alignment and measurement. You can now set NaN for compositionWidth or compositionHeight, and TLF will compose and use the generated contentWidth or contentHeight for alignment, scrolling, etc. The composer now generates a topLeft for the bounds, so you can make a full "content bounds" using contentLeft, contentTop, contentWidth, and contentHeight.Note that this is logical bounds and not inked bounds, so there are some circumstances where ink will not fit in the content bounds.Fixed bugs in how the factory was doing vertical alignment that caused it to be a few pixels off.Fixed some incosistencies between how the standard flow composer worked and how the factory's simple composer works -- composition results should now be more uniform. Added a new test program, MeasurementGrid, for testing all this. It's still a work in progress.
Changes in build 388 (2009/03/09)
 * Fixed issue where applying link or TCY to the last span of a paragraph caused a dangling span to remain with the para terminator.
 * Fixed issue where text would go into a link when it was the last element in a paragraph. Newly typed text now goes into a new span when the selection marker is at the last index.
Changes in build 386 (2009/03/06)
 * Fixed issue with placement of underline and strikethrough on inline images.
 * Fixed placement of underline and strikethrough on text which has a baseline shift applied to it.
Changes in build 385 (2009/03/04)
 * Combined SWC 'textLayout.swc' now included in the libs directory of the build. This includes everything from textLayout_core, textLayout_edit, and textLayout_conversion.
 * Combined RSLs now included in the rsl directory of the build. Both an unsigned SWF and signed SWZ are created. These include everything from textLayout_core, textLayout_edit, and textLayout_conversion.
Changes in build 382 (2009/03/02)
 * Fix issue with composing a TextFlow containing just an empty ParagraphElement.
 * TextLineFactory will generate lines that included InlineGraphics whose source is a "class" - normally an embedded graphic.
 * Expose eventMirrors - use FlowElement.getEventMirror function to access the eventMirror.
Changes in build 381 (2009/02/27)
 * Fixed issue with graphic assigned to ILG getting the wrong sizing.
 * Factory instance functions renamed to textLinesFromString and textLinesFromTextFlow. Static functions renamin unchanged.
Changes in build 380 (2009/02/26)
 * Made backgroundColor work with TextLineFactory. This required an API change - the callback to the factory now must take a DisplayObject as its parameter, since it won't always be passed TextLines. Also, the background shapes themselves no longer include leading, so they do not exactly coincide with the selection bounds. This was another change to support calculating the shapes during composition as opposed to afterward. Also added a snapshot test as part of FactoryImportTest that uses backgroundColor, in addition to updating the existing unit tests.
Changes in build 379 (2009/02/25)
 * Fixed for multiple containers ( we were getting incorrect textLength in the containers), as well as a fix that forces scrollToPosition to compose if the text isn't composed yet.
 * Fix so that we scroll to the active position of the selection after we extend the selection with a keyboard event. Also fixed some of the TextRangeUtil functions used for nextLine, etc. to make sure text is composed through selection before processing that depends on composition results.
 * Plain text import now consistently converts \r to space; previously it was converting only the first one. Still not clear what correct behavior should be.
Changes in build 377 (2009/02/23)
 * Fix bug with importing trailing empty div elements.
Changes in build 374 (2009/02/18)
 * Added support for TextField-style leading. A new leading model value allows lineHeight to be interpreted as the distance of line's ascent from the previous line's descent. Further, lineHeight can be negative. which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
Changes in build 372 (2009/02/16)
 * Added "enableAccessibility" property to IConfiguration, defaults to false. Allows clients to avoid paying price for TextAccImpl objects unless needed.
 * Added support for truncation for text composed using TextLineFactory. The TextLineFactory methods now take a truncation options parameter, which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
Changes in build 371 (2009/02/13)
 * Fixed a number of bugs relating to scrolling by line.
 * Measurement changes. Changed the way contentHeight and contentWidth are calculated, now they reflect the size of the text, regardless of alignment. Eliminated unjustifiedContentHeight and unjustifiedContentWidth; use contentHeight and contentWidth instead.
 * Fix RTE in damage when we try to damage back one line, for textFlow that doesn't have any leaf nodes.
 * Changed InlineGraphicElement so that GraphicElements (and the TextBlocks they are part of) don't get released. Fixes RTE on null pointer in places where we access the GraphicElement.
 * Fix bug deleting all of the last Span of a paragraph, plus some of the following paragraph.
Changes in build 370 (2009/02/12)
 * Removed textFlow property from CompositionCompletionEvent. Use event.target to get to the TextFlow.
Changes in build 369 (2009/02/11)
 * Fix issues in usage of hostTextLayoutFormat
 * Fix FXG export to not export styles with value "inherit"
 * lineBreak property no longer inherits by default
Changes in build 368 (2009/02/10)
 * Fix for RTE that happens after cancelling an operation (calling preventDefault on a FlowOperationEvent).
Changes in build 367 (2009/02/09)
 * ported to Flex 4.0.0.4836. All SWCs now build with this SDK.
Changes in build 366 (2009/02/06)
 * FlowGroupElement addChild, addChildAt and replaceChildren methods now automatically delete new elements from any existing parents. Previously the code would test for parent on new elements and throw.
 * mxmlChildren FlowElement property which is normally used for mxml compilation of TextFlow objects now always deletes existing children
 * Fix a memory leak issue with the TextLayoutFormat cache
 * Fix cascade bug with non-inheriting attributes getting inherited
Changes in build 365 (2009/02/05)
 * Changed TextLayoutFormat.backgroundColor to allow setting value of "transparent" (now the default). Because of this new value for backgroundColor, backgroundAlpha now defaults to 1.
Changes in build 364 (2009/02/04)
 * Performance improvement for handling of TextFlow.hostTextLayoutFormat. The code now assumes that once set by the client the supplied object won't be changed. This avoids a copy.
Changes in build 363 (2009/02/03)
 * Performance work. Remove getCanonical from TextLayoutFormat.
 * Fix for RTE cancelling SplitParagraphOperation.
 * Fixing some float bugs.

Try searching discussions--see: http://discussions.apple.com/thread.jspa?threadID=684662
only caveat is link is dated-I googled for newer...
MacBook Pro 17" Mac mini (Intel) Mac OS X (10.4.8)

ContactSheet X (CSX) v1.4 has been released

ContactSheet X (CSX) v1.4 has been released.
The biggest change with this rev is the addition of PSCS4
support. Other changes include better support for metadata in captions
and templates, improved color profile handling, and improved error
handling. A complete list can be found in the Release Notes link
below.
Download Page
https://sourceforge.net/project/showfiles.php?group_id=173281&package_id=207621
Release Notes and Change Log
https://sourceforge.net/project/shownotes.php?group_id=173281&release_id=641810
Home Page (includes link to PDF docs)
http://ps-scripts.sourceforge.net/ContactSheetX/csx.html
This has been tested on PSCS3/4 on OS X and XP. It may still work with
CS2, I just haven't tested it there this time around.
As always, let me know if you find any problems.
-X

[email protected] wrote:
> I ran this script but I am running into a problem. How come it only does the first five documents in the folder. It will not do that rest. Is there something I have to modify?
Email me me the ContactSheetX.log file (see the README file for its location on
your system) and I'll see if I can determine what's going wrong.
-X (xbytor at gmail dot com)

CSX v1.4b4

I uploaded what I hope will be the last 1.4 beta for ContactSheetX
https://sourceforge.net/project/showfiles.php?group_id=173281&package_id=207621
Here's the relevant chunk from the ChangeLog.
v1.4b4
Fixed formatting bug for GPS metadata.
Fixed Bridge sort order bug.
Fixed Color Profile settings visibility problem on Document panel.
Fixed error related to sheet post-processing.
Added improved error handling and reporting.
Fixed vertical caption alignment bug for multi-line captions.
Simplified CSXBridge implementation, especially for CS3+.
Added Middle to caption vertical alignment.
v1.4b2
Added 'Color Profile' to Document panel. Removed 'convertToProfile' and
'forceProfileMatch. from Advanced panel.
Reworked Progress Bar interaction so that Cancel now terminates the
script after the current image has been processed.
Renamed 'rasterizedThumbs' to 'embedSmartObjects'.
Added code for eventual CS4 port.
Fixed CS2 compatibility problems.
v1.4b1
Added ability to extract all metadata from an image file via Bridge
without having to open the image. This greatly speeds things up when
captions have embedded metadata.
Fixed bug where ° symbol in the default gpsFormat setting was
getting bashed.
Added @Metadata substitution layers. Needs docs and a sample template.
Greatly improved quality of thumbs by reworking SmartObject code. This
is very noticable with large source images.
Fixed a bug with Lab and Grayscale document modes not working.
Added ContactSheet-UI.log to help trackdown errors in the UI.
Added 'Show Previous Log' button on Advanced panel to show the
log file contents from the last run.
Removed logFile and logEnabled from Advanced panel. These values are
now hardwired in the script.
Fixed bug involving saving some of the settings from the Outpanel
when Save Sheet is off and Keep Sheet Open is on.
Added MS-Intuitive-Sort of filenames (xpSort = true). The setting is on
the 'Advanced' panel.
Keep thumbnails as smart objects when placed (rasterizeThumbs = false).
Added ability to disable date/gps formatting for caption fields by
prefixing EXIF, XMP or IPTC tags with a '-'. This allows the raw field
value to be passed through. Ex: %E{-DateTimeOriginal}
Moved logging so that it starts immediately (before conversion
of UI options).
Improved diagnostics for post-validation/pre-processing phase.
Fixed a potential localization problem on the Mac for HP modes that
run external applications.
Fixed bug where the script would not recurse into folders more than
2 deep in some situations.
Added support in InstallCSX for localized (non-English) versions of
Photoshop.
-X
for photoshop scripting solutions of all sorts
contact: [email protected]

Thanks for the heads-up on Your improved Script.
Have a nice weekend

Improved Metadata Handling?

Similar Messages

Maybe you are looking for