joshtynjala / monsterdebugger-client-starling Goto Github PK

I'm wondering if it wouldn't be better to have getStarlingObjectUnderPoint use hitTest(point, false) instead of 'true' so that the user can hover and select even invisible objects or objects in the display list that aren't touchable. Not sure how MonsterDebugger works on the native flash stage but from the tutorials it seemed like it could be used to find hidden objects and scrub the whole hierarchy and not just select objects that are set to touchable.

In my app I use a scaling strategy which tries to keep display root (and its children) as close to a given size as possible and changes the Startling Stage's stageWidth and stageHeight. When I use my scaled app with Monster Debugger I get highlights like this:

You can see a similar issue with Feather's ScrollContainer when selecting its viewPort property.

When I check Highlight and inspect it draws an overlay layer over Stage, but once I click anything it unchecks this option and removes the overlay layer.

HI josh, I use then monster debugger in my App
it seems not work on starling 2.0.1 mobile app,debug with AIR simulator

My class has some constants like this: public static const MAX_FPS:int = 60;

When I initialize or inspects the class (this) I only see: MAX_FPS (int) = null