Replies: 2 comments 8 replies
-
Hi @leelavg ! Thanks for report. I'll try what you mentioned about memory, just in case there is a leak on the GTK side. There are times when the memory is not released instantly. All the memory reserved by NAppGUI is managed by the Heap module, which would report any unreleased allocation. On the other hand, there is not much documentation on Data Binding as a subject. The documentation I provide at |
Beta Was this translation helpful? Give feedback.
-
Closing in favour of #176. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a textview in a layout row with text of 2.5M written (raw) increases the memory occupied by app around ~22M and when the layout row is removed memory usage doesn't go down.
I see in i_destroy_cell func a comment that says only layout/cell is removed but not the contents, is there any way to destroy the content (as per docs destroy does free as well)? Tried a couple of ways but none worked out.
I kinda have coded only 10% of my app and so didn't put it out in open yet to point to the source, pls excuse. I'm on fedora (gtk) btw.
Thanks again for the sdk. Side note, do you have any recommendations for learning MVVM & data binding, I wasn't able to find any good resources other than what's mentioned in sdk docs, pardon I'm new to both C & gui programming and so is the ask for resources for MVVM.
Beta Was this translation helpful? Give feedback.
All reactions