|
Oliver123 wrote: So, any ideas on how to fix this without restarting?
Yes
Oliver123 wrote: When my program blows up
Fix the bug that causes the crash. Also you can put exception handling in your code that would notify you of the error without crashing the process.
led mike
|
|
|
|
|
led mike wrote: Also you can put exception handling in your code that would notify you of the error without crashing the process.
I'm a member of the school that thinks this is rarely a good idea. If you're got a crash let it crash; it makes the bug easier to locate and fix. Also it means that JIT debuggers can be used. Also for clients, Dr.Watson will generate a crash dump file (if configured to do so) which can be used for postmortem debugging. In short if a program crashes, the best thing for it to do is crash.
Steve
|
|
|
|
|
Well he is talking about a "developer problem" not a production problem. I use exception handling to debug all the time. I find that a stack trace is extremely helpful in locating bugs. 
led mike
|
|
|
|
|
Oliver123 wrote: When my program blows up...
ALWAYS wear eye protection. I prefer goggles and a flight helmet.
If you're running in the debugger (sounds like no) you can Shift-F5 stop debugging.
Otherwise CTRL-ALT-DEL, find tradingdemo.exe in the list of running processes, and end the
process.
|
|
|
|
|
You forgot the final step:
format c:
led mike
|
|
|
|
|
led mike wrote: You forgot the final step
Yeah I guess a quick format isn't too "Time consuming".
edit: format /Q c:
Mark
|
|
|
|
|
I bet that the "tradingdemo.exe" process is still running. Check in task manager. If it is just kill it and you should be able to rebuild.
Steve
|
|
|
|
|
Hi,
I have a Dialog application. In some cases I am displaying data in the main dialog by accessing data in an array:
str2.Format("%02d\t, m_Parse.mChannel[i].m_SV);
str+=str2;
SetDlgItemText(IDC_SAT, str);
etc.
etc.
What I want to do is to have some of the data displayed in different colors other than black. How can I set the color of some data before displaying it?
Can someone help me out?
Jerry
|
|
|
|
|
I think the only control that would allow you to mix colors in the text would be a rich edit
control. You could use read-only rich edit controls.
If that's way overkill for just colored text, you could render the text yourself in response to
the WM_PAINT message using perhaps some/all of these functions:
SelectObject() to select a NULL brush (NULL_BRUSH) into the DC or possibly another font as well
SetTextColor()
SetROP2() to set the foreground mixing mode (to R2_COPYPEN, for example)
SetBkMode() to set the background mixing mode (to TRANSPARENT, for example)
DrawText() to draw the text
Just two possibilities
Mark
|
|
|
|
|
|
|
if your control is Edit see WM_CTLCOLOREDIT
|
|
|
|
|
Ok I will take a look at that...thanks, have a good day.
Jerry
|
|
|
|
|
And see MSDN WM_CTLCOLOR notification.It has an example and also you can see another CTLCOLOR_*
|
|
|
|
|
Hello!
I have been having trouble understanding the function DrawText as defined in the MSDN Library:
int DrawText(HDC hDC, LPCTSTR lpString, int nCount, LPRECT lpRect, UNIT uFormat);
Can someone provide a simple example as to what this function does? Any help given me to better understand this function is appreciated.
Mike
|
|
|
|
|
The first parameter is a device context. It's a handle to whatever you're drawing on. It could be the screen, a bitmap, printer, etc.
The second parameter is the string you want to draw - no mystery there.
The third parameter tells DrawText how much of the string it should draw - i.e., the length of the string. You can pass it -1, if you want it to draw the entire string.
The fourth parameter is a bounding rectangle, in which the function will draw the text. The coordinates of the rectangle are in whatever units your device context is set to use. A screen device context would typically use pixels as coordinates.
The last parameter tells DrawText how it should go about drawing the string. The DT_SINGLELINE flag specifies that the text should not be broken into several lines. DT_RIGHT would align the text to the right hand side of the bounding rectangle. DT_END_ELLIPSIS tells DrawText to draw "..." on the right hand side, in case the entire text does not fit in the bounding rectangle. These are just some of the flags that exist. I suggest you look at the MSDN documentation for more information. The flags can also be combined using the or operator. For instance: DT_RIGHT | DT_SINGLELINE would tell DrawText to draw the text on one line, and align it to the right.
--
The Show That Watches Back
|
|
|
|
|
Did you see DrawText on MSDN it has one example of it
|
|
|
|
|
Does anybody know how to prevent child windows from drawing over a certain region of the parent window? My top level window has custom borders, when resizing the child controls are moved/resized. In some instances the child control will paint over the custom borders, I would prefer the children to instead be cropped leaving the borders intact. I know this can be avoided using MINMAXINFO but is there any way to do this using regions and/or WM_PAINT/WM_ERASEBKGND?
|
|
|
|
|
How about using the SetWindowRgn() to set the fdrawable region in the window?
Mark
|
|
|
|
|
I don't see how that would work. I have basically redefined the whole client area of the window. The new borders are rounded. I am already calling SetWindowRgn() to create a rounded window. I have at my disposal a window region, a client region, a border only region and a child clipped region. Basicaly I only want to allow the children to draw within the client region, but I have no idea where and how to set this.
I have tried everything I can think of within WM_PAINT, but nothing seems to be working. Could you suggest anyplace else where I might set/exclude a region?
|
|
|
|
|
waldermort wrote: I am already calling SetWindowRgn() to create a rounded window
What region do you set with SetWindowRgn()? It should be the client region, not the window
region, right?
Mark
|
|
|
|
|
Mark Salsbery wrote: It should be the client region, not the window
region, right?
Wrong!
|
|
|
|
|
I use the 'window region' to set the window region. The 'client region' is the 'window region' excluding the border (there is no caption bar), this is the only place I want child controls to be able to draw. The 'clipping region' is the 'window region' excluding the regions of the child controls which is selected into the DC on WM_ERASEBKGND to prevent flickering (much the same as WS_CLIPCHILDREN).
Idealy, I would like to select the 'client region' into a DC somewhere to prevent children drawing outside the region. But so far I have not had any success. I created the 'border region' hoping to validate it before child controls are painted, but it didn't work.
|
|
|
|
|
Ok another couple ideas (probably as stupid as my other ones)
ExcludeUpdateRgn() specifying the border-only region.
In the parent window's WM_PAINT handler (or WM_NCPAINT?) call ValidateRgn() specifying the border-
only region.
EDIT: You tried that already
|
|
|
|
|
I saw this function on MSDN but I cannot figure out how it's supposed to be used. It accepts a HDC and a HWND, where does the HRGN come into play?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
