[interfacekit] Re: async BView::FrameResized()

Hi,

I can confirm that on R5, the values passed to FrameResized() might not be 
the same as the views current width/height as per Bounds().

Which means using Bounds() in FrameResized() is unreliable. Should we 
duplicate this in Haiku (by using the values from the message), or should 
we make FrameResized() synchronous again, provided that the actual fix for 
#301 was not to call FrameResized() as long as the view as not attached to 
a window? I would be in favour of the later, since I am sure a lot of code 
calls Bounds() in FrameResized() (just look at our repo...) and it is quite 
convenient to be able to rely on that.

Best regards,
-Stephan

Other related posts: