[svn:fx-trunk] 10925: Redo the implementation of dragging & selection being handled upon mouseDown in List .

Revision: 10925
Author:   [email protected]
Date:     2009-10-07 18:52:06 -0700 (Wed, 07 Oct 2009)
Log Message:
Redo the implementation of dragging & selection being handled upon mouseDown in List. Evtim will fix up the behavior such that in a multi-select action, mousing down in a selected item will drag the selected set while mousing down in a non-selected item will select that item anew.
QA: Yes, but don't include in those 3 tests till Evtim checks in, hopefully tomorrow
Doc: No
Checkintests: Pass
Other tests: List tests pass, List D&D tests pass with 3 exclusions.
Noteworthy for Integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DropDownList.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as

Similar Messages

Hi, This was not what I meant. The requirement is: Drag and drop any one of specific list

Hi,
This was not what I meant.
The requirement is:
Drag and drop any one of specific list of components say x, y,z in the parsys
Only after the drag and drop of these components other components can be dragged to the parsys. So we can say that the parsys should allow only the specific components to be added first and only after that other components can be added.
Thanks ,
Dipti

Hi there
I'm guessing that you mean to ask if one is able to force a user to perform a drag-and-drop as part of a simulation?
Unless you program it in Flash or some other application it isn't avaiable. Check the link below for more.
Click here to view
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

[svn:fx-3.x] 12371: The main AccImpl was updated to handle accessible naming conventions differently than before .

Revision: 12371
Revision: 12371
Author:   [email protected]
Date:     2009-12-02 08:51:12 -0800 (Wed, 02 Dec 2009)
Log Message:
The main AccImpl was updated to handle accessible naming conventions differently than before. This change was made to make the 3.x branch consistent with the trunk changes. The updated methods allows the accessibilityName property to overwrite the logic that was previously used to build the accessible name for components that were inside of forms. This method also provides a method to allow developers to specificy that no form heading or form item label should be included in the accessibilityName for the form field by using a space.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as

Revision: 12371
Revision: 12371
Author:   [email protected]
Date:     2009-12-02 08:51:12 -0800 (Wed, 02 Dec 2009)
Log Message:
The main AccImpl was updated to handle accessible naming conventions differently than before. This change was made to make the 3.x branch consistent with the trunk changes. The updated methods allows the accessibilityName property to overwrite the logic that was previously used to build the accessible name for components that were inside of forms. This method also provides a method to allow developers to specificy that no form heading or form item label should be included in the accessibilityName for the form field by using a space.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/accessibility/AccImpl.as

[svn:fx-trunk] 12827: Removed the accessibility implementation for WindowAccImpl and WindowedApplicationAccImpl as they are likely not needed .

Revision: 12827
Revision: 12827
Author:   [email protected]
Date:     2009-12-10 19:03:29 -0800 (Thu, 10 Dec 2009)
Log Message:
Removed the accessibility implementation for WindowAccImpl and WindowedApplicationAccImpl as they are likely not needed. In their current form they were preventing the accessibility of child components from being exposed.
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Removed Paths:
    flex/sdk/trunk/frameworks/projects/airspark/src/spark/accessibility/WindowAccImpl.as
    flex/sdk/trunk/frameworks/projects/airspark/src/spark/accessibility/WindowedApplicationAc cImpl.as

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn:fx-trunk] 10076: Redo fix for SDK-23080, since the last one introduced more problems.

Revision: 10076
Author:   [email protected]
Date:     2009-09-08 18:04:12 -0700 (Tue, 08 Sep 2009)
Log Message:
Redo fix for SDK-23080, since the last one introduced more problems.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23080
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RectangularDropShadow.as

If you're still using Buckminster 3.6, I strongly suggest switching to 3.7 - it has a number of bug fixes and improvements. This applies to both headless, and the IDE (assuming Eclipse 3.7 Indigo).
Matthew

[svn:fx-trunk] 7581: -Redo workaround for SDK21552.

Revision: 7581
Author:   [email protected]
Date:     2009-06-05 09:54:24 -0700 (Fri, 05 Jun 2009)
Log Message:
-Redo workaround for SDK21552. It turns out that in AIR all keyboard events are cancelable so blindly calling event.preventDefault() after the TCM keyDownHandler has processed the event results in the default behavior for normal keys being canceled - hence no text gets inserted. It also turns out that our SystemManager.keyDownHandler is converting the keyDown events for the set of nav keys used by the scroller into cancelable events. For the player, normal keys are not cancelable so blindly calling preventDefault() only canceled the nav keys which is what we wanted.
- Remove a no longer needed check in the text setter since TCM.setText() now does the check.
QA Notes:
Doc Notes:
Bugs: SDK-21580
Reviewers: Gordon
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21580
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/supportClasses/RichEditable TextContainerManager.as

[svn:fx-trunk] 10151: Modified the Channel.applySettings() ASDoc comment.

Revision: 10151
Author:   [email protected]
Date:     2009-09-11 06:20:44 -0700 (Fri, 11 Sep 2009)
Log Message:
Modified the Channel.applySettings() ASDoc comment. Removed the XML snippet for the method parameter, which wasn't relevant to the primary way this method is used. This method is primarily used in our channel subclasses to add settings specific to those channels and then call super to get the base channel settings. If a developer creates a custom channel class, the developer could use it in the same way, but would be setting the applySettings() method on the custom channel class with properties specific to the custom channel implementation. This change addresses bug BLZ-294.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-294
Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/Channel.as

[svn:fx-trunk] 11314: add the empty properties file to svn to fix the build .properties

Revision: 11314
Author:   [email protected]
Date:     2009-10-30 10:38:34 -0700 (Fri, 30 Oct 2009)
Log Message:
add the empty properties file to svn to fix the build.properties
QE notes:
Doc notes:
Bugs: fix the build
Reviewer: Pete
Tests run: checkintests
Is noteworthy for integration: no
Added Paths:
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/de_DE/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/fr_FR/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ja_JP/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ru_RU/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/zh_CN/empty.properties

Thats good news.

[svn:bz-trunk] 11030: Tweak the deserialization of ASObjects to treat an empty string for the type of an object as null .

Revision: 11030
Author:   [email protected]
Date:     2009-10-20 11:35:02 -0700 (Tue, 20 Oct 2009)
Log Message:
Tweak the deserialization of ASObjects to treat an empty string for the type of an object as null. It appears that there is some logic in the LC remoting code that relies on a non-null class name to always exist. This change reverts to the old behavior of not allowing empty string as a value for the ASObject.namedType.
This should fix bug 2448442 and its duplicates caused by the recent serialization changes.
I don't think this is the perfect fix. Pending further investigation, a better fix would be either:
a. If it's OK to assume that empty string should always mean null for the type of the ASObject, the code that enforces it should be in the setter/getter inside ASObject and not in the deserializer.
b. ASObject doesn't guarantee that a named type exists or is valid. In that sense an empty string is as bad as some random characters that cannot be a valid class name in java, so depending on how disruptive it may be, the fix should be in any logic that uses ASObject.getType().
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java

Hi Pavan,
"In your payload there is no namespace prefix for the elements under PayloadHeader element."
Yes, you are right - but this message is standard AQ Adapter Header message - it's not defined by me. I just used message which was automatically added to my project when I have defined AQ Adapter.
"In your process is the default namespace is same as namespace value of tns ??"
Do you mean targetNamespace? If yes it's different as it points to process "targetNamespace="http://xmlns.oracle.com/PF_SOA_jws/PF_APPS/APPS_PROCESS" (names of application and process have changed as I try different ways to do that)
ns1 is: xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/aq/PF_SOA/PF_APPS/PO_AQ"
"another thing is tns and ns1 should have same values.."
When I create a variable of header type, namespace ns1 is automatically created for it. I set it as property of receive activity. When process is instantiated on the serwer I get the error in which you can see that namespace is tns.
Maybe I'm doing something wrong but I don't see how I could fix this in my process.
You can see that the message I get on the server has nothing in common with the application/project/process names. Is it possible to define such variable?
Regards
Pawel
PS:
In Transformation xsl file, both variables (source and target) has tns namespace for Header and PayloadHeader, and no namespace for subfields.
Edited by: pawel.fidelus on 2010-01-05 02:37

[svn:fx-trunk] 9407: Reordering the if-statement in isMeasureFixed() exposed that hostFormat can be null when measure() is called if styles changed and measure is done before the next commitProperties .

Revision: 9407
Author:   [email protected]
Date:     2009-08-19 15:11:34 -0700 (Wed, 19 Aug 2009)
Log Message:
Reordering the if-statement in isMeasureFixed() exposed that hostFormat can be null when measure() is called if styles changed and measure is done before the next commitProperties. This states test exposed this.
We should rethink if we want to clear hostFormat rather than have a hostFormatChanged flag. If there is no hostFormat at measure then it has to be fixed because there is no line break format to check for auto-size.
QE notes:
Doc notes:
Bugs: SDK-22779
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22779
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/RichEditableText.as

Oh my god, it is too long! You definitely check out types, casting and especially ODP.Net (it does everything for you)... etc. They can help you to simplify your code. I do not have enough time to copy paste it to Studio and understand and solve your issue, so I got title of your message as your main question.
In Oracle, you can create an autonumber field by using sequences object. This is really useful when you need to create a unique number to act as a primary key.
Basically you can create a sequence simply typing;
CREATE SEQUENCE MY_SEQUENCE;
now you have a sequence called "MY_SEQUENCE"... Then, I advice you select a number from sequence;
select MY_SEQUENCE.nextval from dual;
I said I advice actually kinda must, although it called sequence, I cannot be sequential. Do not even try to predict the value. You can be sure that it is unique number so you can use it.
Then insert you record and use that number part of your primary key. I think that's it. Have fun.

[svn:bz-trunk] 17772: Update the url in the tests to use a relative path instead of the default localhost : 8400 so that the tests can pass on appservers other than the default Tomcat .

Revision: 17772
Revision: 17772
Author:   [email protected]
Date:     2010-09-20 15:02:50 -0700 (Mon, 20 Sep 2010)
Log Message:
Update the url in the tests to use a relative path instead of the default localhost:8400 so that the tests can pass on appservers other than the default Tomcat.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml

Revision: 17772
Revision: 17772
Author:   [email protected]
Date:     2010-09-20 15:02:50 -0700 (Mon, 20 Sep 2010)
Log Message:
Update the url in the tests to use a relative path instead of the default localhost:8400 so that the tests can pass on appservers other than the default Tomcat.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml

[svn:fx-trunk] 16385: -removed the utilities package target since it' s not used any longer - at least what is contained in this target.

Revision: 16385
Revision: 16385
Author:   [email protected]
Date:     2010-06-01 13:32:35 -0700 (Tue, 01 Jun 2010)
Log Message:
-removed the utilities package target since it's not used any longer - at least what is contained in this target. I believe this was a leftover from flex 2 days.
-fix up the packaging targets to ensure they are being properly built. I removed depends="temp-clean" and inserted antcall target="temp-clean" because a target gets executed only once, even when more than one target depends on it.
QE notes:
Doc notes: no
Bugs: no
Reviewer: Guarav
Tests run: no
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/build.xml

http://blogs.adobe.com/jkost/2014/06/installing-the-2014-release-of-creative-cloud.html
-This messages says (at least some) CC 2014 programs use NEW plugins https://forums.adobe.com/thread/1499663
-so do not uninstall the older CC programs if you use plugins in your programs until you are sure you have plugins that work in CC2014
If you are sure you don't need the old CC programs
-http://helpx.adobe.com/creative-cloud/help/install-apps.html to install or uninstall

[svn:bz-trunk] 22429: Adding the default fallback of serializer and deserializer classes to amf deserializer and amf serializer

Revision: 22429
Revision: 22429
Author:   [email protected]
Date:     2011-09-07 08:04:46 -0700 (Wed, 07 Sep 2011)
Log Message:
Adding the default fallback of serializer and deserializer classes to amf deserializer and amf serializer
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/SerializationContext.java

[svn:fx-trunk] 10602: -include the flex-sdk-description in the mpl package

Revision: 10602
Author:   [email protected]
Date:     2009-09-25 14:27:02 -0700 (Fri, 25 Sep 2009)
Log Message:
-include the flex-sdk-description in the mpl package
bug: sdk-22539
-fix up the build.xml that we include in the packaged sdk. This has no bearing on building the sdk, but only when someone wants to rebuild the swcs from within a packaged sdk.
bug:sdk-23302
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22539
    http://bugs.adobe.com/jira/browse/sdk-23302
Modified Paths:
    flex/sdk/trunk/build.xml
    flex/sdk/trunk/frameworks/build_framework.xml

[svn:fx-trunk] 11276: Turning the default of ItemRenderer' s autoDrawBackground property to true.

Revision: 11276
Author:   [email protected]
Date:     2009-10-29 13:25:24 -0700 (Thu, 29 Oct 2009)
Log Message:
Turning the default of ItemRenderer's autoDrawBackground property to true. This is part of the changes outlined here: http://opensource.adobe.com/wiki/display/flexsdk/ItemRendererChanges
This will break existing ItemRenderers because now we are drawing a rectangular background for rollover/selection/caretting that was not being drawn before. Existing item renderers should be updated to either opt out of this new behavior by explicitly setting autoDrawBackground to false or by updating their ItemRenderers to expect this behavior.
QE notes: Most tests should have already been updated. If tests with item renderers are broken, please update them.
Doc notes: -
Bugs: -
Reviewer: Pete F.
Tests run: checkintests
Is noteworthy for integration: Yes
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ItemRenderer .as

Gordon, it looks like its been a while since you made this post. Not sure how valid it is now...   I am particularly interested in the LigatureLevel.NONE value. It seems that it is no longer supported.
How do I turn of ligatures in the font rendering?
My flex project involves trying to match the font rendering of Apache's Batik rendering of SVG and ligatures have been turned off in that codebase. Is there any way (even roundabout) to turn ligatures off in flash?
Thanks,
Om

[svn:fx-trunk] 10925: Redo the implementation of dragging & selection being handled upon mouseDown in List .

Similar Messages

Maybe you are looking for