In my implementation of TransformManager, the transform objects have children that can sometimes be positioned below 0,0. This causes the TransformManager selection anchor points to be positioned unexpectedly; one would expect that the selection anchor points would begin at the parent object's 0,0 point, but they actually begin at the child object's 0,0 point.
Here is some example code. In this example, the parent object is imageGroup1, and it contains an image that is larger than the parent object and positioned at -20,-20. It also contains a white box, to illustrate where the bounds of the parent object actually are. When you select the object, you would expect the selection handles to be around the white box, but they actually start at the child image.
<?xml version="1.0" encoding="utf-8"?>
Do you have any suggestions?