[svn:fx-trunk] 9225: Fix bug: Rows disappear in Spark List when using negative gap in layout and using virtualization

Revision: 9225
Author:   [email protected]
Date:     2009-08-11 11:36:09 -0700 (Tue, 11 Aug 2009)
Log Message:
Fix bug: Rows disappear in Spark List when using negative gap in layout and using virtualization
Fix: Change H/V layouts first-visible-element lookup logic to accommodate negative gaps.
QE notes: None
Doc notes: None
Bugs: SDK-22497
Reviewer: Hans
Tests run: checkintests,
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22497
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/HorizontalLayout.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as

sorka;
You can check the LabVIEW Support page.
There is a troubleshooting section called LabVIEW Installation/Getting Started Resources. It also includes a LabVIEW 7.x Frequently Asked Questions that has a link that reads Issues Fixed in LabVIEW 7.1. However, not much information is provided there.
Other places where you can post your findings is at the LAVA Forum (check the Bug list forum) and the Info-LabVIEW mailing list. These are not official places, but usually they li
sten
Enrique
www.vartortech.com

Similar Messages

  • [svn:fx-trunk] 12786: Fixed bug with state property value assignments.

    Revision: 12786
    Revision: 12786
    Author:   [email protected]
    Date:     2009-12-10 07:35:43 -0800 (Thu, 10 Dec 2009)
    Log Message:
    Fixed bug with state property value assignments. SetProperty pseudonym values (width/explicitWidth, height/explicitHeight) were not getting set correctly, causing values to be incorrectly assigned to 0 in some cases.
    QE notes: -
    Doc notes: -
    Bugs: sdk-24446
    Reviewer: Corey
    Tests run: checkintests, Mustella tests/States, tests/mx/states
    Is noteworthy for integration: Yes (fix requested by tools)
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24446
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/states/SetProperty.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] 5831: Fix bug Fix SDK-19800 FxButton doesnt resize itself to display all text when lineBreak == toFit

    Revision: 5831
    Author: [email protected]
    Date: 2009-03-31 16:50:47 -0700 (Tue, 31 Mar 2009)
    Log Message:
    Fix bug Fix SDK-19800 FxButton doesnt resize itself to display all text when lineBreak == toFit
    Fix: implement text reflow support for TextGraphicelement.
    QE Notes: None
    Doc Notes:
    Bugs: SDK-19800
    Reviewer: Carol, Gordon
    tests: checkintests, mustella
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19800
    http://bugs.adobe.com/jira/browse/SDK-19800
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/supportClasses/TextGraphicE lement.as

  • [svn:fx-trunk] 9890: Fix bug involving changes to tabbing related properties

    Revision: 9890
    Author:   [email protected]
    Date:     2009-09-01 15:57:01 -0700 (Tue, 01 Sep 2009)
    Log Message:
    Fix bug involving changes to tabbing related properties
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-19577
    Reviewer: Corey
    API Change: No
    Is noteworthy for integration: No
    tests: checkintests mustella/managers/FocusManager
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-19577
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/FocusManager.as

  • [svn:fx-trunk] 9287: Fixes bug with shader-transition effects ( AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters .

    Revision: 9287
    Author:   [email protected]
    Date:     2009-08-13 15:53:43 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fixes bug with shader-transition effects (AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters. Fix was to capture the bitmap snapshot of the target without any of its own filters applied and to then use the ShaderFilter in conjunction with the target's filters during the animation.
    QE notes: Probably need more tests in this area, now that we handle it
    Doc notes: none
    Bugs: sdk-20250
    Reviewer: Jason
    Tests run: Checkintests, Mustella (spark/effects/[AnimateTransitionShader|Wipe|CrossFade])
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-20250
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransitionShader.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

  • [svn:fx-trunk] 9284: Fix bug: Spark BasicLayout should throw error/ RTE when setting useVirtualLayout

    Revision: 9284
    Author:   [email protected]
    Date:     2009-08-13 15:33:07 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fix bug: Spark BasicLayout should throw error/RTE when setting useVirtualLayout
    QE notes: None
    Doc notes: None
    Bugs: SDK-22211
    Reviewer: Hans
    Tests run: checkintests, gumbo/core/Group, gumbo/core/DataGroup, gumbo/core/List
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22211
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/bundles/en_US/layout.properties
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/BasicLayout.as

    This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
    The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
    Please could you attach DropDow nList.as that you edited ?
    Thank you so much.

  • [svn:fx-trunk] 9324: Fix bug: orientation/verticalAlign/ horizontalAlign properties of TileLayout should not be bindable

    Revision: 9324
    Author:   [email protected]
    Date:     2009-08-14 15:04:23 -0700 (Fri, 14 Aug 2009)
    Log Message:
    Fix bug: orientation/verticalAlign/horizontalAlign properties of TileLayout should not be bindable
    Fix: remove metadata, we were not dispatching events anyway.
    QE notes: None
    Doc notes: None
    Bugs: SDK-22715
    Reviewer: Hans
    Tests run: build
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22715
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/TileLayout.as

    to put it simple, the DataGrid supposely changes the dataProvider on each page (page here is actually the selection in the list. since the list displays only one item at one time, I just called each selection as page) . So, I was thinking to refresh the itemRenderer on each swipe. could be there are any other way to do this so appreciate any help and ideas. Thanks!

  • [svn:fx-trunk] 9275: Fix bug: GraphicElement.getStrokeExtents needs ASDoc

    Revision: 9275
    Author:   [email protected]
    Date:     2009-08-13 12:05:09 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fix bug: GraphicElement.getStrokeExtents needs ASDoc
    Fix: Add comment, while at it, updated the API to return a Rectangle instead.
    QE notes: None
    Doc notes: None
    Bugs: FLEXDOCS-1032
    Reviewer: Deepa
    Tests run: checkintests, spark/primitives, gumbo/layout/graphicElements
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1032
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Ellipse.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Path.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Rect.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/StrokedEleme nt.as

  • [svn:fx-trunk] 7891: Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets .

    Revision: 7891
    Author:   [email protected]
    Date:     2009-06-16 13:38:37 -0700 (Tue, 16 Jun 2009)
    Log Message:
    Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets.
    QE Notes: none
    Doc Notes: None
    Bugs: SDK-21839
    Reviewer: Evtim
    Tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21839
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

  • [svn:fx-trunk] 9127: Fixes bug in Slider animation where we would set the actual value during the animation , ignoring any snapInterval setting.

    Revision: 9127
    Author:   [email protected]
    Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
    Log Message:
    Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
    QE notes: None
    Doc notes: None
    Bugs: SDK-21776
    Reviewer: Hans
    Tests run: checkintests, Mustella (gumbo/components/Slider)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21776
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

    Revision: 9127
    Author:   [email protected]
    Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
    Log Message:
    Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
    QE notes: None
    Doc notes: None
    Bugs: SDK-21776
    Reviewer: Hans
    Tests run: checkintests, Mustella (gumbo/components/Slider)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21776
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

  • [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] 17920: Fix for WebLogic: WebLogic does not provide File IO on the deployed artifacts hence using getResourceAsStream .

    Revision: 17920
    Revision: 17920
    Author:   [email protected]
    Date:     2010-09-29 05:56:06 -0700 (Wed, 29 Sep 2010)
    Log Message:
    Fix for WebLogic: WebLogic does not provide File IO on the deployed artifacts hence using getResourceAsStream.
    Modified Paths:
        blazeds/trunk/apps/samples/WEB-INF/src/flex/samples/marketdata/Portfolio.java

    check the server log;
    /app/oracle/product/fwm11g/user_projects/domains/fwm_domain/servers/AdminServer/logs/AdminServer.log
    you can launch the console and see if it is running; http://<server>:<port>/console

  • [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] 12685: Fix for RTE in VideoPlayer when trying to capture bitmaps.

    Revision: 12685
    Revision: 12685
    Author:   [email protected]
    Date:     2009-12-08 19:23:32 -0800 (Tue, 08 Dec 2009)
    Log Message:
    Fix for RTE in VideoPlayer when trying to capture bitmaps. Put try-catch block around bitmapData.draw() and use a Rectangle if it throws an error. Also, added some documentation in BitmapUtil for getSnapshot since it may throw the same type of error.
    QE notes: No
    Doc notes: No
    Bugs: SDK-24574
    Reviewer: Ryan
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24574
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/HighlightBitmapCaptureSkin .as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/utils/BitmapUtil.as

  • [svn:fx-trunk] 8474: * Fixed the AST generation code path of Vector typed variables and

    Revision: 8474
    Author:   [email protected]
    Date:     2009-07-09 07:20:32 -0700 (Thu, 09 Jul 2009)
    Log Message:
    Fixed the AST generation code path of Vector typed variables and
      properties with Bindable.
    tests Passed: checkintests
    Needs QA: YES
    Needs DOC: NO
    Bug fixes: SDK-21587
    API Change: NO
    Reviewer: Peter D.
    Code-level description of changes:
       AbstractSyntaxTreeUtil.java
         Modified generateParameter(*) to use generateTypeExpression().
       binding/BindableSecondPassEvaluator.java
         Modified generateGetter() to use AbstractSyntaxTreeUtil.generateTypeExpression().
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21587
    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/BindableSecondPassEva luator.java

    I got again a total system freeze today when I wanted to launch firefox using only the openbox menu, without wbar running.
    So I decided to try now the 'nouveau.noaccel=1' kernel command line parameter, and to use again wbar for my frequently used applis.
    In the Xorg log, the differences are:
    without 'nouveau.noaccel=1'
    [ 30.761] (II) UnloadModule: "nv"
    [ 30.761] (II) Unloading nv
    [ 30.761] (--) Depth 24 pixmap format is 32 bpp
    [ 30.762] (II) NOUVEAU(0): Opened GPU channel 0
    [ 30.765] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 30.765] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 30.765] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 30.776] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 30.777] (II) EXA(0): Driver registered support for the following operations:
    [ 30.777] (II) Solid
    [ 30.777] (II) Copy
    [ 30.777] (II) Composite (RENDER acceleration)
    [ 30.777] (II) UploadToScreen
    [ 30.777] (II) DownloadFromScreen
    [ 30.777] (==) NOUVEAU(0): Backing store disabled
    [ 30.777] (==) NOUVEAU(0): Silken mouse enabled
    with 'nouveau.noaccel=1'
    [ 1191.621] (II) UnloadModule: "nv"
    [ 1191.621] (II) Unloading nv
    [ 1191.621] (--) Depth 24 pixmap format is 32 bpp
    [ 1191.621] (EE) NOUVEAU(0): Error creating GPU channel: -19
    [ 1191.621] (EE) NOUVEAU(0): Error initialising acceleration. Falling back to NoAccel
    [ 1191.621] (==) NOUVEAU(0): Backing store disabled
    [ 1191.621] (==) NOUVEAU(0): Silken mouse enabled
    [ 1191.621] (==) NOUVEAU(0): DPMS enabled
    So now 3D acceleration is disabled.
    I will see now if the system is stable enough for my daily usage and gives satisfactory performances.
    I am almost sure that the mesa nouveau dri driver is the cause of the freezes.
    Last edited by berbae (2013-03-27 10:07:42)

Maybe you are looking for

  • How do I get the picture to open on the main page when I am using Bing?

    How do I enable the daily photograhs to auotomaticly be visable when I open the seach engin BING? The BING main page is currently gray in color and I am unaware how to activate the screen-shot photo. The photos were visable only a few days ago.

  • Where can I obtain a copy of FireFox 12.0

    FireFox 13 takes entirely too long to load Msn.com. I wish to go back to FireFox 12 until such a time as webpage loading problems with FireFox 13 and beyond are resolved.

  • Does the Clone repair tool have an Aligned option like PhotoShop?

    PhotoShop's clone stamp has an option that is called "Aligned" under CS3 (not sure of its name in prior versions.) When clicked, there is a fixed spatial relationship between the source and destination pixels, even if you complete one clone operation

  • Shooting multiple bullets

    Hello everyone, I'm trying to make my platform game character shoot a gun, my character and gun are one movieclip and the bullet is another. The bullet mc starts on a blank frame with a stop() function, when I press the space bar the bullet mc plays

  • Simple actionscript please help...

    Heya ... hope someone can help me thanks :D, I have a movie clip mc, inside it is another movie clip mc2, inside that there is a dynamic text field = btnTitle (instance name) I am trying to load the variables into the text field but it doesnt work...