My Avalonia app will have some auto-complete controls that can have hundreds of items in the data source where each item has an icon. In the source data, there is only be a small number of unique icons (say 6) but each one can be rendered many times over. Best equivalence I can think of is an intellisense/auto-complete popup in IDEs.
Back in the day, a common technique was to perform procedural drawing to memory, then during render time, blit the image onto the device context. This effectively would cache a render of the image so the procedural drawing didn't have to occur for every instance.
My Avalonia app will have some auto-complete controls that can have hundreds of items in the data source where each item has an icon. In the source data, there is only be a small number of unique icons (say 6) but each one can be rendered many times over. Best equivalence I can think of is an intellisense/auto-complete popup in IDEs.
Back in the day, a common technique was to perform procedural drawing to memory, then during render time, blit the image onto the device context. This effectively would cache a render of the image so the procedural drawing didn't have to occur for every instance.
Does this library do this?