Microsoft Detours 1.5
Hello everybody! I've a problem with MS Detours Library. I've installed MS Detours on my Win XP SP2 (with Visual Studio 2005) to build my DLL that helps me to solve lots of problems. The DLL runs on my system but when I put my DLL on an other system (Windows XP SP3 on VirtualPC - so, windows. Well, after some tests I found that the DLL is not.
Chris Maunder 12-Jul-09 23:37 12-Jul-09 23:37 Apologies for the shouting but this is important. When answering a question please:. Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, or mark it down.
Insults are not welcome. If the question is inappropriate then click the 'vote to remove message' button Insults, slap-downs and sarcasm aren't welcome. Let's work to help developers, not make them feel stupid. Chris Maunder 12-Feb-09 18:19 12-Feb-09 18:19 For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C forum will end in tears. Be specific!
Don't ask 'can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with. Keep the subject line brief, but descriptive. Eg 'File Serialization problem'.
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can. Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked. Do not remove or empty a message if others have replied.
Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add 'Solved' to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you. If you are posting source code with your question, place it inside tags. We advise you also check the 'Encode HTML tags when pasting' checkbox before pasting anything inside the PRE block, and make sure 'Ignore HTML tags in this message' check box is unchecked. Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question in one forum from another, unrelated forum (such as the lounge). It will be deleted. Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums. No advertising or soliciting. We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal. Cheers, Chris Maunder The Code Project Co-founder. Again Richard MacCutchan is correct so let me explain my code name is a 'pointer to a char' NOT a char So this line if (name && namemax 1) Is a shortcut of writing if ( (name!= 0) && (namemax 1) ) writing if (anything) Basically checks if the thing called 'anything' is not zero its a shortcut So what the line it is checking is the pointer called name is not 0 (or null which is an invalid pointer) the space for the buffer name is greater than 1.
Microsoft Detours 1.5 Free
Why well the code specifically makes an ' 0' terminated C string so it needs a minimum buffer size of 1 to hold the ' 0' So name 0 or namemax 0 would bug the code so they are specifically handled. So the line is a specific safety to make sure you could NEVER bug the routine doing either the function will simply return 0 which is correct it read no character data.
There are a couple of other possible background bugs and program hints which was in my hint to change the interface. 1.) The use of 'stdin' could be possibly problematic in some esoteric systems. You don't know it's actually a device there might be no keyboard etc on the system.
As such bringing it in thru the interface pass that responsibility out to the caller code. 2.) We don't ever change name or namemax internally so placing a const in front of them makes it clear that is the case and also allows the optimizer to really go to work. So it's not a bug fix but a help to the compiler and anyone using the code. So that is as robust to function input error as I can make your function.
Microsoft Detours 1.5 2017
You are left with two possible errors outside my control passing in a pointer to some wrong place and passing in a wrong maximum buffer size. I would have to be a mind reader to be able to deal with those but I have dealt with all the obvious possible errors.
Singersinger wrote:PostThreadMessage(mpThread-mnThreadID,WMMSG,0,(LPARAM)sString.GetBuffer(sString.GetLength)); u pass a pointer to the function. Some times by the time the message was recieved by the thread, sString have got desctructed. So the memory that the lParam was pointing will b a invalid one. Try the bolow approch. LPTSTR lpMessage = new TCHARsString.GetLength; tcscpy( lpMessage, sString); PostThreadMessage(mpThread-mnThreadID,WMMSG,0,(LPARAM)lpMessage); and in the thread side LPTSTR lpMessage = (LPTSTR)pMsg-lParam;; CString s = lpMessage; delete lpMessage; AfxMessageBox(s).
Born in South Africa in 1939, flugelhorn, trumpet, and cornet virtuoso Hugh Masekela was inspired by American jazz as a young boy and served an extensive apprenticeship with some of his homeland's musical giants. In 1959, he and pianist Dollar Brand (aka Abdullah Ibrahim) formed the legendary Jazz.Missing. Hugh masekela hedzele. Find a Hugh Masekela - Live At The Market Theatre first pressing or reissue. Complete your Hugh Masekela collection. Shop Vinyl and CDs.Missing.
Waldermort 15-Sep-06 9:59 15-Sep-06 9:59 Image distortion algorithms are hard to find, and c/c examples are very rare. I am rendering a ripple effect (stone into a pond) onto a bitmap. The algorithm itself is quite easy yet I have noticed an annoyance (and also noticed it in every example I have found. When the bitmap is distorted the top and bottom is pulled away from the edge, revealing the origional bitmap beneath, also the left and right edges are 'how to say' wrapped around, ie the void space is filled using pixels from the opposit edge. I know that GIMP allows the option of either filling the void with the opposite edge, or filling with a brush. But both of these solutions don't look realistic.
I'm open to suggestions. You could enlarge the source image by wrapping the opposite edges some ammount of pixels, so that you ripple a larger image, but it will be clipped to the source image size; but you might have some problems with the corners Attempt to some ASCII art drawing showing what I mean: source image +-+ +-+ enlarge source image aaaaaaaaaaaaa aaaaaaaaaaaaa +-+ yy xx yy xx yy xx yy xx yy xx yy xx yy xx yy xx +-+ bbbbbbbbbbbbb bbbbbbbbbbbbb does that make sense? Waldermort wrote:I could do the enlargment before I even touch into the ripple code sure. But i think doing them at the same time would be faster (though speed isn't the top priority in all situations).
My code does something like this: for each output pixel (x,y): run the ripple calculations backwards to find the source pixel (a,b) since a and b are fractions interpolate from multiple source pixels to find the output color if the source image is 100x100 to scale based on crop rect (10,10, 90,90) (for example), i would do this: for each output pixel (x,y): run the ripple calculations backwards to find the source pixel (a,b) scale a,b from the source rect into the crop/zoom rect interpolate from a,b. Just a thought. Bloodwinner wrote:case WMCREATE to realise it WMCREATE: The WMCREATE message is sent when an application requests that a window be created by calling the CreateWindowEx or CreateWindow function. (The message is sent before the function returns.) The window procedure of the new window receives this message after the window is created, but before the window becomes visible. WMPAINT: The WMPAINT message is sent when the system or another application makes a request to paint a portion of an application's window ie when we want to draw something on the window. Because when Windows wants to repaint a window, because an obscured part was exposed or for another reason, it sends a WMPAINT message to the window to get it to repaint itself.
If you put the rendering code elsewhere you'll see the rendering but when a part of the window is obscured and then exposed (or for some other reason needs to be re-rendered) the WMPAINT handler will regenerate the image but it will not include the line. Aside from this I suspect the WMCREATE handler is too early anyway. This situation is set to change with Vista's DWM but still the WMPAINT handler will remain the correct place to perform most rendering operations.