 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Fishface
Guest
|
 Posted: Thu Jul 31, 2003 1:20 am Post subject: Re: Problem with BitBlt function |
 |
|
Ruby wrote:
| Quote: |
Hi, this code works (I can see the image) only when i enable
line 2, why? Why "ProcessMessages" is not enough for it to work?
On a timer event ( Every 200ms) -
1: BitBlt( Form1->Video_Data->Canvas->Handle,
0, 0, 50, 50, TempPic->Canvas->Handle,
0, 0, SRCCOPY );
2: // Form1->Video_Data->Refresh();
3: Application->ProcessMessages();
|
I'm going to take a wild guess and say Video_Data is a
TImage. When you modify the bitmap using the API,
how else is the TImage supposed to know that it has
been modified? Yes, you have to tell it so that it knows
to redraw itself.
|
|
| Back to top |
|
 |
Ruby
Guest
|
| Posted: Sun Aug 03, 2003 7:34 pm Post subject: Re: Problem with BitBlt function |
|
|
OK, Thanks :-)
"Fishface" <invalid (AT) ddress (DOT) ok?> wrote:
| Quote: | Ruby wrote:
Hi, this code works (I can see the image) only when i enable
line 2, why? Why "ProcessMessages" is not enough for it to work?
On a timer event ( Every 200ms) -
1: BitBlt( Form1->Video_Data->Canvas->Handle,
0, 0, 50, 50, TempPic->Canvas->Handle,
0, 0, SRCCOPY );
2: // Form1->Video_Data->Refresh();
3: Application->ProcessMessages();
I'm going to take a wild guess and say Video_Data is a
TImage. When you modify the bitmap using the API,
how else is the TImage supposed to know that it has
been modified? Yes, you have to tell it so that it knows
to redraw itself.
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
