LiveDocs Comments - flash - 9.0 - ActionScriptLangRefV3 - flash/display/BitmapData.html

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

swartz1999 — 2008-03-03T16:30:36

Paul, we cannot reproduce the problem you are experiencing. As adbe_paul recommends, feel free to log a bug in the Adobe Flex bugbase.

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

Paul Feakins — 2008-02-09T03:08:18

Of course. I'm just wondering what's wrong with my code below? It says above that the constructor requires a width and height, but the code below won't compile because it says BitmapData() takes no more than 0 arguments. I'm a little confused.


import flash.display.BitmapData;

public function init():void
{
var myBitmapData:BitmapData = new BitmapData(100, 100, false, 0xFFFFFF);
}

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

adbe_paul — 2008-02-07T10:32:10

Without seeing your code, it's impossible to say what might be causing the problem.

If it's something that keeps happening, please file a bug for Flex Builder in the public Flex bugbase:
http://bugs.adobe.com/flex/

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

Paul Feakins — 2008-02-05T12:33:09

Hi there, I'm probably making a very simple error by Flex Builder is telling me that BitmapData() accepts no more than 0 arguments when I try to compile. However, code hinting suggests it takes width, height, transparency and colour?

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

Stephen Barrante — 2008-01-16T13:43:36

The documentation for getPixel() indicates that a 0 value will be returned if
the (x,y) coordinates are outside the bounds of the bitmap.

I'm running into a situation where a check to see if the returned value is 0 is
true very regularly. What became apparent was that it was actually return
black pixel values, or 0x000000, which when turned into a decimal = 0. It
seems like it would be difficult to evaluate whether or not the script is failing
or if I am getting valid pixel information back in the form of a full black pixel.

Has anyone encountered this and could offer an explanation? In this case
you would think that it should return a -1.

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

Carl Looper — 2007-07-21T16:52:14

As of writing the current release version of FlashPlayer9 does not distinguish between bitmapData.unlock() and bitmapData.unlock(changeRect). Both behave as if only unlock() was called. Furthermore, a call to lock() without a corresponding unlock() - can fail to block an update of the display - depending on the circumstances.

Otherwise the lock/unlock behaves as expected and functionally improves performance.

The problem is known to Adobe and a fix is in the pipeline for future releases of the player.

flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html

Carl Looper — 2007-07-09T16:10:05

In BitmapData.compare operations the result type is an object because it is either a signed integer object or a BitmapData object

So the result needs to be cast as the required object either this way (as per updated documentation):
diffBmpData = bmd1.compare(bmd2) as BitmapData;

or this way:
diffBmpData = BitmapData( bmd1.compare(bmd2) );

But these only work if you know a BitmapData object really is being returned. In some situations you may not be able to control this.

In these situations you can couch the statement in a try/catch block - and if an exception is thrown (because the returned object was not a BitmapData object) you can catch the returned object as an integer and act accordingly.

Carl