[svn:fx-gumbo_beta2] 10472: Fix for Fade bug.

Revision: 10472
Author:   [email protected]
Date:     2009-09-21 15:11:11 -0700 (Mon, 21 Sep 2009)
Log Message:
Fix for Fade bug. Previously, Fade assumed that any target object with a 'parent' must be a child of that container. However, a target object can also be the 'mask' property of that parent. When Fade went to query which element the mask was on the parent, the parent threw an RTE because its element list did not contain that target object. The fix was to special-case the mask situation and return 'undefined' for the index value, meaning that the object does not have a parent and will not be tracked as an element that can be removed/added.
QE notes: None
Doc notes: None
Bugs: SDK-23327
Reviewer: Jason
Tests run: checkintests, Mustella effects/Fade, manual tests
Is noteworthy for integration: Yes
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23327
Modified Paths:
    flex/sdk/branches/gumbo_beta2/frameworks/projects/spark/src/spark/effects/Fade.as

Similar Messages

  • [svn:fx-trunk] 10898: Fix for a bug: After playing a hide effect, a window wouldn't be visible again.

    Revision: 10898
    Author:   [email protected]
    Date:     2009-10-06 13:54:04 -0700 (Tue, 06 Oct 2009)
    Log Message:
    Fix for a bug: After playing a hide effect, a window wouldn't be visible again.
    The issue here is that all effects that occur because of HIDE end up calling setVisible() (see EffectManager.effectEndHandler).  Window/WindowedApplication was basically left with two concepts of setVisible...the displayObject one and the native application one, and they were out of synch.  So setting visible=true on the window wasn?\226?\128?\153t calling setVisible(true) which controls the display object visibility.  Now instead of doing our work in the visible setter, we override setVisible() and do it in there.
    QE notes: -
    Doc notes: -
    Bugs: SDK-23263
    Reviewer: Darrell
    Tests run: checkintests, Rob ran mustella window/windowedapplication
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23263
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/Window.as
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/Window.as
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

    I run Suse 9.1 Linux, and Suse has a package called lmsensors which by default on my machine gives readings like this:
    Code: [Select]
    temp1:       +27°C  (high =    +0°C, hyst =   +22°C)   sensor = thermistor
    temp2:     +41.0°C  (high =   +80°C, hyst =   +75°C)   sensor = PII/Celeron diode 
    Now that 41C is pretty high for an idle AMD643000+ running at 1000Mhz, 1.08V. Too high, I would say. temp 1 in this case is the SYS temp, temp2 is the CPU temp.
    Now, using lmsensors I can duplicate your little trick and tell it that temp 2 is in fact a 3904 transistor. Having done this can I get readings like this:
    Code: [Select]
    temp1:       +27°C  (high =    +0°C, hyst =   +22°C)   sensor = thermistor
    temp2:     +16.0°C  (high =   +80°C, hyst =   +75°C)   sensor = 3904 transistor 
    Problem is, I'm not sure that the sensor is actually a 3904 transistor! The number's lower, but I was pretty sure that the sensor in the AMD64 is in fact a diode. Also, surely the CPU temp can't actually be that much lower than the SYS temp.
    So, I think your fix succeeds in giving lower temps and that's great in that it will tell your system software that the CPU is not overheating, but I don't think it's the solution to high temp reporting. Anyway, as you say, its a solution for people who can't run with system shutdowns due to bogus high temps.  
    I've been looking at these temp issues with the MSI K8T, and I was thinking the problem was simply a miscalibration. The Winbond sensor chip on my board (maybe the K8N is the same, maybe not) has a sensor temp offset that gets added to the temp coming from the sensor. On the K8T this number is +54C.   Funny number I know, but I've "fixed" the problem while I wait for a real bios fix on the K8T by simply reducing this offset to give me a CPU temp that matches SYS temp when idle. This enables cool'n'quiet fan control to work properly on my system, which is my main practical concern.

  • [svn:fx-trunk] 12370: Fix for doc bug FLEXDOCS-1150

    Revision: 12370
    Revision: 12370
    Author:   [email protected]
    Date:     2009-12-02 08:48:37 -0800 (Wed, 02 Dec 2009)
    Log Message:
    Fix for doc bug FLEXDOCS-1150
    Added a few new examples and default sizes to Spark components
    QE notes: -
    Doc notes: -
    Bugs: -
    Reviewer: -
    Tests run: - FLEXDOCS-1150
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1150
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1150
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/formatters/DateFormatter.as
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/BorderCont ainerExample.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/VScrollBar Example.mxml
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Application.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/BorderContainer.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ComboBox.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DataGroup.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DropDownList.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Group.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/HGroup.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NavigatorContent.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Panel.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/SkinnableContainer.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/SkinnableDataContainer.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TabBar.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextInput.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TileGroup.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VGroup.as
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/Applicatio nContainerExample.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/HScrollBar Example.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/MyBorderSk in.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/SkinnableC ontainerExample.mxml
        flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/SkinnableD ataContainerExample.mxml

  • [svn:fx-trunk] 12187: Fixes for ASDoc bugs:

    Revision: 12187
    Revision: 12187
    Author:   [email protected]
    Date:     2009-11-24 14:14:48 -0800 (Tue, 24 Nov 2009)
    Log Message:
    Fixes for ASDoc bugs:
    Doc for a simple class with a bindable property adds IEventDispatcher methods.
    No ASDoc content for autogenerated methods and properties from the tag.
    asdoc fails with IndexOutOfBoundsException on code that compiles without warnings.
    QE notes: None
    Doc notes: None
    Reviewed By: Paul
    Bugs: SDK-23864, SDK-23941, SDK-24281
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23864
        http://bugs.adobe.com/jira/browse/SDK-23941
        http://bugs.adobe.com/jira/browse/SDK-24281
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableProperty.vm
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/managed/ManagedProperty.vm
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java

  • [svn:fx-gumbo_beta2] 10484: Fix for autoCenter problem when Move/ Resize effects are used.

    Revision: 10484
    Author:   [email protected]
    Date:     2009-09-21 19:38:14 -0700 (Mon, 21 Sep 2009)
    Log Message:
    Fix for autoCenter problem when Move/Resize effects are used. autoCenterTransform calculates the center dynamically, using the current width/height of the target. This calculation can be one frame off if a Resize effect is running in parallel with the transform effect. Also, containers do their validation lazily, so they need to be forced to validate in order to have an up-to-date width/height. This fix addresses these problems by reordering the effects in a Parallel hierarchy to put the Resize effects (and composite effects containing Resize) at the front of the set of effects and by calling validateNow() on the target of a transform effect prior to calculating the transform center (if appropriate).
    QE notes: None
    Doc notes: None
    Bugs: SDK-23306
    Reviewer: Jason
    Tests run: checkintests, Mustella spark/effects mx/effects, manual tests
    Is noteworthy for integration: Yes
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23306
    Modified Paths:
        flex/sdk/branches/gumbo_beta2/frameworks/projects/framework/src/mx/effects/effectClasses/ CompositeEffectInstance.as
        flex/sdk/branches/gumbo_beta2/frameworks/projects/framework/src/mx/effects/effectClasses/ ParallelInstance.as
        flex/sdk/branches/gumbo_beta2/frameworks/projects/spark/src/spark/effects/supportClasses/ AnimateTransformInstance.as

    Dear Pallavi,
    Very useful post!
    I am looking for similar accelerators for
    Software Inventory Accelerator
    Hardware Inventory Accelerator
    Interfaces Inventory
    Customization Assessment Accelerator
    Sizing Tool
    Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
    Request help on such accelerators... Any clues?
    Any reply, help is highly appreciated.
    Regards
    Manish Madhav

  • [svn:fx-4.x] 15123: Fix for ASDoc bugs:

    Revision: 15123
    Revision: 15123
    Author:   [email protected]
    Date:     2010-03-29 17:46:28 -0700 (Mon, 29 Mar 2010)
    Log Message:
    Fix for ASDoc bugs:
    @see links are not working in the ASDoc of a style property
    @see links in a skinPart ASDoc are not visible
    Asdoc tool generates bad links for Vector. type, property detail section
    QE notes: None.
    Doc notes: None.
    Bugs: SDK-26034, SDK-26035, SDK-26036
    Reviewed By: Darrell
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-26034
        http://bugs.adobe.com/jira/browse/SDK-26035
        http://bugs.adobe.com/jira/browse/SDK-26036
    Modified Paths:
        flex/sdk/branches/4.x/asdoc/templates/all-index.xslt
        flex/sdk/branches/4.x/asdoc/templates/class-files.xslt
        flex/sdk/branches/4.x/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGener ator.java

    Stope
    Mailing me ***
    Sent from my I phone

  • [svn:fx-trunk] 9319: Added missing ASDoc version tagging as part of fix for Watson bug 2402680.

    Revision: 9319
    Author:   [email protected]
    Date:     2009-08-14 14:38:48 -0700 (Fri, 14 Aug 2009)
    Log Message:
    Added missing ASDoc version tagging as part of fix for Watson bug 2402680. Code compiles and checkintests pass.
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ConfigMap.as
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/messages/MessagePerformanceUtils. as

    Revision: 9319
    Author:   [email protected]
    Date:     2009-08-14 14:38:48 -0700 (Fri, 14 Aug 2009)
    Log Message:
    Added missing ASDoc version tagging as part of fix for Watson bug 2402680. Code compiles and checkintests pass.
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ConfigMap.as
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/messages/MessagePerformanceUtils. as

  • Ios7 bookamrking web application to home screen via Safari crashes after login and when we try to open any link inside. Can anyone please tell me if there is any scheduled fix for this bug in safari?

    ios7 bookmarking web application to home screen via Safari, crashes after login and when we try to open any link inside from the icon that gets created on the home screen. Can anyone please tell me if there is any scheduled fix for this bug in safari?
    From what i understand i see that - Cookies are not transferred between your website and your webapp when installing the icon on the home screen (for authentication purposes for example). It was working until 6.1 and now it’s not working anymore.
    Can someone please tell me if this bug will be fixed in any future release, if so the ticket number of some kind that i can track, or if there is a workaround for this issue?

    ios7 bookmarking web application to home screen via Safari, crashes after login and when we try to open any link inside from the icon that gets created on the home screen. Can anyone please tell me if there is any scheduled fix for this bug in safari?
    From what i understand i see that - Cookies are not transferred between your website and your webapp when installing the icon on the home screen (for authentication purposes for example). It was working until 6.1 and now it’s not working anymore.
    Can someone please tell me if this bug will be fixed in any future release, if so the ticket number of some kind that i can track, or if there is a workaround for this issue?

  • HT4528 Is there a fix for the bug where my BRAND NEW iphone 5S is locking up when I enable the magnifying glass to edit a text and it locks up!?

    Is there a fix for the bug where my BRAND NEW iphone 5S is locking up when I enable the magnifying glass to edit a text and it locks up!?

    Try a reboot press & hold power button & menu until Apple Logo comes on then wait
    you will not lose any data.
    That may fix your problem.
    bsydd uk

  • [svn:fx-i11] 5537: Fix for bug with FxRotate3D that Thermo ran into with our i11 build.

    Revision: 5537
    Author: [email protected]
    Date: 2009-03-24 20:16:43 -0700 (Tue, 24 Mar 2009)
    Log Message:
    Fix for bug with FxRotate3D that Thermo ran into with our i11 build. The problem was that we were sometimes setting offsets values to NaN due to bad initialization, and that we were also incorrectly calculating the transform center when offsets had not yet been initialized on the target.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-20209
    Reviewer: Ely
    tests: checkintests, mustella mx/effects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-20209
    Modified Paths:
    flex/sdk/branches/i11/frameworks/projects/flex4/src/mx/effects/FxAnimate3D.as
    flex/sdk/branches/i11/frameworks/projects/framework/src/mx/core/AdvancedLayoutFeatures.as

    We experience it as soon as we enable iCloud. Then an apple certificate is automatically added to the keychain and used for every https-access. Deleting the certificate com.apple.idms.appleid.prd... will do as a workaround but the certificate continues to be added to the keyChain from time to time or if you start over deactivating iCloud and then activate back.
    Is this still a bug in Safari? Rosario

  • [svn:fx-trunk] 5473: Fix for bug around handling of constraints during and after effects were run , both for old and new effects.

    Revision: 5473
    Author: [email protected]
    Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
    Log Message:
    Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17809
    Reviewer: Jason
    Testing: checkintests, Mustella Effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17809
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

    Revision: 5473
    Author: [email protected]
    Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
    Log Message:
    Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17809
    Reviewer: Jason
    Testing: checkintests, Mustella Effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17809
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

  • [svn:fx-trunk] 12294: * Fix for error reporting bug.

    Revision: 12294
    Revision: 12294
    Author:   [email protected]
    Date:     2009-11-30 13:25:28 -0800 (Mon, 30 Nov 2009)
    Log Message:
    Fix for error reporting bug.  The bug was caused by a warning being
      reported during one compilation and then an error being reported in
      a following compilation.  Due to the warning, the Source's logger
      was disconnected instead of being nulled out during the first
      compilation.  Then in the second compilation, we weren't reassigning
      the logger, so the disconnected logger was being left in place.  As
      a result, it was throwing off expected error counts and caused an
      assert to fire.
    QE notes: There is probably an easier way to reproduce the assertion
              that George hit without having to create multiple projects
              and without having to manually copy SWC's around.  I didn't
              realize this until I had a fix, though.  One key aspect that
              George didn't note and might not have realized, is that the
              variable needs to cause a warning, so leaving off a
              namespace works, but making it public, private, etc doesn't.
    Doc notes:
    Bugs: SDK-24314
    Reviewer: Corey
    Tests run: checkintests
    Is noteworthy for integration: fixes FB issue
    Code-level description of changes:
      Modified setLogger() to always reassign logger.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24314
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java

  • [svn:fx-trunk] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

    Revision: 12962
    Revision: 12962
    Author:   [email protected]
    Date:     2009-12-15 10:32:23 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Fix for ASDoc not saving event type for metadata tag
    QE notes: None.
    Doc notes: None
    Bugs: SDK-24706
    Reviewed By:Corey
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24706
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

    aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    Which correspondents fine with the
    device "hw:0,3"
    in my mpd.conf alsa section.
    Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
    hokasch:
    I tried changing the mixer to "Master" but that did not change much.

  • [svn:fx-trunk] 7473: Fix for 'ant asdoc' does not work.

    Revision: 7473
    Author:   [email protected]
    Date:     2009-06-01 12:09:26 -0700 (Mon, 01 Jun 2009)
    Log Message:
    Fix for 'ant asdoc' does not work.
    It should now work from both svn and package zip.
    Bugs: SDK-15306
    QE Notes: None.
    Doc Notes: None.
    tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-15306
    Modified Paths:
        flex/sdk/trunk/asdoc/build.xml
        flex/sdk/trunk/build.xml

  • [svn:fx-trunk] 13136: Fix for FLEXENT-1196 ( Replay of click on NavigatorContent does not close the combobox)

    Revision: 13136
    Revision: 13136
    Author:   [email protected]
    Date:     2009-12-21 17:40:28 -0800 (Mon, 21 Dec 2009)
    Log Message:
    Fix for FLEXENT-1196 (Replay of click on NavigatorContent does not close the combobox)
    We need not record OPEN event when it is triggered from a KeyBoard event that types a character. Replaying the type event would automatically open the drop down.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXENT-1196
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/SparkComboBoxAutomationImpl.as
        flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/supportClasses/SparkDropDownListBaseAutomationImpl.as

Maybe you are looking for