Two questions.
Is there additional documentation on the DesktopGrid besides what’s found in the BLOG article and at DesktopGrid — Xojo documentation , and the examples?
Also, is there any significance, in terms of scope or performance, to which object(s) or which kind of object is selected as a GridDataSource? In other words is the GridDataSource object just a place to keep the GridDataSource interface methods?
Thanks
Hi Keith
I have a small test program to try out
my old container display with the new
Xojo Grid functions - I haven’t solved a few things yet
but it works well for testing.
Hi @Keith_Culotta,
About examples: you can go straight to the Examples option from the IDE’s “Choose a Project” window and search for DesktopGrid:
Also: https://www.youtube.com/watch?v=d7sMn2UujqE
That video has the slides in English… and the Audio in Spanish, but you can enable automatic translation / captions in YouTube.
Yes. You can implement the Class Interface in any object / class you want.
That gives me a clearer picture the role of the GridDataSource.
The video explains that cells that have scrolled out of the window are closed and the data released (paraphrasing here). Is that always true, or must “WeakRef” be used as suggested in the video for the cells to be released?
I’d keep weakref references to them (when it is necessary), so these can be properly freed from memory.
In other scenarios (it depends the kind of logic or use you want to do for the grid), there is no need to keep references to the content at all (I.e: the instantiated container controls).
