saving the processor

o i c....
yea it works now...tks a lot....:)


well, speed is not a major concern in this case for me...

but can u pls tell me how can i make the flashing stop in the PeekView pls???
you asked me to put InvalidateRect(0) for the time being...
so how can i change it so that it doesnt blink anymore??

hope you can pls help....tks a lot...appreciate your help...:)

Take a look at the attached project.
The following functions have changed a bit:

Code:

---

CPeekView::OnDraw
CPeekView::OnUpdate
CPeekView::OnEraseBkgnd

CEditorView::OnDraw
CEditorView::OnUpdate
CEditorView::OnEraseBkgnd

---

Once again, it's slow. You need to use CreateDIBSection.

Of course, I forgot to attach the attachment :blush

Joe, just a general suggestion: I don't understand why you use a 2D array to store the bitmap data, and SetPixel() to render it in the PeekView? Your data is a bitmap, right? So why don't you just take a CBitmap and attach it to your doc? The doc's GetSquareColor() / SetSquareColor() would then have to be implemented to access that bitmap (using, for example, something like GetBitmapBits() / SetBitmapBits()), and the PeekView would simply take that bitmap and BitBlt() it to its DC. There's no point in having an additional 2D array of pixels to store the bitmap data when you can simply store it in a CBitmap.

BTW, thanks for your XMas greetings. I also wish you to have had a nice XMas, and wish you a Happy New Year. :)

Quote:

---

Originally posted by gstercken
Joe, just a general suggestion: I don't understand why you use a 2D array to store the bitmap data, and SetPixel() to render it in the PeekView? Your data is a bitmap, right? So why don't you just take a CBitmap and attach it to your doc? The doc's GetSquareColor() / SetSquareColor() would then have to be implemented to access that bitmap (using, for example, something like GetBitmapBits() / SetBitmapBits()), and the PeekView would simply take that bitmap and BitBlt() it to its DC. There's no point in having an additional 2D array of pixels to store the bitmap data when you can simply store it in a CBitmap.

---

o i c...actually i started with the array for the grid purposes...then came all the way here...so continued using it.....:(
didnt know could do such a thing too...:(

Quote:

---

Originally posted by gstercken
I also wish you to have had a nice XMas, and wish you a Happy New Year. :)

---

sure did..tks..:)

Quote:

---

Originally posted by Marc G
Take a look at the attached project.
The following functions have changed a bit:

Code:

---

CPeekView::OnDraw
CPeekView::OnUpdate
CPeekView::OnEraseBkgnd

CEditorView::OnDraw
CEditorView::OnUpdate
CEditorView::OnEraseBkgnd

---

Once again, it's slow. You need to use CreateDIBSection.

---

tks a lot...

it doest really matter if its slow...cause the editting will be on pixel by on pixel....
so speed wise i think there shouldn't be much prob...

is there anything else i can do on it for betterment???

Yes, like we've already told you a few times. Instead of using an array to store the pixels, store them directly in a CBitmap or DIB section.

i have never used CBitmap or DIBSectiona nd i ahve to copmplete this proj by 20th Jan..:(
can i just leave it like this and proceed further???:( :o
will i run into trouble later???:confused: :(

No, you will not run into any troubles, except for the program being slow, especially for 640x480.

can u pls tell me, if i want to incorporate DIBSection, how do i go about it?

I've changed your project a bit to work with a memory bitmap instead of an array. See attached project.

This version is extremely fast while editing the bitmap (bitmaps upto 6400x4800 and possibly even higher, do mind that the scrollbars overflow with this kind of images!), but there's still a bit of flicker when scrolling the big editing view.

Note 1: The code is a mess, but i don't have time to clean it. It could be even the case there are some redundant lines of code, but you get the idea.

Note 2:I've also removed all the LOENGLISH coordinate stuff, because without it it's much more simple to draw stuff.

And again i forget to attach the **** project :mad:

LOL ... this board replaces some words with *'s. The word i typed wasn't even a bad word!

so setting LOENGLISH is bad??:confused:

Quote:

---

Originally posted by Joseph_R_Thomas
so setting LOENGLISH is bad??:confused:

---

Not bad, it just depends on your needs: If you need to deal with real world units like cm, mm, inches or TWIPS, those mapping modes are fine. But as in your case, where you merely want to enlarge the bitmap's pixels by some fixed factor to edit them, MM_TEXT or MM_ISOTROPIC are far more suitable and easier to use (haven't you read the GDI chapters in Prosise's book ;) ?)