Specifically, That will be used with C++11 in 32 bit, That will be used with CODE::BLOCKS 17.12 , I am referring to bitmap irregular regions , I am referring to 2 individual bitmaps (irregular regions) ,
I have tried this. I have made one bitmap region show up and move (with and without a form showing behind it).
What I want to do is this using double (or triple?) buffering.
I want to Create an irregular region from a bitmap using bitblt and masking. (I can do this).
I want to Create a second irregular region from a second bitmap using bitblt and masking. (I can do this).
I want to Combine the two irregular regions into one larger irregular region, showing bitmap region #1 in front of #2 partially covering it up. (I tried this multiple times and I do not know how to make it work even after reading multiple web sites and books).
I want to Copy? the combined irregular bitmaps to the screen (dc?).
I have had this almost working multiple times. I found examples of how to do this but with boxes and circles etc. but I do not yet understand how to use those examples for irregular regions.
I even created (maybe lost it in my attempts) two separate regions that I could put one in front of the other, and move either one with the mouse, but where the front one covered the back one it permanently removed that area of the back one. This is getting old. I need clean code that I have not misinterpreted and messed up, that shows how it is done.
For now I need to get this cleared up. Were to start. I have lots of books that I am reading on C++. I researched the internet for examples, and got worthless (to me) Visual Studio and .net stuff that "claims" to be C++ but has to be interpreted (by me) to work without Visual Studio and .net.
C++11. Two irregular Bitmap regions that are movable. On a form that can be either visible behind them or invisible behind them. Neither irregular bitmap, when in front, permanently removes part of the irregular bitmap that was behind.
My code: It is a mess. I do not want to show it unless you say that I have to.
Thank you.
Aucun commentaire:
Enregistrer un commentaire