John, what OS are you using? Reading your description of the behavior, the "black square" (which is the 32x32 canvas) "erases" anything it passes over (colors it black) but that's not what I'd call working fine! :) It corrupts the user's desktop and leaves canvas crap all over it (Win2k,XP) even after the user exits the program. Manually refreshing the desktop/bringing other windows into focus is the only way I have gotten rid of the corrupted area. I just wish my program wouldn't make the Desktop to forget to Cls and flip properly, so to speak. Even if I make the window unmoveable/undragable, it still leaves a very literal black mark (where the canvas was located over) after exiting.
Sorry I'm not sure what you mean by border left over when moving... The window style is 0 so that is why there is no border, (I think this style might be necessary for the SetLayeredWindowAttributes call) and the canvas leaves a filled black box....
In the original InvalidateRect() crash, though it crashed, the canvas was translucent (semi-transparent) along with its window on Win2k/XP.
If anyone has a decent workaround to fake it somehow e.g. get under the window without any strain on older PCs, I'm definitely interested (maybe better to make a new thread for that if it's confirmed this cannot work).
Sorry I'm not sure what you mean by border left over when moving... The window style is 0 so that is why there is no border, (I think this style might be necessary for the SetLayeredWindowAttributes call) and the canvas leaves a filled black box....
In the original InvalidateRect() crash, though it crashed, the canvas was translucent (semi-transparent) along with its window on Win2k/XP.
If anyone has a decent workaround to fake it somehow e.g. get under the window without any strain on older PCs, I'm definitely interested (maybe better to make a new thread for that if it's confirmed this cannot work).