Bitmap question: HBITMAP

Question

0.00/5 (No votes)

See more:

Using SetBitmapBits is confusing me. Is its sole purpose to transfer my array of pixel info to a buffer owned by the handle "HBITMAP" ?

Is there a way to know where this buffer is located and write to it directly?

Seems like a waste of time to draw on your own array and then perform a huge array copy by calling SetBitmapBits(HBITMAP, size, source[])

Or am I out of my mind and there's something I'm missing about all this? (It's happened before...)

I have looked everywhere for what SetBitmapBits/GetBitmapBits actually do and have found nothing other than the fact you must call them. (Or their newer counterparts SetDIBits/GetDIBits: but these seem they should be even slower.)

Thanks in advance!

Posted 10-Jul-11 6:23am

Bob Namenottaken

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Emilio Garavaglia · Answer 1 · 2011-07-10T20:35:00

Solution 1

GDI object's internal data don't belong to your process but to the GDI subsystem. You cannot read/write to them directly because there is a "process boundary" in between (they can even be on another machine!).

The memory itself can be moved around by the GDI functions, without your program even notice. It would be quite hard to give you a memory address to that.

Posted 10-Jul-11 20:35pm

Emilio Garavaglia

Comments

Bob Namenottaken 11-Jul-11 8:38am

Thank you. I understand that - I just don't like the idea of wasting the time with the copy. But I'm ok if "that's the way it is". I was just wondering if experienced programmers had a tcehnique to avoid the copy.

Emilio Garavaglia 11-Jul-11 10:25am

unfortunately, it is not a matter of experience. Simply, the system is not designed to work that way.