In the evening, I met a very varied matter: I have established a resource DLL file with VS2003, then put a number of GIF files in the inside, then compile, it looks so perfect. However, it was later when it was used. I can't help but study, I found that the original vs203 secretly turned the GIF file into the BMP format and stored, and finally entered the DLL to go to the GIF skin BMP file, no wonder I have to fail when I read. Moreover, the file in the JPG format did not escape its pockets, and it was converted, and he did not say hello. Also, the conversion behavior is starting from the introduction of the document into the resource.
My god, if you have a rebellion, what can I do in addition to crash?
So my procedure is so down, so my beautiful evening is dedicated to the keyboard and the display ...
Tell me that in addition to wanting to swear, I should have a better reaction?
I believe that the developer must think so: 俺 code only knows BMP, you call you to work, so it is called 俺 to handle BMP, so you give you what picture is turned into bmp ...
But you at least say hello to me! ?
Therefore, many times, we have thought a lot for users, thinking a lot. In fact, many times the user will not be grateful, and the opposite will feel very dissatisfied. I have received itself. Do not think about the problem from the perspective of the recipient, and more payable can only be exchanged.
BTW, the solution to this problem is this: the suffix name of the picture file is deleted. The VS2003 determines whether or not the file format is required, it seems to rely on the file's suffix name. In this way, the file that deletes the name of the columns is stored by the old man as the binary data file, no one is carrying your files to your file.
Welcome to the author's personal homepage: http://www.mrspace.net/
