Thanks for that!
BTW why would you leek memory by design? Have not written the garbage
collection yet or what?
On Wed, Mar 28, 2018 at 10:34 PM, Dalai Felinto wrote:
> Hi,
>
> > > When will it come back?
> > Soon.
>
> Move to collections (M key) was just committed. We may iterate over it to
> fi
On Sun, Mar 11, 2018 at 3:51 PM, Knapp wrote:
> What is the best link for 2.8 news?
Summary:
https://www.blender.org/2-8/
Blog:
https://code.blender.org
Social media:
YouTube - https://www.youtube.com/BlenderDevelopers
Twitter - https://twitter.com/BlenderDev
Facebook - https://www.facebook.com
Hi,
> BTW why would you leek memory by design? Have not written the garbage
collection yet or what?
I explain it here: https://developer.blender.org/rBf167226b793e
But basically in order to do multi-level (i.e., nested) menus with the
current code base I had to resort to uiItemMenuF.
This funct
So it will only deallocate the memory when you call it the next time but
you never need to do this when you destroy the object? Am I understanding
this correctly?
If so, then why not add a function to UItemMenuF that releases the memory?
On Thu, Mar 29, 2018 at 7:36 PM, Dalai Felinto wrote:
> Hi