On Sat, May 28, 2011 at 7:31 AM, Jon Yoder<darkwyrm@xxxxxxxxx> wrote:
Depending on the situation, you could create a BBitmap which accepts
children, temporarily remove the view from its current parent, add it to the
bitmap, force it to draw itself, and then add the view back to its original
parent. This method does have some drawbacks: flicker on the screen,
The flicker could actually be avoided via careful use of
BWindow::{Disable,Enable}Updates().
significant overhead, and you have to be careful about how many BBitmaps you
create which accept children, but it's an alternative.
How so? This was true on BeOS since each view accepting BBitmap also
spawns a thread, and on that platform one couldn't create more than
iirc 192 threads in a team owing to the fixed 64MB stack/app and
poorly chosen thread stack sizes, but we don't have that particular
issue.
