Not a bug fix, per se, but a change in the way the dll handles the hBitmap passed to it. I had made the incorrect assumption that the host language would have a good way to deal with the .GetHbitmap method. Apparently, you need to define a Win32 DeleteObject command to remove the resources created with that function.
It's not too big a deal in the .net languages, but VB6 could get ugly. Instead, I'm now automatically deleting the object sent to the LcdUpdateBitmap function. The download is on the DMcLgLCD page and contains updated example code.
It's not too big a deal in the .net languages, but VB6 could get ugly. Instead, I'm now automatically deleting the object sent to the LcdUpdateBitmap function. The download is on the DMcLgLCD page and contains updated example code.
RSS Feed
