Quote:f you are going to display those images often (like in the routine, you shared), then it is a good idea to load and cache the images in memory until you are sure you'll not need those anymore. The _LOADIMAGE function adds quite a bit of processing overhead that may not really show until you are calling _LOADIMAGE inside tight loops. My two cents.
Good point. If the buttons were used in a form typing routine, the image would need to be loaded each time a key was pressed. I suppose what I can do is try some routines with the images saved in memory, and see how much memory the app uses. There will no doubt be some good balance between CPU and memory usage.
Thanks for the reply,
Pete