[svn:fx-trunk] 10138: Adding alpha to BitmapFill

Revision: 10138
Author:   [email protected]
Date:     2009-09-10 16:51:52 -0700 (Thu, 10 Sep 2009)
Log Message:
Adding alpha to BitmapFill
http://bugs.adobe.com/jira/browse/SDK-22932 - Border's backgroundAlpha style has no effect when backgroundImage is set
I have added an alpha property to BitmapFill. Since graphics.beginBitmapFill doesn?\226?\128?\153t have an alpha parameter, I have to clone the bitmapData source and apply to it a colorTransform (which contains the alphaMultipler).
If the source image doesn't support an alpha channel (ex. JPEG), then I need to copy the source into a new bitmapData object that supports transparency. This occurs one time in the source setter.
If the alpha or source has changed, then I need to copy the source into a new bitmapData. The reason is that using the BitmapData.colorTransform function is cumulative. Once I've applied an alphaMultiplier to it, there is no way to restore the alpha. I've optimized the code a bit to only copy the bitmapData if needed. For example, if we have already copied the data to add the transparent pixel border (to prevent the streaking effect on a non-repeating fill), then we forgo the copying.
QE notes: Need new tests for this property
Doc notes: Need docs for this property
Bugs: SDK-22932
Reviewer: Ryan
Tests run: checkintests
Is noteworthy for integration: Yes
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22932
    http://bugs.adobe.com/jira/browse/SDK-22932
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/BitmapFill.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/BorderSkin.as

Similar Messages

  • [svn:bz-trunk] 18061: Added svn:executable property to sh and bat files

    Revision: 18061
    Revision: 18061
    Author:   [email protected]
    Date:     2010-10-07 06:57:08 -0700 (Thu, 07 Oct 2010)
    Log Message:
    Added svn:executable property to sh and bat files
    Property Changed:
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/catalina.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/catalina.sh
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/cpappend.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/digest.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/digest.sh
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/setclasspath.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/setclasspath.sh
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/shutdown.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/shutdown.sh
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/startup.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/startup.sh
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/tool-wrapper.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/tool-wrapper.sh
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/version.bat
        blazeds/trunk/servers/apache-tomcat-6.0.29/bin/version.sh

    Well, I've tried compiling a package and I have modified the PKGBUILD file to look like this now. (Keeping it as simple as possible)
    pkgname=dvbcut-svn
    pkgver=16
    pkgrel=1
    pkgdesc="DVBCUT-svn is an application that allows you to
    edit MPEG files. ie: Remove TV ads. (SVN version: Fri, 01 Dec 2006)."
    url="http://dvbcut.sourceforge.net"
    depends=('qt' 'libao')
    makedepends=('subversion' 'scons')
    conflicts=('dvbcut' 'ffmpeg')
    provides=('dvbcut')
    source=()
    md5sums=()
    _svntrunk=https://svn.sourceforge.net/svnroot/dvbcut/trunk
    _svnmod=dvbcut
    build() {
    cd $startdir/src
    svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod
    cd $_svnmod
    msg "SVN checkout done or server timeout"
    msg "Starting make..."
    make || return 1
    # vim:syntax=sh
    I then run makepkg PKGBUILD and let it do its thing
    It ends with this...
    scons: done building targets.
    ==> Removing info/doc files...
    ==> Compressing man pages...
    ==> Stripping debugging symbols from libraries...
    ==> Stripping symbols from binaries...
    ==> Generating .PKGINFO file...
    ==> Generating .FILELIST file...
    tar: *: Cannot stat: No such file or directory
    tar: Error exit delayed from previous errors
    ==> Compressing package...
    tar: *: Cannot stat: No such file or directory
    tar: Error exit delayed from previous errors
    ==> Finished making: dvbcut-svn  (Sun Jan 21 19:08:28 UTC 2007)
    I'm not sure what's causing this error message.
    tar: *: Cannot stat: No such file or directory
    tar: Error exit delayed from previous errors
    I'll try installing it and see how it goes.

  • [svn:fx-trunk] 7784: adding xslt change so info related to Alternative shows up in the asdoc

    Revision: 7784
    Author:   [email protected]
    Date:     2009-06-12 07:46:21 -0700 (Fri, 12 Jun 2009)
    Log Message:
    adding xslt change so info related to Alternative shows up in the asdoc
    QE Notes: None.
    Doc Notes: None.
    Modified Paths:
        flex/sdk/trunk/asdoc/templates/class-parts.xslt
    Added Paths:
        flex/sdk/trunk/asdoc/templates/images/P_AlternativeMetadataIndicator_30x28_N.png

    I've checked the resolution in Photoshop just as a double-check and it shows resolution as 300 PPI. When you say "because they can be mixed" do you mean because elements and graphics with the PDF can be of varying resolutions? I hadn't thought of that, if that's what you meant. I do have some items within my pdf that might be lower resolution.
    If these show up in my Preflight Panel as an issue, does this mean they would be flagged also with the Printer? In trying to find a resolution I read several forum discussions about how Printers often run your document through a Preflight process and will send it back when there are low resolution images in the document.
    Is there some other way to be sure these images are in the InDesign document as 300 PPI so I can know they will in fact print correctly?
    PS - Peter - thanks for the super quick response! And I saw your the highlighted "Exceptional Contributor" on the right sidebar for the InDesign forum - clearly well-deserved! Congrats

  • [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] 10389: Added support for octothorpe in embed file names.

    Revision: 10389
    Author:   [email protected]
    Date:     2009-09-18 07:19:26 -0700 (Fri, 18 Sep 2009)
    Log Message:
    Added support for octothorpe in embed file names.  And here I thought I'd never use the term octothorpe in a sentence.
    QE notes: None
    Doc notes: None
    Bugs: SDK-23033
    Reviewer: Paul
    Tests run: Checkin
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23033
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedEvaluator.java

  • [svn:bz-trunk] 21277: Added ds-console source to package-oem and removed copy command for datavisualization .swc which doesn't exist in the specified location.

    Revision: 21277
    Revision: 21277
    Author:   [email protected]
    Date:     2011-05-18 11:35:28 -0700 (Wed, 18 May 2011)
    Log Message:
    Added ds-console source to package-oem and removed copy command for datavisualization.swc which doesn't exist in the specified location. I do not find it in the most recent package-oem.zip neither
    Modified Paths:
        blazeds/trunk/build.xml

    Gusar wrote:No, it's not. I have actually seen cases where software rendering gave a higher glxgears score than hardware rendering (and no, it wasn't about vsync). Of course, with *actual* apps on the same machine, software rendering sucked compared to hardware rendering.
    Please do not jump to conclusions and make assumptions here like 'when will people finally get it??'.  I never said it was a benchmark.  I have also seen many examples of where it's results do not go with conventional performance.  I have a Radeon 9000 that goes faster on glxgears than a Geforce FX 5600 running Nouveau.  Which is the faster card?  The FX by miles.  It is not a benchmark as it can not be compared between configurations.  What I know is that on this individual system, from prior experience over many years when 3D acceleration is working glxgears gets between 300 and 400 fps.  When it is not working it gets less than 10.  That is a fact but does not mean it is benchmarkable.  Yes, a Quake 3 timedemo (I have these numbers too and they very much correlate to glxgears performance for this system given just how slow it is) would be a benchmark but when it runs less than 0.1fps and even the 2D rendering means that navigating the menu is impossible, there just isn't the time to find out.  Hence if playing around with drivers on this system I would use glxgears to check that 3D acceleration is working but not to benchmark.  Glxinfo does not give you all this evidence.
    But to clarify, I wouldn't use glxgears as a benchmark, benchmarking is different and I do a lot of that too.

  • [svn:fx-trunk] 11483: Adding a LRU cache for the transcoding results of a CFF based DefineFont4 tag to avoid transcoding the same font description twice .

    Revision: 11483
    Author:   [email protected]
    Date:     2009-11-05 16:01:37 -0800 (Thu, 05 Nov 2009)
    Log Message:
    Adding a LRU cache for the transcoding results of a CFF based DefineFont4 tag to avoid transcoding the same font description twice.
    Also we now throw a better error when CFFFontManager is asked to embed a local font by name as this is not yet supported.
    QE notes: Please test that the same font embedded twice does not take twice as long as a single embedding.
    Doc notes: N/A
    Bugs:
    SDK-23966 - Compiler should generate a warning or error when embedAsCFF is true and src:local is used for font embedding
    SDK-23806 - OEM compiler appears to transcode embedded fonts twice
    SDK-23788 - Search fonts recursively
    Reviewer: Paul
    Tests run: Checkintests, bug test cases
    Is noteworthy for integration: Yes
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-23966
        http://bugs.adobe.com/jira/browse/SDK-23806
        http://bugs.adobe.com/jira/browse/SDK-23788
    Modified Paths:
        flex/sdk/trunk/lib/flex-fontkit.jar
        flex/sdk/trunk/modules/swfutils/src/java/flash/fonts/FontDescription.java
        flex/sdk/trunk/modules/swfutils/src/java/flash/swf/tags/DefineFont4.java

  • [svn:fx-trunk] 5353: * Added compiler error for Halo Navigators containing non-Containers

    Revision: 5353
    Author: [email protected]
    Date: 2009-03-17 12:59:06 -0700 (Tue, 17 Mar 2009)
    Log Message:
    * Added compiler error for Halo Navigators containing non-Containers
    as their first level child.
    tests Passed: checkintests
    Needs QA: YES
    Needs DOC: NO
    Bug fixes: SDK-19317
    API Change: NO
    Reviewer: Pete F.
    Code-level description of changes:
    compiler/mxml/lang/StandardDefs.java
    Added getContainerPackage(), isHaloNavigator(), CLASS_VIEWSTACK,
    CLASS_ACCORDION, and PACKAGE_MX_CONTAINERS.
    compiler/mxml/builder/ComponentBuilder.java
    Modified
    ComponentBuilder.ComponentAttributeHandler.nestedDeclaration() to
    report an error if a non-container is declared as a child of a
    Halo navigator.
    compiler_en.properties
    Added HaloNavigatorsRequireHaloContainerChildren message.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19317
    Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties

  • [svn:fx-trunk] 9171: Adding the change notes that come from the TLF folks

    Revision: 9171
    Author:   [email protected]
    Date:     2009-08-07 08:57:35 -0700 (Fri, 07 Aug 2009)
    Log Message:
    Adding the change notes that come from the TLF folks
    bug: nope
    qa: nope
    checkintests: no need
    Added Paths:
        flex/sdk/trunk/frameworks/projects/textLayout/ReleaseNotes.txt

  • [svn:fx-trunk] 12784: Added = 1.0 metadata for Power exponent property.

    Revision: 12784
    Revision: 12784
    Author:   [email protected]
    Date:     2009-12-10 07:32:14 -0800 (Thu, 10 Dec 2009)
    Log Message:
    Added >= 1.0 metadata for Power exponent property.
    QE notes:
    Doc notes:
    Bugs: sdk-24594
    Reviewer: Chet
    Tests run:
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24594
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/easing/Power.as

  • [svn:fx-trunk] 7677: adding xslt change so Theme shows up in asdoc for the styles ( where applicable)

    Revision: 7677
    Author:   [email protected]
    Date:     2009-06-09 10:54:15 -0700 (Tue, 09 Jun 2009)
    Log Message:
    adding xslt change so Theme shows up in asdoc for the styles (where applicable)
    QE Notes: None.
    Doc Notes: None.
    Modified Paths:
        flex/sdk/trunk/asdoc/templates/ASDoc_terms.xml
        flex/sdk/trunk/asdoc/templates/class-files.xslt

    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>

  • [svn:fx-trunk] 5587: Adding @namespace to halo and haloclassic defaults. css themes.

    Revision: 5587
    Author: [email protected]
    Date: 2009-03-26 12:06:28 -0700 (Thu, 26 Mar 2009)
    Log Message:
    Adding @namespace to halo and haloclassic defaults.css themes.
    QE: Could you please check if this fixes the recent themes issues, and that -compatibility-version=3.0.0 still works as expected too?
    Dev: No
    Doc: No
    Checkintests: Pass
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/halo/defaults.css
    flex/sdk/trunk/frameworks/projects/haloclassic/defaults.css

    I just saw that we are using xmlns:mx="http://www.adobe.com/2006/mxml" in all our custom components written in mxml, including our main application.
    In our custom css, I have the default namespace set to:
    @namespace "library://ns.adobe.com/flex/mx";
    could this result in these warnings ?

  • [svn:fx-trunk] 10600: Adding drag support to List - dragInitiator.

    Revision: 10600
    Author:   [email protected]
    Date:     2009-09-25 13:38:22 -0700 (Fri, 25 Sep 2009)
    Log Message:
    Adding drag support to List - dragInitiator. Currently can't drop the dragged items yet.
    - ListItemDragProxy class - default drag proxy for List (through a new style "dragIndicatorClass")
    - Added dragEnabled, dragMoveEnabled properties to List
    QE notes: Dragging from List is now possible. Dropping to different containers will come with subsequent check-in.
    Doc notes: None
    Bugs: None
    Reviewer: Ryan
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/defaults.css
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
        flex/sdk/trunk/frameworks/spark-manifest.xml
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ListItemDrag Proxy.as

  • [svn:fx-trunk] 12027: Added selectionAnchorIndex and selectionActiveIndex getters to RichEditableTextAccImpl and SkinnableTextBaseAccImpl .

    Revision: 12027
    Revision: 12027
    Author:   [email protected]
    Date:     2009-11-19 21:43:31 -0800 (Thu, 19 Nov 2009)
    Log Message:
    Added selectionAnchorIndex and selectionActiveIndex getters to RichEditableTextAccImpl and SkinnableTextBaseAccImpl. The presence of these getters is supposed to make Player 10.1 and AIR 2.0 able to support text-selection-accessibility for TLF-based text; they are the ActionScript side of the GetSelection() method in Adobe's ISimpleTextSelection COM interface for screen readers like JAWS.
    Although Player 10.1 and AIR 2.0 are adding a flash.accessibility.ISimpleTextSelection interface to formalize these getters, we want to be able to compile against the playerglobal.swc for Player 10.0 (or airglobal.swc for AIR 1.5). We could define our own copy of this interface in Flex, but it isn't necessary because the Player and AIR do not actually look at whether an AccessibilityImplementation class declares that it implements ISimpleTextSelection; they only look at whether an AccessibilityImplementation class has these getters.
    This way of doing text-selection-accessibility replaces the ITextSupport interface that was in earlier versions of Player 10.1 and AIR 2.0, including the betas. So you try it you must have a very recent build of 10.1 and 2.0.
    QE notes: None
    Doc notes: None
    Bugs: None
    Reviewer: None
    Tests run: None
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/RichEditableTextAccImpl. as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/SkinnableTextBaseAccImpl .as

  • [svn:fx-trunk] 12432: Added Capabilities. hasAccessibility check before calling Accessibility.updateProperties() in setter methods.

    Revision: 12432
    Revision: 12432
    Author:   [email protected]
    Date:     2009-12-03 06:59:10 -0800 (Thu, 03 Dec 2009)
    Log Message:
    Added Capabilities.hasAccessibility check before calling Accessibility.updateProperties() in setter methods.  This prevents an error on systems that do not support accessibility.
    QE notes: none
    Doc notes: none
    Bugs: (24454
    Reviewer: Gordon
    Tests run: checkintests
    Is noteworthy for integration: no
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as

Maybe you are looking for