puzzler Posted May 25, 2017 Share Posted May 25, 2017 In 2.6.2, I've found that calling myGroup.getBounds().bottom gives me back an incorrect value unless I retrieve myGroup.height first. I find it bizarre that the behavior of getBounds seems to be influenced by whether or not I've inspected the height of the group first. Is this a known problem? Is there a way to make sense out of this behavior? Link to comment Share on other sites More sharing options...
samme Posted May 26, 2017 Share Posted May 26, 2017 Try just myGroup.bottom. Link to comment Share on other sites More sharing options...
puzzler Posted May 26, 2017 Author Share Posted May 26, 2017 That definitely works. I'm not sure how I failed to notice that property was available directly on group. Thanks. The behavior of getBounds() is still rather bizarre to me, but if it's mainly meant as some sort of internal call to facilitate the other properties, maybe I'm just not supposed to be accessing it directly. Link to comment Share on other sites More sharing options...
Recommended Posts