"Hector Santos" <sant9442@nospam.gmail.com> wrote in message
news:ufF$nt3yKHA.928@TK2MSFTNGP05.phx.gbl...
Peter Olcott wrote:
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in
message
news:ndgkq5lbilsibpqql11bi0d0tp6b6psl6q@4ax.com...
If you want text on a dialog box, place a static control
there and use SetWindowText to
tell it what to display.
I don't think that will work because I need to specify
every detail of the text, its font, foreground color, et
cetera. In any case this is all moot now anyway. I am
simply bitblt-ing my memory bitmap to the window.
Developing the style of writing directly to a dialog box
surface will eventually uncover a
large set of problems, none of which you want to deal
with.
joe
This is only for internal testing purposes.
Then even more the reason to just use the IDE and controls
as to not waste time learning something you will never use
anyway - like Intel Chip Caches. :)
--
HLS
Here is an interesting note that I don't understand. A
slight revision (to make it a little less CPU intensive,
thus more memory intensive) only actually achieves 21 MB per
second of the 12 GB / second maximum RAM speed. (RAM speed
reported by MemTest86).
const uint32 size = 100000000;
std::vector<uint32> Data;
uint32 Max = 0x3fffffff;
void Process() {
clock_t finish;
clock_t start = clock();
double duration;
uint32 num;
for (uint32 N = 0; N < Max; N++)
num = Data[num];
finish = clock();
duration = (double)(finish - start) / CLOCKS_PER_SEC;
printf("%4.2f Seconds\n", duration);
}
Another thing that I don't understand is that it crashes
when
num = Data[num];
is replaced by
num = Data[N];
1. You never initialize num, so executing num = Data[num] will access
2. You never resize the vector space "Data" before you attempt to