[svn:fx-trunk] 8459: Fixing current point after CloseSegment command in Path sequences.

Revision: 8459
Author:   [email protected]
Date:     2009-07-08 12:39:23 -0700 (Wed, 08 Jul 2009)
Log Message:
Fixing current point after CloseSegment command in Path sequences.  Also fixing up cubic and quadratic smooth/shorthand logic (t/s) when preceding command is not a curve command).
Bugs: SDK-21866, SDK-21862, SDK-21607
Reviewer: Jason, Peter F.
QE Notes: None
Doc Notes: None
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21866
    http://bugs.adobe.com/jira/browse/SDK-21862
    http://bugs.adobe.com/jira/browse/SDK-21607
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Path.as

Hi,
If I were you, I would Streamline the MDT Task Sequence to find the root cause.
Moreover, please refer to the link below:
How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Similar Messages

  • [svn:fx-trunk] 5806: Fix null pointer reported by the doc team.

    Revision: 5806
    Author: [email protected]
    Date: 2009-03-31 10:03:36 -0700 (Tue, 31 Mar 2009)
    Log Message:
    Fix null pointer reported by the doc team.
    QE Notes: None.
    Doc Notes: None.
    tests: checkintests, asdoc tests
    Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

  • [svn:fx-trunk] 5146: Fix Gumbo_Priority bug, SDK-19515 - RTE in Path when data is empty.

    Revision: 5146
    Author: [email protected]
    Date: 2009-03-02 16:06:06 -0800 (Mon, 02 Mar 2009)
    Log Message:
    Fix Gumbo_Priority bug, SDK-19515 - RTE in Path when data is empty.
    Reviewer: Glenn
    Checkintests: Pass
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19515
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Path.as

    error dateField not selecion date 27/11/2002 ?
    This is bug flex 3 ?
    thanks

  • [svn:fx-trunk] 12865: Fix mx.controls.HTML and mx.core. FlexHTMLLoader so the participate in the current IME scheme

    Revision: 12865
    Revision: 12865
    Author:   [email protected]
    Date:     2009-12-11 13:51:27 -0800 (Fri, 11 Dec 2009)
    Log Message:
    Fix mx.controls.HTML and mx.core.FlexHTMLLoader so the participate in the current IME scheme
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-24391
    Reviewer: Corey
    API Change: No
    Is noteworthy for integration: No
    tests: checkintests mustella/apollo/HTML
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24391
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/controls/HTML.as
        flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/FlexHTMLLoader.as

    OK, Just changed the screen option in DEVICE... And now I'm getting this in my log files. When I try and install that package with pacman, it wants to remove the normal nvidia driver. Can I run one for each graphics card?
    Xorg.0.log
    (II) Module "ramdac" already built-in
    (WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is
    (WW) NVIDIA(0): supported through the NVIDIA 173.14.xx Legacy drivers.
    (WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
    (WW) NVIDIA(0): more information. The 185.18.36 NVIDIA driver will ignore
    (WW) NVIDIA(0): this GPU. Continuing probe...
    (II) resource ranges after probing:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888

  • [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] 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] 8602: Fix RTE after setting baseColor.

    Revision: 8602
    Author:   [email protected]
    Date:     2009-07-15 15:06:23 -0700 (Wed, 15 Jul 2009)
    Log Message:
    Fix RTE after setting baseColor.
    https://bugs.adobe.com/jira/browse/SDK-21749
    TitleBarSkin:
    Remove items form color exclusion array. Remove ?\226?\128?\156bgFill?\226?\128?\157 because it is not of type DisplayObject or GraphicElement. Remove ?\226?\128?\156background?\226?\128?\157 because it is part of the window chrome and should be affected by baseColor.
    SparkSkin:
    Only process excluded objects of type DisplayObject or GraphicElement in updateDisplayList().
    https://bugs.adobe.com/jira/browse/SDK-21625
    Spark and Halo WindowedApplication/Window:
    Update class comments and remove dead code.
    QE Notes: none.
    Doc Notes: none.
    Bugs: SDK-21749, SDK-21625.
    Reviewer: Glenn
    tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21749
        http://bugs.adobe.com/jira/browse/SDK-21625
        http://bugs.adobe.com/jira/browse/SDK-21749
        http://bugs.adobe.com/jira/browse/SDK-21625
    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
        flex/sdk/trunk/frameworks/projects/airframework/src/spark/skins/spark/windowChrome/TitleB arSkin.mxml
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/SparkSkin.as

  • [svn:fx-trunk] 10008: Fix for SDK-23005 performance regression after BlendMode changes

    Revision: 10008
    Author:   [email protected]
    Date:     2009-09-04 00:10:00 -0700 (Fri, 04 Sep 2009)
    Log Message:
    Fix for SDK-23005 performance regression after BlendMode changes
    Fix: make sure GE and Group DisplayObject sharing works in the blendMode="auto" case.
    QE notes: None
    Doc notes: None
    Bugs: SDK-23005
    Reviewer: Evtim
    Tests run: checkintests, basictests
    Is noteworthy for integration: Yes, blendMode behavior affects Catalyst
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23005
        http://bugs.adobe.com/jira/browse/SDK-23005
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Group.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as

    FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

  • [svn:fx-trunk] 7868: Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector . MotionPath

    Revision: 7868
    Author:   [email protected]
    Date:     2009-06-15 16:37:33 -0700 (Mon, 15 Jun 2009)
    Log Message:
    Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector.
    Modified Paths:
        flex/sdk/trunk/development/eclipse/flex/flex4test/src/testWheel.mxml

    Walter Laan wrote:
    almightywiz wrote:
    Walter Laan wrote:
    The security popup really messes with the focus in Firefox (3.6.16) though.Not saying you're wrong, but I'm using FireFox 3.6.16, as well, and I have none of the focus troubles you've described.Cannot reproduce it now either. Weird.I got the impression you were referring to keyboard focus, so I did some further tests on focus behavior. The test results are listed in the Accumulated Results table on the 1st post.
    The only browser so far that works as I'd expect, or at least as I'd like, is IE.
    Applets and keyboard navigation have always been a PITA. Some time ago I vaguely recall seeing an update involving a new parameter to regulate initial focus (applet or page, ..or another applet), but for the life of me I cannot locate it now. Given that it was a parameter for initial focus, I doubt it would help in this case.
    Edited by: Andrew Thompson on Mar 26, 2011 6:18 PM
    Removed table which has now been expanded & added to 1st post.

  • [svn:bz-trunk] 23085: Fix test to explicitly remove an event listener after the test is finished .

    Revision: 23085
    Revision: 23085
    Author:   [email protected]
    Date:     2011-10-21 07:49:33 -0700 (Fri, 21 Oct 2011)
    Log Message:
    Fix test to explicitly remove an event listener after the test is finished. Not doing this was causing the test to throw an RTE.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxml

    Thanks for the ideas regarding beforeInvoke, Ben.  I will try to check that out.  In my situation, here's essentially how my script is working...
    BeforeSave is invoked.
    Script makes a change to the document, which should be captured in the saved file.
    Document saves.
    Document appears saved for a moment, and then appears unsaved (asterisk in the document title).
    My biggest problem is that this behavior isn't consistent.  I have dozens of users, all running the same script, and the problem only occurs with certain users and at random times. I can move a problematic document from a user's machine to a different machine, and the problem doesn't occur there.  It's very difficult to troubleshoot because I can't reproduce it consistently.

  • [svn:fx-trunk] 11999: Fixed: ASC-3889 - Using setting in a for loop causes Verify error

    Revision: 11999
    Revision: 11999
    Author:   [email protected]
    Date:     2009-11-19 11:37:09 -0800 (Thu, 19 Nov 2009)
    Log Message:
    Fixed: ASC-3889 - Using setting in a for loop causes Verify error
    Notes: emit pop after callstatic to a void function to balance the stack.
    Reviewer: jodyer+
    Testing: asc,tamarin,flex checkin tests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/ASC-3889
    Modified Paths:
        flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/CodeGenerator.java

    Blacklisting the ahci module does indeed get rid of the error. Would be nice to figure out why it was conflicting with the ahci module though.
    I have not yet tried the 173xx drivers, but the latest drivers for the Quadro FX 580 are the 256.53 drivers according to nvidia.
    Posted at the nV forums (http://www.nvnews.net/vbulletin/showthread.php?t=155282), so we'll see what they suggest.

  • [svn:fx-trunk] 12982: Fix for issue with exposing accessible names for combobox list items

    Revision: 12982
    Revision: 12982
    Author:   [email protected]
    Date:     2009-12-15 20:44:23 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Fix for issue with exposing accessible names for combobox list items
    QE notes: none
    Doc notes: none
    Bugs: n/a
    Reviewer: Gordon
    Tests run: checkintests
    Is noteworthy for integration: no
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ComboBoxAccImpl.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ListBaseAccImpl.as

    Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
    margin-bottom: -2px;
    Your nav p will then look like this:
    nav p {
              font-size: 90%;
              font-weight: bold;
              color: #FFC;
              background-color: #090;
              text-align: right;
              padding-top: 5px;
              padding-right: 20px;
              padding-bottom: 5px;
              border-bottom-width: 2px;
              border-bottom-style: solid;
              border-bottom-color: #060;
              background-image: url(images/background.png);
              background-repeat: repeat-x;
              margin-bottom: -2px;

  • [svn:fx-trunk] 7553: Fix the default value of the [skinPart] "required" attribute for asdoc.

    Revision: 7553
    Author:   [email protected]
    Date:     2009-06-04 09:32:51 -0700 (Thu, 04 Jun 2009)
    Log Message:
    Fix the default value of the "required" attribute for asdoc.
    Bugs: SDK-21488
    QE Notes: None.
    Doc Notes: None.
    tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21488
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelGenerator.java

    ${ui:cond( uix.current.isNewRow, 'true', ui:cond( bindings.AddProjectNutsoverleg.value == 1, 'true', 'false' ) ) } notice the '.value' it could also be '.inputValue'.
    If not there is also an option to make sure that when the checkbox is empty a value is returned anyways this work like this:
      protected void processUpdateModel( DataActionContext ctx )
        //First look for the request parameter
        Object cbInRequest = ctx.getHttpServletRequest().getParameter( "nameofthecheckbox" );
        //We only need to do anything if it was not submitted
        if( cbInRequest == null )
          // Get hold of the Form Bean containing the record
          BindingContainerActionForm updateForm = (BindingContainerActionForm) ctx.getActionForm();
          //Get the binding for our particular column
          JUCtrlAttrsBinding checkBoxBinding = (JUCtrlAttrsBinding)updateForm.get( "nameofthecheckbox" );
          //Reset that explicitly to the *unchecked* value
          checkBoxBinding.setAttribute( 0, new oracle.jbo.domain.Number( 0 ) );
        super.processUpdateModel( ctx );
      }Maybe this helps.

  • [svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

    Revision: 12994
    Revision: 12994
    Author:   [email protected]
    Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
    Log Message:
    Fixes for two issues that were showing up in FB.
    QE notes:
    Doc notes:
    Bugs: SDK-24669, SDK-24686
    Reviewer: Corey
    Cycloner: George
    Tests run: checkintests
    Is noteworthy for integration: yes, fixes two FB issues.
    Code-level description of changes:
      modules/compiler/src/java/flex2/tools/PreLink.java
        Modified postRun() to swap in the root CompilationUnit's Logger
        when validating it's StyleContainer.  This allows the warnings
        from StylesContainer.validate() to be persisted across incremental
        compilations.  This fixes SDK-24686.
      modules/compiler/src/java/flex2/compiler/Source.java
        Made getLogger() public, so it could be called from PreLink.
      modules/compiler/src/java/flex2/compiler/CompilerAPI.java
        Modified compile() to check forcedToStop() after each PreLink
        batch.  This fixes SDK-24669.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24669
        http://bugs.adobe.com/jira/browse/SDK-24686
        http://bugs.adobe.com/jira/browse/SDK-24686
        http://bugs.adobe.com/jira/browse/SDK-24669
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

  • [svn:fx-trunk] 10866: Fix broken links in ASDoc comments for TLFTextInput. as and TextArea.as, and add OverrideBase.as to ASDoc output

    Revision: 10866
    Author:   [email protected]
    Date:     2009-10-05 08:56:44 -0700 (Mon, 05 Oct 2009)
    Log Message:
    Fix broken links in ASDoc comments for TLFTextInput.as and TextArea.as, and add OverrideBase.as to ASDoc output
    QE notes: -
    Doc notes: -
    Bugs: -
    Reviewer: -
    Tests run: - checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/states/OverrideBase.as
        flex/sdk/trunk/frameworks/projects/spark/src/mx/controls/TLFTextInput.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextArea.as

    Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
    CSS part:
    nav p {
    font-size: 90%;
    color: #FFC;
    text-align: right;
    font-weight: bold;
    background-color: #090;
    padding-top: 5px;
    padding-right: 20px;
    padding-bottom: 5px;
    border-top-width: 2px;
    border-top-style: solid;
    border-top-color: #060;
    HTML part: (bold italic is the part I added)
    <body>
    <div class="container">
      <div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
      <header></header>
      <nav>
        <p>Home | About Us | Contact Us</p>
      </nav>
      <div class="sidebar1">
        <ul class="nav">
          <li><a href="#">Green News</a></li>
          <li><a href="#">Green Products</a></li>
          <li><a href="#">Green Events</a></li>
          <li><a href="#">Green Travel</a></li>
          <li><a href="#">Green Tips</a></li>
        </ul>

Maybe you are looking for