[svn:fx-trunk] 11378: Rearrange exisiting TLF sources to be in the same structure as the new drop we 're about to take so that we can maintain the change history.

Revision: 11378
Author:   [email protected]
Date:     2009-11-02 12:43:46 -0800 (Mon, 02 Nov 2009)
Log Message:
Rearrange exisiting TLF sources to be in the same structure as the new drop we're about to take so that we can maintain the change history.
QE notes:
Doc notes:
Bugs:
Reviewer:
Tests run: checkintests, TextArea
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/manifest.xml
    flex/sdk/trunk/frameworks/projects/textLayout/src/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flash/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/BuildInfo.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/CoreClasses.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/EditClasses.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/acc/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/compose/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/container/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/container/TextContain erManager.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/debug/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/EditManager.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/ElementRange.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/IEditManager.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/IMEClient.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/Mark.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/ParaEdit.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/SelectionFormatS tate.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/SelectionManager .as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/TextClipboard.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/TextFlowEdit.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/edit/TextScrap.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/elements/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/events/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/events/FlowOperationE vent.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/events/SelectionEvent .as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/external/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/factory/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/formats/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/operations/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/property/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/tlf_internal.as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/utils/
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/textLayout/utils/NavigationUtil. as
    flex/sdk/trunk/frameworks/projects/textLayout/src/flashx/undo/
Removed Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/

Similar Messages

My iPhone 4 has lost SIM connection several times over the past week when the phone is left on continually. I have had the SIM checked and it was not the source of the problem. I have found that I can reactivate the SIM by switching the phone off and on.

My iPhone 4 has lost SIM connection several times over the past week when the phone is left on continually. I have had the SIM checked and it was not the source of the problem. I have found that I can reactivate the SIM by switching the phone off and on again. Has anyone else experienced this problem and if so, is there an easy fix. I have been advised by Apple that the latest IOS update may overcome this situation but I'm only on slow download speeds and 690 Mb would take forever. I would appreciate any advice.
Best regards,
Rob.

PinguXeF wrote:
, while I have taken a backup of the iTunes Library,
this means nothing if it was not done correctly...
To have EVERYTHING on a New Computer...
From your OLD computer...
Copy your ENTIRE iTunes FOLDER to an External Drive... and then from the External Drive to your New Computer..
Full Details Here > http://support.apple.com/kb/HT1751

[svn:bz-trunk] 21277: Added ds-console source to package-oem and removed copy command for datavisualization .swc which doesn't exist in the specified location.

Revision: 21277
Revision: 21277
Author:   [email protected]
Date:     2011-05-18 11:35:28 -0700 (Wed, 18 May 2011)
Log Message:
Added ds-console source to package-oem and removed copy command for datavisualization.swc which doesn't exist in the specified location. I do not find it in the most recent package-oem.zip neither
Modified Paths:
    blazeds/trunk/build.xml

Gusar wrote:No, it's not. I have actually seen cases where software rendering gave a higher glxgears score than hardware rendering (and no, it wasn't about vsync). Of course, with *actual* apps on the same machine, software rendering sucked compared to hardware rendering.
Please do not jump to conclusions and make assumptions here like 'when will people finally get it??'. I never said it was a benchmark. I have also seen many examples of where it's results do not go with conventional performance. I have a Radeon 9000 that goes faster on glxgears than a Geforce FX 5600 running Nouveau. Which is the faster card? The FX by miles. It is not a benchmark as it can not be compared between configurations. What I know is that on this individual system, from prior experience over many years when 3D acceleration is working glxgears gets between 300 and 400 fps. When it is not working it gets less than 10. That is a fact but does not mean it is benchmarkable. Yes, a Quake 3 timedemo (I have these numbers too and they very much correlate to glxgears performance for this system given just how slow it is) would be a benchmark but when it runs less than 0.1fps and even the 2D rendering means that navigating the menu is impossible, there just isn't the time to find out. Hence if playing around with drivers on this system I would use glxgears to check that 3D acceleration is working but not to benchmark. Glxinfo does not give you all this evidence.
But to clarify, I wouldn't use glxgears as a benchmark, benchmarking is different and I do a lot of that too.

[svn:fx-trunk] 10505: Update to TLF Build 516.

Revision: 10505
Author:   [email protected]
Date:     2009-09-22 10:35:30 -0700 (Tue, 22 Sep 2009)
Log Message:
Update to TLF Build 516. See textLayout/ReleaseNotes.txt.
Updated build file so the manifest for textLayout_edit is removed since TLF did it with their build file.
QE notes:
Doc notes:
Bugs:
Reviewer: Gordon asked me to do this
Tests run: checkintests, TextInput, TextArea, RichText
Is noteworthy for integration: yes
Modified Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/ReleaseNotes.txt
    flex/sdk/trunk/frameworks/projects/textLayout/build.xml
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/BaseTextLayoutImporter.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/HtmlExporter.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/HtmlImporter.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/TextConverter.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_conversion/src/flashx/textLayout /conversion/TextLayoutImporter.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/manifest.xml
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/Build Info.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/BaseCompose.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/ComposeState.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/ParcelList.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/SimpleCompose.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/StandardFlowComposer.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/compo se/TextFlowLine.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/conta iner/ColumnState.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/conta iner/ContainerController.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/debug /Debugging.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/FlowElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/FlowGroupElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/FlowLeafElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/ParagraphElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/SpanElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/TCYElement.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/TextFlow.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/ITabStopFormat.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/ITextLayoutFormat.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TabStopFormat.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TabStopFormatInc.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TextLayoutFormat.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TextLayoutFormatInc.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/forma ts/TextLayoutFormatValueHolder.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/textLayout/EditC lasses.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/textLayout/edit/ SelectionManager.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/textLayout/opera tions/DeleteTextOperation.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_edit/src/flashx/undo/UndoManager .as
    flex/sdk/trunk/frameworks/projects/textLayout/tlf.properties
Removed Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkActiveFormat.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkHoverFormat.as
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_core/src/flashx/textLayout/eleme nts/LinkNormalFormat.as

[svn:fx-trunk] 13964: Work around TLF bug #2545307.

Revision: 13964
Revision: 13964
Author:   [email protected]
Date:     2010-02-03 11:47:06 -0800 (Wed, 03 Feb 2010)
Log Message:
Work around TLF bug #2545307. ContainerController.mouseWheelHandler() should be checking if the default behavior is prevented before it acts on the event. The workaround is to override TextContainerManager.mouseWheelHandler(), which dispatches to ContainerController.mouseWheelHandler(), and only call it if event.isDefaultPrevented() is false.
QE notes:
Doc notes:
Bugs: SDK-25291, Watson #2545307
Reviewer: Hans
Tests run: checkintests
Is noteworthy for integration:
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-25291
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

[svn:fx-trunk] 8563: When integrating TLF Build 468, the scrapToPaste() method of PasteOperation needs to be replaced by textScrap.clone(), not just textScrap.

Revision: 8563
Author:   [email protected]
Date:     2009-07-14 14:47:50 -0700 (Tue, 14 Jul 2009)
Log Message:
When integrating TLF Build 468, the scrapToPaste() method of PasteOperation needs to be replaced by textScrap.clone(), not just textScrap.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Carol to review
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/RichEditableText.as

[svn:fx-trunk] 7071: Providing assignable lvalue context while parsing rvalues in preparation to fix bugs such as SDK-17748 and SDK-18877 .

Revision: 7071
Author:   [email protected]
Date:     2009-05-19 08:17:09 -0700 (Tue, 19 May 2009)
Log Message:
Providing assignable lvalue context while parsing rvalues in preparation to fix bugs such as SDK-17748 and SDK-18877. This change makes the compiler aware of a new piece of metadata . When parsing text values, this metadata instructs the TextParser to not look for literal syntax for Arrays, Booleans, Numbers, etc... and instead just treat the content as String. However, it will still honor { } binding syntax and @function syntax.
Once TLF and Gumbo text components are updated to use this metadata on the appropriate properties we will be able to close the bugs mentioned above.
QE: Not yet
Doc: No
Checkintests: Pass
Cyclone Tests: Mxunit, Mxunit - compc, Mxunit - rsl, Mxmlcunit, Compiler api all pass.
Reviewer: Paul
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17748
    http://bugs.adobe.com/jira/browse/SDK-18877
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ArrayBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/PrimitiveBuilder.jav a
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/VectorBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/NodeTypeResolver.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/TextParser.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/ValueNodeHandler.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/Effect.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/Property.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/Style.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/TypeTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/StatesModel.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties
Added Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/Assignable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/DynamicProperty.java

[svn:fx-trunk] 11466: For now keep the name of the textLayout rsl the same as it is in flex-config .xml.

Revision: 11466
Author:   [email protected]
Date:     2009-11-05 08:22:15 -0800 (Thu, 05 Nov 2009)
Log Message:
For now keep the name of the textLayout rsl the same as it is in flex-config.xml. Jim will follow behind me and do the necessary build work to keep the name TLF gives it which is textLayout_1.0.0.buildNumber.swf.
QE notes:
Doc notes:
Bugs:
Reviewer:
Tests run:
Is noteworthy for integration: no
Added Paths:
    flex/sdk/trunk/frameworks/rsls/
    flex/sdk/trunk/frameworks/rsls/textLayout_4.0.0.0.swf

[svn:bz-trunk] 13746: Bug: LCDS-952

Revision: 13746
Revision: 13746
Author:   [email protected]
Date:     2010-01-25 07:44:49 -0800 (Mon, 25 Jan 2010)
Log Message:
Bug: LCDS-952
QA: Yes - please make sure that:
-This change didn't cause any regressions. Last time, it caused some issues but we don't seem to remember what they were.
-Make sure the max limit is being enforced and the JVM option to change it actually works.
Doc: Yes, might want to document about default max string length of 25MB and the JVM option to change it.
Checkintests: Pass
Details: Limited maximum incoming string length to 25MB by default. Also provided a JVM option called max-string-bytes that one can use to change this limit (using -Dmax-string-bytes=1000 for example).
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-952
Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/errors.properties
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java

[svn:fx-trunk] 10214: This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList - damageHandler - invalidateDisplaylist - back to updateDisplayList.

Revision: 10214
Author:   [email protected]
Date:     2009-09-13 07:33:58 -0700 (Sun, 13 Sep 2009)
Log Message:
This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList -> damageHandler -> invalidateDisplaylist -> back to updateDisplayList. The bug file was for TextArea which is RET but the same bug was in RichText as well.
This example with a renderer exposed it because the typicalItem that is composed to figure out sizes and the actual first item in the list share the same textFlow. It actually has nothing to do with useVirtualDisplay other than it was sharing a textFlow.
It turns out that the TextFlowFactory dispatches damage events every time the textFlow is composed. Unlike when the flowComposer is used, it always considers the flow damaged. It was exacerbated by each of the two components having a damage handler for the same textFlow.
The solution is to use the textFlow generation number. In the damageHandler if the generation is the last known generation number, assume no changes, and return immediately from the damage handler.
QE notes: There are 1 TextArea, 6 TextInput and 2 NumericStepper failuers, with or without my changes. The common link seems to be DispatchKeyEvent. Most were testing maxChar, displayAsPassword and restrict. I tested these and they seem to be working correctly.
Doc notes:
Bugs: SDK-23002
Reviewer: Gordon
Tests run: checkintests, TextArea, TextInput and NumericStepper
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23002
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

Revision: 10214
Author:   [email protected]
Date:     2009-09-13 07:33:58 -0700 (Sun, 13 Sep 2009)
Log Message:
This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList -> damageHandler -> invalidateDisplaylist -> back to updateDisplayList. The bug file was for TextArea which is RET but the same bug was in RichText as well.
This example with a renderer exposed it because the typicalItem that is composed to figure out sizes and the actual first item in the list share the same textFlow. It actually has nothing to do with useVirtualDisplay other than it was sharing a textFlow.
It turns out that the TextFlowFactory dispatches damage events every time the textFlow is composed. Unlike when the flowComposer is used, it always considers the flow damaged. It was exacerbated by each of the two components having a damage handler for the same textFlow.
The solution is to use the textFlow generation number. In the damageHandler if the generation is the last known generation number, assume no changes, and return immediately from the damage handler.
QE notes: There are 1 TextArea, 6 TextInput and 2 NumericStepper failuers, with or without my changes. The common link seems to be DispatchKeyEvent. Most were testing maxChar, displayAsPassword and restrict. I tested these and they seem to be working correctly.
Doc notes:
Bugs: SDK-23002
Reviewer: Gordon
Tests run: checkintests, TextArea, TextInput and NumericStepper
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23002
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

[svn:bz-trunk] 18821: Check-in a minor fix that deals with a missing MessageBroker class ( this could happen in Java/Android clients).

Revision: 18821
Revision: 18821
Author:   [email protected]
Date:     2010-11-26 07:33:24 -0800 (Fri, 26 Nov 2010)
Log Message:
Check-in a minor fix that deals with a missing MessageBroker class (this could happen in Java/Android clients).
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageException.java

I see some message about a proxy. Have you checked that you can use the proxy from you network?
If not you should turn the proxy off.
Timo

[svn:fx-trunk] 12985: Add metadata. xml for the SWC themes so that if Builder imports them they have nice names , etc.

Revision: 12985
Revision: 12985
Author:   [email protected]
Date:     2009-12-15 23:20:44 -0800 (Tue, 15 Dec 2009)
Log Message:
Add metadata.xml for the SWC themes so that if Builder imports them they have nice names, etc. These need to be updated by the Builder team if we end up changing how sourceLocation works, etc. Also would be good if we added metadata.xml for the CSS versions.
Modified Paths:
    flex/sdk/trunk/samples/themes/arcade/build.xml
    flex/sdk/trunk/samples/themes/cobalt/build.xml
    flex/sdk/trunk/samples/themes/graphite/build.xml
    flex/sdk/trunk/samples/themes/zen/build.xml
Added Paths:
    flex/sdk/trunk/samples/themes/arcade/src/metadata.xml
    flex/sdk/trunk/samples/themes/cobalt/src/metadata.xml
    flex/sdk/trunk/samples/themes/graphite/src/metadata.xml
    flex/sdk/trunk/samples/themes/zen/src/metadata.xml

Note the last paragraph in the original post which explains how Flickr handles resolution changes without breaking the rectangles. Perhaps a more straightforward approach would be to store both the rectangle coordinates for each rectangle AND the image's width and height at the time the rectangles were created. Then if the image is scaled, the rectangles can be scaled accordingly. For example, if a rectangle is at x=100,y=200,w=50,h=70, the "original dimensions" are 1000x2000, and the image's current dimensions are 500x1000, then an application could assume the image has been scaled down by (500/1000=) 0.50, and so the x,y,w,h of each rectangle could also be multiplied by 0.50 (x=50,y=100,w=25,h=35). I'd recommend storing floating-point values so that multiple scalings don't make the rectangles "creep".
Of course, it is possible that really the image was cropped rather than scaled, but fairly unlikely you would happen to crop it the same percent in both directions. Even if an image is cropped, someone could manually repair the rectangles by sliding and scaling them until the fit back on the faces (unless most of the faces were cropped off).
A rectangle-aware application could scale and translate the rectangles during a crop or scaling operation, but other applications could still survive scaling if they at least preserve the XMP tags as-is.

E-sourcing couldn't send out E-mail notification of new user.

Dear experts,
I got stuck on SMTP issue when configuring a E-sourcing sandbox, when I created some Buy-side users, the system was not able to send out the notifications but all stuck in "Queued Messages" .
I browsed in the system, the settings related with the SMTP function including below items:
1: "Source Email" in Company Properties, this email address is going to be indicated as the sender of a new user notification;
2: "Messaging" configuration in System Properties:
( messaging messaging.smtp.mailhost
messaging messaging.smtp.password
messaging messaging.smtp.username )
I have set up above fields as the same as a working E-sourcing application, but my sandbox still doesn't work for me, the new user created can't receive the notification to become a valid user of the system, so they will not be able to logon to the system without password information.
Would you please advice me what should I do, any of your response in highly appreciated!
Thanks and best regards!
edward.

Edward,
Please verify a couple of things:
1. Is the functional e-sourcing box is running on the same version of Sandbox version (which you are configuring)
2. Verify that "New User" notification template is set to active in the email templates setting through setup
3. If no issues with 1 and 2 then would suggest to clear mail queue from backend and try generating a new email
Please let us know the out come.
Good Luck.

No mapping for Same structure in source and target

Hi Experts,
I want to transfer the source structure to two receivers . Here source and target structures are same so i dont need mapping.
My question is how many DT,MT and MI required .. mapping required or not.
Thanks in Advance
CS

hi CS,
here in your scenario as u have told that source and reciver are of same structure . definitely you didn't need any mapping . and you have to create two data type(one for sender and one for receiver) , two message types(one for sender and one for receiver)) , and two message interfaces(one for sender and one for receiver).
while creating message types it asks for data type and while creating message interface it asks for message type only . as the structures of sender and receiver are same then inspite of having two receivers we have to create ony one message interface on sender side . later the adapter will take care of further proceedings
but in case of configuration you have to import three business systems . one for sender and two for receiver systems . and you have to configure the communications channels accordingly. as per the receivers accepting the structures you have to use the relevant adaptors .

Can source and target tables be the same

Hi there,
I need to restate profit center column in the delivery fact table. Historical Profit Centers need to be populated since today is the first time we brought in Profit Center field from LIPS table. The source for the delivery fact table is SAP LIPS table. so what I did is:
joined the LIPS and delivery fact table on (LIPS.delivery number = deliveryfacttable.delivery number & LIPS.delivery line item number = deliveryfacttable.delivery line item number) to get the profit center.
So the source and the target delivery fact table are the same. Is this a good practice becuase Data services warns me that the source and target tables are the same.
Please let me know a better alternative approach to this OR a better approach to restate fields for historical data. Thanks in advance.
Regards,
samqiue

Arun,
actually the LIPS resides on another server and in order to fetch data I have to write an R3 ABAP data flow, so I cant use it directly in a lookup.
Except what Im thinking based on your reply to use a lookup table is: that I will extract 3 colums (delivery number, delivery line item number and profit center) to a table and then use the lookup.
Thanks.
Regards,
samique

[svn:fx-trunk] 11378: Rearrange exisiting TLF sources to be in the same structure as the new drop we 're about to take so that we can maintain the change history.

Similar Messages

Maybe you are looking for