And see an article Date and Time in C++[^] about timer and date ;) WhiteSky

See GetActiveWindow WhiteSky

Your CImage object goes out of scope at the end of the function so it probably destroys the HBITMAP via its destructor. Instead of m_bitmap = (HBITMAP)image; try m_bitmap = image.Detach(); and remove this line: if (m_bitmap) DeleteObject(m_bitmap); Mark

WhiteSky, no i do not see a null value of variable because when i come into the showPicture() function the very 1st thing crashes... CPaintDC dc(this); which gives me an error: it crashes and gives this error: Debug Assertion Failed! Program: c:\..\test.exe File: f:\..\ship\atlmfc\src\mfc\wingdi.cpp Line: 1090 Press retry to debug application When I press re-try it goes to this code: ASSERT(::IsWindow(pWnd->m_hWnd)); in wingdi.cpp CPaintDC::CPaintDC(CWnd* pWnd) { ASSERT_VALID(pWnd); ASSERT(::IsWindow(pWnd->m_hWnd)); if (!Attach(::BeginPaint(m_hWnd = pWnd->m_hWnd, &m_ps))) AfxThrowResourceException(); } my reply to James' post: my dialogs are modeless... that's why i thought that this would work. what i'm trying to achieve at the end is to have 3 separate window where we can view pictures from 3 separate cameras we collect data from and 1 dialog box that controls the camera.... if I had just a dialog based app my code works. i simply initialize everything in ::OnInitDialog() and then it has a function called ::OnPaint() that I can call showImage().... It is in an MDI application where everything gets hazy... since it doesn't have an ::OnPaint() or ::OnInitDialog() function. Please advice. thanks, Kitty Kitty5

kitty5 wrote: .. imageViewer::funcA(); To make such call possible. finA() must be static function of class imageViewer. Prasad Notifier using ATL | Operator new[],delete[][^]

Are you sure you want to do this? Our product currently has this scenario in several places and it is a nightmare to maintain, especialy where help is involved. Just this week I separated one of the .h/.cpp pairs so that each was using its own dialog template. The dialog templates are almost identical so the original author thought it would be neat if only one class serviced both templates. Yuck! "Approved Workmen Are Not Ashamed" - 2 Timothy 2:15 "Judge not by the eye but by the heart." - Native American Proverb

afaik you can't get that level of control over the hardware. You could try a much faster dedicated PC, but windows isn't a realtime OS, and you can't force it to absolutely favor any one application over the remainder of the system. I don't know if a realtime OS (some linux variants qualify) would give you absolute control over the bus either. You could also try reducing the amount of hardware on the PCI bus. Im not sure that just PCI cards that use it though, so you'd need to research the mobo chipset to find out what if anything else is routed through it. Newerboards would probably be less likely to run devices off it instead of doing a direct Device-Northbridge-Cpu connection.

When you allocate a chunk of memory, what you get is a memory chunk at least as big as what you requested, and some extra data. The whole chunk looks like this: [ Extra Data ][ Your data - X bytes ] The pointer which new returns, is the adress of the first byte of [ Your data ]. The [ Extra Data ] chunk is used later on when you deallocate the memory. When you pass a pointer to delete for deallocation, delete will actually "step back" and take a peek at what's inside [ Extra Data ]. That chunk of data contains book keeping information about the memory allocation - which it really needs to be able to put the allocated memory back into the pool of unallocated memory. If you increment the pointer value, it will no longer point to the beginning of the data chunk which new returned. So when you pass the modified pointer to delete, it will not find the book keeping information when it "steps back". It will find data from which you put into your data chunk, which delete will interpret as garbage... -- Torn from tomorrow's headlines

kitty5 wrote: but whenever I try to do: if( processInfo->szExeFile == _T("hello.exe")) it doesn't work. and when I try to print out cout<szExeFile; I get "Name: 0036630C"... processInfo->szExeFile is a pointer. When you try comparing it or print it you are really testing the address. You should de-reference it first ie if( *processInfo->szExeFile == _T("hello.exe")) cout<szExeFile;

This is just a guess, but I would imagine that the card would treat the FIFO like a buffer stream. That is, you will always be reading from the top fo the stream, so you would always pass in 0 to ReadFile. If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week Zac

If (1) your "black & white video data" is actually "8-bit grey-scale" (which is what one might expect from a video camera), and (2) the image size is fixed (number of pixels horizontal & vertical is known), it could be quite easy. Create a window to use to display the images Create a bitmap header. Set the bitmap parameters (number pixels X & Y, pixel depth, not using pallette, etc) Read the binary file into some area in memory Set the bitmap header "data" parameter to point to your data Use SetDIBitsToDevice to display it in your window. Repeat the last 3 steps until stopped If the video has unusual attributes (for example, it is 12-bit greyscale from a medical imager, or if it is in columns not rows) you will probably need an intermediate step, to create a bitmap which Windows understands.

See AfxBeginThread[^] _** **_ WhiteSky

kitty5 wrote: buff = new ULONG[11250000]; //total of 11,250,000 32-bit words Just an FYI: Avoid declaring such large chucks of memory (be it stack or heap). While this array alone (which will be about 45 MB) won't cripple your system, imagine declaring 10 or 20 of them (throughout your application). Next thing you know, your application requires a full GB of RAM by itself (not good!). If possible, you should try to read a large file in smaller chunks, process the data, and read the next chuck. If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week Zac

Found it! it's the MAKELONG macro! DWORD MAKELONG( WORD wLow, WORD wHigh ); yeay! Kitty5

bob16972 wrote: This sounds like a homework assignment. Not even remotely. "Money talks. When my money starts to talk, I get a bill to shut it up." - Frank "Judge not by the eye but by the heart." - Native American Proverb

kitty5 wrote: do I access buff the same as an array? yes Let's execute on the customer-facing market-driven swim-lane paradigm!

Zac Howland wrote: It sounds like you are treating your dialogs as modal dialogs (that is, you are calling DoModal at some point). Yes, that was exactly what I was doing. Ok Cool. I figured it had something to do with the DoModal function that I was messing up on. Thanks! You ROCK! :-D Kitty5

GO IT! Thanks!:-D Kitty5

:-D Ok, I've figured out how to get the dialog boxes to exchange data. Now I'm trying to figure out how when you have one dialog box open how you can open another one while the 1st box is still open and functioning. Right now when I have a dialog box open I can only work in the one box and can't click on anything outside it (i.e. clicking on the toolbar to open another dialog box or getting the about box to come up isn't working...) I guess I'm looking for making these dialog boxes work like child forms in an MDI MFC App. Thanks, Kitty5 -- modified at 9:17 Friday 21st July, 2006