[svn] 4335: GraphicElement Optimization

Revision: 4335
Author: [email protected]
Date: 2008-12-16 16:52:56 -0800 (Tue, 16 Dec 2008)
Log Message:
GraphicElement Optimization
- Changed how a shared displayObject is positioned in a GraphicElement. Previously, it was always placed at (x,y). Now, it is placed at (0,0) if the displayObject can be shared (ie. it has no transforms). This solves the problem of a sharedDisplayObject getting repositioned without the GraphicElement being aware of it.
- Optimized Group.updateDisplayList so that we only redraw the GraphicElement's that share a displayObject that needs to be updated. Added a new class called InvalidatingSprite which has a single property called "invalid". If a GraphicElement needs to be redrawn, it marks its shared or unshared displayObject as invalid. Group will then only update the GraphicElements whose displayObject is marked invalid. Added invalidateDisplayList calls in a few missing places.
QE Notes: Some of the mustella bitmaps need to be regenerated. The player renders differently two transformed sprites that draw the same visuals. For example, a rotated sprite at (0,0) with a drawRect at (20,20) will look from a rotated sprite at (20,20) with a drawRect at (0,0).
Doc Notes: None
Bugs: SDK-18053
Reviewer: Evtim
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18053
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/FxTrackBase.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Line.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/Path.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s
flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxVSliderSkin.mxml
Added Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/core/InvalidatingSprite.as

Similar Messages

[svn] 4255: GraphicElements are no longer supported in DataGroup.

Revision: 4255
Author: [email protected]
Date: 2008-12-08 15:32:25 -0800 (Mon, 08 Dec 2008)
Log Message:
GraphicElements are no longer supported in DataGroup. This allowed us to clean up a lot of the code (hurray!)
Moreover, there are some other cleanups. We now support null items. Item renderers are strongly typed as IVisualElements now (an item renderer must be an IVisualElement and a DisplayObject). We also don't dispatch events when changing the itemRenderer or itemRendererFunction anymore as there's no need to do it and no need to make these properties bindable.
Also a minor fix in FlexNativeMenu where the binding metadata was using the wrong event.
QE Notes: Steve's already changed mustella tests for me.
Doc Notes: None
Bugs: SDK-18040, SDK-18046, SDK-18045
Reviewer: Glenn
tests: checkintests, mustella DataGroup, FxDataContainer, FxList, Group
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18040
http://bugs.adobe.com/jira/browse/SDK-18046
http://bugs.adobe.com/jira/browse/SDK-18045
Modified Paths:
flex/sdk/trunk/frameworks/projects/airframework/src/mx/controls/FlexNativeMenu.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/DataGroup.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxButtonBar.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxList.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/Group.as

jasonwryan wrote:
theking2 wrote:
tomegun wrote:All our packages now have service files, so everyone should be able to migrate away from rc.conf. New users should never create/need it.
Does "All our packages" also include the AUR packages?
No: they are not Arch packages.
theking2 wrote: The one I specifically am worried about is the LogitechMediaServer AUR, and the miniDLA. Is there a way to find out if they will run with systemd and if not what to do?
You can just read the PKGBUILD rather than expecting others to do it for you...
I can read fairly well, (with my reading glasses, admitted) what particularly do I have to (not) worry about?
p.s. I did write my own PKGBUILDs in the past that work passably well
Last edited by theking2 (2012-12-06 01:18:48)

[svn] 3149: Fix bugs introduced by the display object sharing optimization.

Revision: 3149
Author: [email protected]
Date: 2008-09-08 16:58:35 -0700 (Mon, 08 Sep 2008)
Log Message:
Fix bugs introduced by the display object sharing optimization. This checkin should fix ordering problems when dynamically adding/removing graphic elements, and ordering problems when changing graphic element properties that require a display object (rotation, alpha, filters, etc).
Bugs:
MXMLG-219: BitmapGraphic component content always rendered from 0, 0 origin.
MXMLG-220: setting visible property of Rect and Ellipse does nothing.
MXMLG-222: setting the alpha of a rectangle changes z-order when there are 3 or more rectangles
SDK-16754: Z-order incorrect when a Group is present
QA: Yes - the test files from these bugs (or something equivalent) should be added to our standard test suite
Reviewer: Deepa
Ticket Links:
http://bugs.adobe.com/jira/browse/MXMLG-219
http://bugs.adobe.com/jira/browse/MXMLG-220
http://bugs.adobe.com/jira/browse/MXMLG-222
http://bugs.adobe.com/jira/browse/SDK-16754
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/core/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/BitmapGraphic.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/graphicsClasses/GraphicElement .as

This is the great thread ;-)
My favorite threads are below.
Munky posted great reply :8}
SQL Query Help
order in a connect by

[svn:fx-trunk] 5028: IGraphicElement interface clean-up and optimizations.

Revision: 5028
Author: [email protected]
Date: 2009-02-20 16:02:17 -0800 (Fri, 20 Feb 2009)
Log Message:
IGraphicElement interface clean-up and optimizations.
Animating a GraphicElement that doesn't share the Group's DO should be now faster and smoother since redrawing it won't redraw the Group anymore.
1. Group doesn't always clear the first sequence of display objects now
2. Moved the shared DO logic almost entirely into Group
3. More granular invalidation for GraphicElements
QE Notes: Make sure we have test that count the number of display objects for a given set of graphic elements and a group
Doc Notes:
Bugs: None
Reviewer: Glenn, Ryan, Jason
tests: None
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/GroupBase.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/core/InvalidatingSprite.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/BitmapGraphic.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/IGraphicElement.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/StrokedElement.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/baseClasses/GraphicElement.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/baseClasses/TextGraphicElement.a s
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/IVisualElement.as
Added Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/ISharedDisplayObject.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/baseClasses/ISharedGraphicsDispl ayObject.as

[svn] 4137: Optimize Group layout invalidation.

Revision: 4137
Author: [email protected]
Date: 2008-11-18 17:53:32 -0800 (Tue, 18 Nov 2008)
Log Message:
Optimize Group layout invalidation.
This change adds two Boolean flags to track if Group?\226?\128?\153s layout is invalidated. This way whenever a GraphicElement?\226?\128?\153s invalidateDisplayList() is called, the Group won?\226?\128?\153t redo the layout, but only validate that particular GraphicElement?\226?\128?\153s display list. Similar for size. Also I removed unconditional updateDisplayList() while assigning GraphicElement display objects and instead invalidate only the GraphicElements that have their sharedDisplayObject reassigned (we were already invalidating when the exclusive display object is assigned).
Additionally I added a small check in the stroke property change event handler to make sure we invalidate parent size & layout only when the stroke weight is changed, which minimizes layout passes for skin state changes, where states would change stroke color/settings.
QE Notes: None
Doc Notes: None
Bugs: None
Reviewer: Glenn
tests: checkintests, mustella (gumbo/core, gumbo/layout, graphictags, gumbo/filters)
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/GroupBase.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/StrokedElement.as

[svn] 3936: Added flag to force the creation of a displayObject for a GraphicElement

Revision: 3936
Author: [email protected]
Date: 2008-10-28 17:27:07 -0700 (Tue, 28 Oct 2008)
Log Message:
Added flag to force the creation of a displayObject for a GraphicElement
SDK-17818 - calling getBitmapData on a GraphicElement that shares it's displayobject always causes a layout pass
adding flag which forces the graphicElement to always create a displayObject for itself. This is a temporary solution to the bug and should get revisted after alpha.
QE Notes: n/a
Doc Notes: n/a
Bugs: SDK-17818
Reviewer: Gordon
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17818
http://bugs.adobe.com/jira/browse/SDK-17818
Modified Paths:
flex/sdk/branches/gumbo_alpha/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/G raphicElement.as

mimomimi wrote:
Hi;
I am developing a console for my Server Application. I'm using a JFrame and a ScrollPane.
I am using a vertical Scroll and I want to force the index of this Scroll to be in the down in order to display the last informations added to my console.
I didn't find a solution yet.
Thank you for your help.
CheersYou mean like was mentioned in [this |http://forums.sun.com/thread.jspa?threadID=5420524&tstart=0] post, right on the front page of the Swing Forums?

[svn] 2622: TextBox and TextGraphic now call applyDisplayObjectProperties() at the end of their draw() method, like all other GraphicElements.

Revision: 2622
Author: [email protected]
Date: 2008-07-24 16:13:32 -0700 (Thu, 24 Jul 2008)
Log Message:
TextBox and TextGraphic now call applyDisplayObjectProperties() at the end of their draw() method, like all other GraphicElements. This method handles setting the visibiliy of the GraphicElement's DisplayObject, among other things.
Note: We should make it unnecessary for each GraphicElement subclass to have to call applyDisplayObjectProperties() at the end of draw(). The GraphicElement base class should ensure that this gets called at the appropriate time.
Group now calls draw() on graphic elements even if they are invisible, because otherwise applyDisplayObjectProperties() never gets called and the TextLines stay visible. Group was assuming that the only visible stuff in a GraphicElement is drawn with Graphics calls, which isn't the case.
This change is OK for now because every GraphicElement currently has its own DisplayObject, but it will need to be rethought when GraphicElements share DisplayObjects.
Reviewer: Chet
Bug: MXMLG-206 ("Setting visible property on TextGraphic does nothing")
QA: Peter, please add a Mustella test case for the 'visible property of TextBox and TextGraphic
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/MXMLG-206
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/core/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/TextBox.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/TextGraphic.as

Changes for spine–aligned head:
public class StickManTool extends JPanel
    public StickManTool ()
        limbs [16] = new Limb (lankle, lfoot, 1);
        head = new Head2D (limbs[0]);
    protected void paintComponent (Graphics g)
        head.draw(graphics);
    private void updateLimbs (Point start, Point end)
        head.setPosition();
class Head2D extends Ellipse2D.Double
    public static double width = 30;   // width of head
    public static double height = 40; //height of head
    Point atlas;
    Point pelvis;
    private AffineTransform xform = new AffineTransform();
    public Head2D(Limb spine)
        super ();
        atlas = spine.movingJoint;
        pelvis = spine.fixedJoint;
        setPosition();
    public void setPosition()
        // Find angle of spine.
        double dy = atlas.y - pelvis.y;
        double dx = atlas.x - pelvis.x;
        double theta = Math.atan2(dy, dx);
        //System.out.printf("theta = %.1f%n", Math.toDegrees(theta));
        // Find center of head as extension along spine from atlas.
        double cx = atlas.x + (height/2)*Math.cos(theta);
        double cy = atlas.y + (height/2)*Math.sin(theta);
        // Move to origin of head.
        xform.setToTranslation(cx-width/2, cy-height/2);
        // Rotate head about its center.
        xform.rotate(theta+Math.PI/2, width/2, height/2);
    public void draw(Graphics2D g2)
        g2.draw(xform.createTransformedShape(this));
    public double getWidth () { return width; }
    public double getHeight () { return height; }
    public void setWidth (double widthIn) { width = widthIn; }
    public void setHeight (double heightIn) { height = heightIn; }
}

[svn:fx-trunk] 7434: Remove over-optimization that doesn't work if bounds. x != 0.

Revision: 7434
Author:   [email protected]
Date:     2009-05-29 11:22:17 -0700 (Fri, 29 May 2009)
Log Message:
Remove over-optimization that doesn't work if bounds.x != 0.
QA Notes:
Doc Notes:
Bugs: SDK-21470
Reviewers: Gordon
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21470
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/SimpleText.as

I have exactly the same issue and it is INFURIATING. I have done several factory resets. reinstalled iTunes, pretty much everything as above. Hours and hours of failed trial and error. I can get one proper sync. ONE. If I'm lucky, by wiping everything. Then will iTunes update reliably? NO. Exactly the above issue. (including huge "other" files from some of the failed syncs.)
Iphone 6, latest updates. Latest OS X, latest iTunes. This problem started in the last week or so with my iPhone 5 before I upgraded a few weeks ago. It has to be an issue with the new iTunes and its (in)ability to do proper syncing.

[svn] 1418: Remove the optimization that was added as part of the fix for BLZ-133.

Revision: 1418
Author: [email protected]
Date: 2008-04-25 11:16:16 -0700 (Fri, 25 Apr 2008)
Log Message:
Remove the optimization that was added as part of the fix for BLZ-133. We cannot depend on isRequestedSessionIdFromCookie reliably, instead we should rely on the fact that encodeURL returns the same url when cookies are enabled.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-133
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/SessionFilter.j ava

This indicates corrupt files. A restore should resolve.

[svn:fx-trunk] 7465: Rev 7434 removed an optimization that didn' t work if bounds.x != 0.

Revision: 7465
Author:   [email protected]
Date:     2009-06-01 05:52:48 -0700 (Mon, 01 Jun 2009)
Log Message:
Rev 7434 removed an optimization that didn't work if bounds.x != 0. This puts it back in correctly.
QA Notes: need to add tests to determine if objects are clipped when they should not be
Doc Notes:
Bugs: SDK-21470
Reviewers: Gordon
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21470
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/supportClasses/TextGraphicE lement.as

Updated first post with dmesg output. I added all of it, but here's a quick snippet of the tail (which is right after booting up and attempting to autostart SLiM)
[ 13.426857] NVRM: API mismatch: the client has the version 310.19, but
NVRM: this kernel module has the version 304.60. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.
Why is the kernel getting 304.60 ? That's got to be the issue, but I don't why the kernel is getting 304.60 ...
Output of pacman -Qs nvidia:
local/conky-nvidia 1.9.0-2
An advanced, highly configurable system monitor for X based on torsmo
local/lib32-nvidia-utils 310.19-1
NVIDIA drivers utilities and libraries. (32-bit)
local/libvdpau-git-flashpatch 20120825-1
Nvidia VDPAU library from git with patch to fix flash blue tint and bleed through
local/libxnvctrl 304.51-1
NVIDIA X Ctrl library
local/nvidia 310.19-2
NVIDIA drivers for linux.
local/nvidia-utils 310.19-1
NVIDIA drivers utilities and libraries.

[svn] 3130: Fix SDK-16700: Applying a matrix to a GraphicElement does not get applied immediately.

Revision: 3130
Author: [email protected]
Date: 2008-09-05 15:32:13 -0700 (Fri, 05 Sep 2008)
Log Message:
Fix SDK-16700: Applying a matrix to a GraphicElement does not get applied immediately.
Added explicit matrixChanged and displayObjectChanged flags to GraphicElement so we can reliably track changes to those items. Changed commitXY() to set the x and y properties directly on the display object rather than indirectly through the matrix. Setting through the matrix caused any non-rotation or scale transform to be lost.
Reviewer: Deepa
Checkintests: pass
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16700
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/graphicsClasses/GraphicElement .as

:/ - I just said I can't post this on the business forum as I have tried, it it says my post doesn't conform to the rules, yet there isn't anywhere where it breaks them. I will already be in talks with a lawyer but I was wondering if a more amicable solution could be reached first

[svn] 4624: Flex SDK Bug Fix - Add snapshot support for 3D transformed GraphicElements

Revision: 4624
Author: [email protected]
Date: 2009-01-22 13:15:17 -0800 (Thu, 22 Jan 2009)
Log Message:
Flex SDK Bug Fix - Add snapshot support for 3D transformed GraphicElements
SDK-17362 - GraphicElement.getBitmapData doesn't handle 3D transforms
Added in support to take a bitmap snapshot of a 3D transformed GraphicElement.
Added a flag to getBitmapData to return a bitmap of the target either in the local or global coordinate space.
Also, fixed a bug in the bitmap snapshot logic for a 2D GraphicElement that was sharing its displayObject.
Note that the 3D snapshot isn't accurate if you have set maintainProjectionCenter on an ancestor. There are also limitations when rotation is applied. In addition, getting a local 3D snapshot isn't too accurate once you start scaling ancestors.
QE Notes: Add mustella tests for getBitmapData
Doc Notes: Document that getBitmapData now supports 3D transforms
Bugs: SDK-17362
Reviewer: Evtim
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17362
http://bugs.adobe.com/jira/browse/SDK-17362
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

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

[svn] 2695: Add includeInLayout property to GraphicElement.

Revision: 2695
Author: [email protected]
Date: 2008-07-31 13:40:32 -0700 (Thu, 31 Jul 2008)
Log Message:
Add includeInLayout property to GraphicElement.
Reviewed by Ryan.
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/graphicsClasses/GraphicElement .as

[svn:bz-trunk] 12783: Optimizations around subtopic handling in MessageService/ ActionscriptAdapter, now we avoid calling Subtopic constructor ( which is costly) multiple times.

Revision: 12783
Revision: 12783
Author:   [email protected]
Date:     2009-12-10 06:42:14 -0800 (Thu, 10 Dec 2009)
Log Message:
Optimizations around subtopic handling in MessageService/ActionscriptAdapter, now we avoid calling Subtopic constructor (which is costly) multiple times.
Checkintests: Pass - except the usual 3 failing tests.
QA: Yes
Doc: No
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/services/MessageService.java
    blazeds/trunk/modules/core/src/flex/messaging/services/messaging/SubscriptionManager.java
    blazeds/trunk/modules/core/src/flex/messaging/services/messaging/adapters/ActionScriptAda pter.java

[svn] 3624: Enabling initial support for colorTransform in GraphicElement.

Revision: 3624
Author: [email protected]
Date: 2008-10-14 08:35:30 -0700 (Tue, 14 Oct 2008)
Log Message:
Enabling initial support for colorTransform in GraphicElement.
Bugs: MXMLG-241
Check-in Tests: Pass
Reviewer: Chet, Ryan, Jason
QA: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/MXMLG-241
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

I guess GraphicElement will never support automation, at least by the time of Flex 4 release.
During my tests with GraphicElement extending IAutomationObject interface, I've just hit RTE coming from closed-source mx.automation.AutomationManager class requesting the automated UI control to implement IUIComponent interface, and obviuosly GraphicElement class does not implement this interface
TypeError: Error #1034: Type Coercion failed: cannot convert GraphicElementAutomation@7b10e19 to mx.core.IUIComponent.
at mx.automation::AutomationManager/getChildren()[C:\work\flex\dmv_automation\projects\automation\src\mx\automation\AutomationManager.as:1157]

[svn] 4335: GraphicElement Optimization

Similar Messages

Maybe you are looking for