Hey Rutger,
2013/6/13 Rutger ter Borg <rut...@terborg.net>
>
> Hey Koen,
>
> sorry, my bad. Of course they will end up on the heap, they're part of a
> heap-allocated WApplication. What I was trying to say is that I'm trying
> to keep the amount of allocations as small as possible by instantiating
> them by value as data members of classes.
>
I've never attempted to do that, but that should be possible, really.
I do not really approve of the strategy though; our experience from
profiling is that widget allocation isn't at all a bottle neck, there are
far more things happening dynamically during rendering (which inevitably
happens to a widget) that take much more time (and more memory
allocations/deallocations).
Regards,
koen
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
