|
I wrote a tool a while back that I use to see exactly what every step in my code is doing when working with bitmaps. Check it out, maybe it will help you spot the problem.
http://www.codeproject.com/tools/imageviewer.asp[^]
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good - Use it!
|
|
|
|
|
I put all the components where instructed, and it doesn't seem to do anything. Does it matter that I'm using VS2005?
Nevermind - stupid programmer tricks. 
-- modified at 12:41 Thursday 27th July, 2006
|
|
|
|
|
Well, the "targetDC" device context appears to change when I copy the images to it, but when I try to do the last "pNewTargetBmp = targetDC.SelectObject()" call in the code above, the viewer won't show the bitmap.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
I found that the resulting bitmap on the last SelectObject call is nothing but a single pixel centered in what would be the image.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
The single pixel is the default bitmap that is selected into a memory device context. If that is what you see that means you are not successfully selecting a bitmap into that device context. You have to create a memory bitmap the size and bit depth required, and use SelectObject() to attach it to the memory device context. The memory device context will then do all it's drawing onto that bitmap.
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good - Use it!
|
|
|
|
|
John Simmons / outlaw programmer wrote: I found that the resulting bitmap on the last SelectObject call is nothing but a single pixel centered in what would be the image.
Are you looking at bmpTarget or at pNewTargetBmp. Your final image should be in bmpTarget at this point.
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good - Use it!
|
|
|
|
|
targetDC.BitBlt(0, 0, nTargetWidth, nTargetHeight, &sourceDC, 0, 0, SRCPAINT);
ShowBitmap(bmpTarget);
pOldSourceBmp = sourceDC.SelectObject(&bmpLabs);
targetDC.BitBlt(nSrcWidth, 0, nTargetWidth, nTargetHeight, &sourceDC, 0, 0, SRCPAINT);
ShowBitmap(bmpTarget);
targetDC.SelectObject(pOldTargetBmp);
m_ResultsImages.Replace(0, &bmpTarget, NULL);
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good - Use it!
|
|
|
|
|
I use some console application running it from inside VC project and I want to redirect its output to file
bool runprocess(wchar_t *cmnd)
{
SECURITY_ATTRIBUTES sattr;
memset(&sattr,0,sizeof(sattr));
sattr.nLength = sizeof(sattr);
sattr.bInheritHandle = true;
STARTUPINFO sInfo;
memset(&sInfo,0,sizeof(sInfo));
PROCESS_INFORMATION pInfo;
memset(&pInfo,0,sizeof(pInfo));
sInfo.cb = sizeof(sInfo);
sInfo.dwFlags = STARTF_USESTDHANDLES;
bool res = CreateProcess(0,cmnd,0,0,true,NORMAL_PRIORITY_CLASS|CREATE_NO_WINDOW,0,0,&sInfo,&pInfo);
if(res)
WaitForSingleObject(pInfo.hProcess, INFINITE);
return res;
}
runprocess(L"consoleapp.exe >output");
But the file output is not created though consoleapp worked normally?
How to get its output without reading hStdInput, hStdOutput from STARTUPINFO structure?
9ine
|
|
|
|
|
Since you are using the STARTF_USESTDHANDLES flag, you also need to open files for standard input, output, and error, and set their HANDLE values in the STARTUPINFO structure. Also, remove the "> output" from the command line, since you are already doing the redirection.
Software Zen: delete this;
|
|
|
|
|
hi i want to use API PfBindInterfaceToIPAddress(ihandle,PF_IPV4,(PBYTE)"202.165.250.50") and in this i had to supply the ip adress as byte but i want to do with byte like
byte i[]={205,25,236,25};
but it gives error so i had to use as in above api but it did not work tell me how to do that.
i thinks so this function faildue to that
-- modified at 9:42 Thursday 27th July, 2006
|
|
|
|
|
you could simple split the string by searching the '.' characters, but it can become mmuch more complicated if you have to check if the ip is valid...
consider this :
"304.6458.0.12"
|
|
|
|
|
int i[]={202,165,250,50};
AfxMessageBox("Step 1 Done");
PBYTE ip=(PBYTE)i;
I had used this as ip but still functin does not succeed i think it has some other problem.
Tasleem Arif
|
|
|
|
|
tasleem143 wrote: int i[]={202,165,250,50};
AfxMessageBox("Step 1 Done");
PBYTE ip=(PBYTE)i;
If you want a BYTE array then declare it as a byte array
BYTE i[] = {202, 165, 250, 50};
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good - Use it!
|
|
|
|
|
I'm finding a solution to make the mouse pointer to hourglass during wait for some process in my project.
Please give me some information of this.
|
|
|
|
|
{
CWaitCursor foo;
...wait for some process in your project...
}
when foo goes out of scope, the cursor will become an arrow again
|
|
|
|
|
If this is with MFC, use CWaitCursor. Otherwise, handle the WM_SETCURSOR message.
"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
|
|
|
|
|
|
I use VC++ 6.0 and i have a date picker. My problem is that whenever I start the program it start with the date being set to 01.01.1970. How can I set it to start with today, let's say?
|
|
|
|
|
tanarnelinistit wrote: How can I set it to start with today, let's say?
With the SetTime() method.
"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
|
|
|
|
|
Hi,
I have used CRITICAL_SECTION to make my code thread safe and I was wondering if there is some way of testing it. I can call the code from two different threads and the code doesnt appear to screw up - but how do I really know that the cricial sction has blocked one thread until the other has completed rather than just being (un)lucky and both threads never actually called at the same time?
Is there something I can put in there to record that two threads have attempted to access the same resource?
TIA
Tony
|
|
|
|
|
 Do you always test things like that ? Did you check if the if/else statments were doing their job, or if CreateThread is really creating a new thread  ?
Seriously, if you use them like it is documented, they will work how it is documented. No need to be paranoid  .
|
|
|
|
|
Hi,
Thanks for the reply.
Yes I do like to test stuff like that - I try to test all my code, including whether my if/else's do what I expect them to do. Not that I don't trust the compiler, but I sometimes write stuff that doesn't work - maybe its just me 
So if I understand your correctly, if I 'think' I understand the documentation and it 'appears' to work - then it must be OK - non need to test it right? 
I just wnated to make sure that my code is robust, no corruptions - no deadlocking - that kind of stuff. Then I can sleep at night.
Cheers 
Tony
-- modified at 9:38 Thursday 27th July, 2006
|
|
|
|
|
You sqid this:
softwaremonkey wrote: but how do I really know that the cricial sction has blocked one thread until the other has completed rather than just being (un)lucky and both threads never actually called at the same time?
I understood that you wanted to check if the critical section were working properly, not your code. In that case, I think it is a litle bit useless to verify things that are used by milion of people 
But I understand now (yes, I know, my brain is slow today  ) that you want to check your code. Something that comes to my mind: in your thread, you can simply make a very lenghty operation (like a double for loop) that is inside a locked section. Then, with the other thread, wait that the critical section is freed. Log the times in a file to see if the second thread is really waiting for the critical section. Of course this is a basic scenario but you can improve it (e.g. use a lenghty operation in both threads)
|
|
|
|
|
Hi,
Thanks, I will try that.
Incidentally, I came across this intersting article about testing critical sections...
http://msdn.microsoft.com/msdnmag/issues/03/12/CriticalSections/default.aspx
It also has some code for some kind of debugging tools. I havent checked it out yet - still reading the article.
Thanks again for the help.
Tony 
|
|
|
|
|
A simpler test:
have a volatile bool variable with global lifetime, visible in the critical section of code.
Initialize to zero before you start the thread(s).
Directly after Lock, check reentrancyFlag == 0
set flag to 1
Upon exit, set to 0
Make sure that you never forget to reset to zero even if you exit early through return or exception (e.g. through a scopeguard[^])
For a very critical test, put a Sleep() into the protected block 8debug build only, of course), so that overlaps are much more likely.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
