Just upgraded to 3.0 beta and found out that the method I used to retrieve width/height of objects doesn’t work anymore.
If I do this:
var Test:Sprite = new Sprite();
Test.graphics.beginFill( 0xff0000, 1 );
Test.graphics.drawRect( 0, 0, 320, 240 );
Test.graphics.endFill();
addChild( Test );
And execute trace( Test.width ) when targeting HTML, Windows or Neko, all I get is 0. I tried to do type casting — trace( cast( Test, Sprite ).width ) — but no success.
If I do it while targeting Flash it outputs the correct width/height of the object. Any other target gives me 0.
If the object is from a class that extends a DisplayObject (hope I’m saying this right…still a total noob ) sometimes I also get values like “103.92304845413263”, even though the object is 320px wide.
Is there a way to get the correct width of objects in 3.0? Should I use legacy mode?
Sorry if I wrote it badly, not a native english speaker
BTW, I’m on a machine running Win 8.1 Pro (if this helps with anything)
Thanks!
EDIT: Not all DisplayObjects return a different value for its dimensions. Using Shape, instead of Sprite/MovieClip, returns the proper width.
package;
import openfl.display.Sprite;
class Main extends Sprite {
public function new () {
super ();
var Test:Sprite = new Sprite();
Test.graphics.beginFill( 0xff0000, 1 );
Test.graphics.drawRect( 0, 0, 320, 240 );
Test.graphics.endFill();
addChild( Test );
trace (Test.width);
}
}
I got 320. Is this occurring as part of a larger, more complicated project, or maybe this was resolved in the repository, and hasn’t been released yet. I think we’ll do another beta release soon today
Joshua, I tested the code again and I’d like to correct one thing I said.
Not all objects that extend DisplayObject returns 0. Trying the code I posted with Shape returns the proper width, but using Movieclip or Sprite returns 0.
Will properly write an issue in the Github repo, if it helps.
You should avoid using the width and height properties of DisplayObjectContainer(s) such as Sprite and MovieClip, as it will change if any of their children moves over the initial width and height.
This will be even more likely to happen if you center your Sprite, to make things like rotation easier.
Hi, Marco. And thanks! I already learnt this by trial and error when I started thinking about the current project , but that isn’t a big problem. For what I’m doing here, I have to use width/height of the container to properly resize it when the stage/screen resizes.
Before adding children objects, I set up a small safe zone so I don’t have to worry about its children moving. Since I’m building a puzzle right now, since each tile’s movements are predictable, and since the tiles move relative to the container’s original dimensions, it doesn’t pose a problem, for now. But for my second project, I might have a few headaches if I do this.
Since I’m still learning Haxe (and how to properly write code), I think it is a good thing to let these things happen.
) sometimes I also get values like “103.92304845413263”, even though the object is 320px wide.
