On Wed May 29 07:05:40 2024 +0000, Elizabeth Figura wrote:
I took a look at it again and it reliably sets the last error each
time it's called. I added a condition to separate the two errors. It always sets ERROR_SUCCESS when it creates a d3d9on12 object, otherwise it sets it to ERROR_TOO_MANY_POSTS, which is an odd error to set it to. That only necessarily means that the function calls something which clobbers the last error. If it's not documented to set the last error, and no program has been shown to depend on it, then I wouldn't test or implement that behaviour.
Okay, I'll remove it in the next push.