trouble filling in a closed vector shape

[madscijr]

That makes sense - I asked how we might gracefully determine if an image handle is associated with an image before doing _FreeImage and @SMcNeill had an answer that works for me... 

Code: (Select All)

SUB FreeImage (handle AS LONG)

   IF handle < -1 THEN 

     _FREEIMAGE handle

    handle = 0

   END IF

END SUB

Just write your own freeimage routine and have it *always* set to handle back to 0 when it's freed the handle.
If a handle isn't loaded at all, then it's going to be 0.
If a handle is > 0 then it's going to be a screen handle and not needing to be freed.
Only LOAD when handles are 0 or -1, and only FREE when the handle is < -1 and then set the handle back to 0.
It's about the easiest way to deal with the issue that I know of.

and @RhoSigma had some good suggestions too: 

IMO it should be handle = -1 instead of 0, as -1 is the official invalid image handle value, while 0 could be a screen page in legacy screens and get missinterpreted as the current destination page.
Best is probably to use the provided compiler constants, hence handle = _INVALID_IMAGE.

One should be able to safely call that custom FreeImage routine at the end of a program or routine without having to worry about an error if the image has already been freed. 

Good to know about that maptriangle for filled triangles!

[bplus]

Still I don't believe it necesary to free images at the end of a program what do the developers who know under-the-hood stuff say? @SMcNeill the amazing, @DSMan195276 the Super Moderator @a740g the serious serious

Inquiring minds need to know! I cant imagine any program would leave stuff in RAM after closing thats like not wiping your butt after... never mind.