|
How to get a CWnd(CView) background color in a MDI application.
|
|
|
|
|
How to get a CWnd(CView) background color in a MDI application.
|
|
|
|
|
Its the second time i got this message from ms visual studio 6.0 :
"Debug Assertion Failed !
Program : prgram.exe
File : dlgdata.cpp (?)
Line : 43
For info on debug [...] see ms vsc doc...
Press retry to debug the application"
It just seems to come out of nowhere since my program doesnt pose any problem during the compilation.
Can anyone help me please, i'm stuck ! !
thanks.
|
|
|
|
|
assertions are a good thing!
They are placed in code by the programmer to verify that something is true, and if it isn't true, force (when DEBUG is defined) the display of a nasty message like the one you describe.
You are getting this assertion from an MFC app (via the ASSERT() macro) but the standard library assert() is available as well for non MFC apps.
MFC code uses ASSERTs liberally - as it should. Very often you'll see code that does something like ASSERT(pointer != NULL). If the expression is true, the code continues - but if not (i.e. a NULL pointer) the code will 'assert'. The idea is that its better to see the fault here than to track a subsequent access violation (which may end up in a system DLL).
Note that you have to be careful not to put code with side effects inside an ASSERT - because it won't be compiled for a release build - MFC provides the VERIFY macro if you want to do the equivalent of an assert in a release build.
Philosophies vary on what constitutes a valid place for an assertion. Some say they should be reserved for critical things like NULL pointers that will generally cause a crash. I tend to use them for even minor things that may not be critical but I want to know about them - things that I might miss if I just TRACE a notification to the debug output window.
The ASSERT you are getting comes from CDataExchange - probably some problem with a dialog control ID. What you can do is choose Retry to invoke the debugger, then press Alt+7 to display the call stack. (Or View | Debug Windows | etc.) By looking at the ASSERT statement and the surrounding code, you should be able to identify some offending variable or resource define. You'll often need the call stack to backtrack to the source of the problem, but unless its some nasty mess in your resouce file you should be able to figure it out.
|
|
|
|
|
Thanx a lot !
You've been a great help, thanks to the call stack i noticed some references to edit box ID's which were useless since i had deleted the corresponding edit boxes...
Thank you again !!
|
|
|
|
|
Excellent summary Tim, you should submit it as an article.
As you and I both know  , new MFC programmers (and many long standing ones), don't really understand the value and function of ASSERT()'s, and quite often after they start using them, place code in them not realizing the code is only included in a Debug build.
I also agree that they should be used liberally, as they have zero effect on the performance of runtime code.
|
|
|
|
|
I'm new to MFC, and I have a little problem.
Is there a way to have a dialog bar on the top of a CView in an MDI app?
I have the following code, but the dialog bar doesn't get drawn!
It works great if I create the dialog bar on the MainFrm.
int MyView::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
m_pDlgBar = new CDialogBar();
if (!m_pDlgBar)
return -1;
m_pDlgBar->Create(
this,
IDD_DLGBAR,
WS_CHILD | CBRS_TOP | CBRS_TOOLTIPS | CBRS_FLYBY,
ID_DIALOGBAR); // I don't really know what this parameter does
m_pDlgBar->ShowWindow(SW_SHOWNORMAL);
if (CView::OnCreate(lpCreateStruct) == -1)
return -1;
}
Any suggestions?
Thanks In Advance.
Erik
|
|
|
|
|
You want to add the toolbar (or dialog bar) to the frame insted of the view. You can catch the button messages in the doc, view, or frame. The code below will add a toolbar to the child frame:
int CFrameClass::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
if (CMDIChildWnd::OnCreate(lpCreateStruct) == -1)
return -1;
//Create the toolbar.
{
EnableDocking(CBRS_ALIGN_ANY);
if(!m_wndToolBar.Create(this, WS_CHILD | WS_VISIBLE | CBRS_TOP, IDR_TOOLBAR_DEFECTVIEW) ||
!m_wndToolBar.LoadToolBar(IDR_TOOLBAR_DEFECTVIEW))
{
TRACE0("Failed to create toolbar\n");
}
else
{
// TODO: Remove this if you don't want tool tips or a resizeable toolbar
m_wndToolBar.SetBarStyle(m_wndToolBar.GetBarStyle() |
CBRS_TOOLTIPS | CBRS_FLYBY | CBRS_SIZE_DYNAMIC);
// TODO: Delete these lines if you don't want the toolbar to
// be dockable
m_wndToolBar.EnableDocking(CBRS_ALIGN_ANY);
DockControlBar(&m_wndToolBar, AFX_IDW_DOCKBAR_RIGHT);
}
return 0;
}
Good luck,
Jonathan Craig
|
|
|
|
|
Thanks!
It worked, but how can I get a pointer to the child from the view?
Thanks again!
Erik
|
|
|
|
|
Look up this document in the MSDN or on Microsoft's web site; "Relationships Among MFC Objects". I keep this one tacked to the wall next to my computer.
The function you want is CWnd::GetParentFrame(). Remember the view is a child of the frame.
Good luck and happy hacking...
Jonathan Craig
|
|
|
|
|
This is very strange problem because my code works perfectly when dynamically linking to MFC.
At some point in my project I use:
HCURSOR hAniCur = (HCURSOR)LoadImage(AfxGetResourceHandle(),
MAKEINTRESOURCE(IDR_HOURGLASS), IMAGE_CURSOR, 0, 0, LR_DEFAULTCOLOR);which gives me a valid handle as long as MFC is in a DLL, but returns NULL when I link static MFC libraries.
There are no differences between Debug or Release builds, both suffer the same problem. I also tried to change the resource ID of the animated cursor and to use a string instead of a number, but without success.
I have reproduced this problem on a little test project if anyone likes the challenge...
Thanks in advance,
Paolo
|
|
|
|
|
Step through AfxGetResourceHandle() and make sure it's returning the correct HINSTANCE. I've seen that function return unexpected results before, which then causes all sorts of resource headaches.
|
|
|
|
|
I tried with AfxGetInstanceHandle(), AfxGetResourceHandle() and GetModuleHandle(NULL). They all return the same value, that is 0x00400000, which is right.
What's more, loading from a file works just fine with the arguments I pass to the function.
It seems like LoadImage can't find the resource, but why?
When I link with static libraries I add some resources to my executable, so I thought something was in conflict with the animated cursor resource. I tried with different IDs, but without any luck.
I imported the animated cursor as a custom resource, naming that type "ANICURSOR". Is this right? Or I should use something else?
I think the correct resource type is RT_ANICURSOR, but how can I add such resources to my project?
However, loading the animated cursor with the type I specified works in Debug version.
Any other ideas?
|
|
|
|
|
Convert the image to one of the closest DIB format, and then use StretchDIBits to display it.
My guess is that each pixel is a 16-bit grayscale level, so the closest DIB format would be 8-bit grayscale image, or a 256-color DIB with a grayscale color table.
Setup a BITMAPINFO structure with a 256-color grayscale color table, convert the image array to a 64x64 BYTE array, and then use StretchDIBits to display it.
|
|
|
|
|
I discovered what was wrong: if there are static cursor resources (RT_CURSOR) both LoadImage() and LoadCursor() don't look for animated cursor resources (RT_ANICURSOR = 21).
Statically linking to MFC involves the inclusion of some MFC resources, among which there are two cursors for context-sensitive help.
I've tried adding the animated cursor as a static cursor, but both VC++ IDE and the resource compiler recognize the internal file format.
So what should I do, if I don't want to load the cursor from file?
Is this a BUG ?? (tested on Win95 and Win2000)
Any suggestion would be appreciated... 
|
|
|
|
|
To solve the problem, I thought to load the animated cursor resource and then create the cursor handle with the following code:HRSRC hResInfo = FindResource(NULL, MAKEINTRESOURCE(IDR_HOURGLASS), RT_ANICURSOR);
DWORD dwResSize = SizeofResource(NULL, hResInfo);
HGLOBAL hRes = LoadResource(NULL, hResInfo);
PBYTE pResData = (PBYTE)LockResource(hRes);
HCURSOR hAniCur = CreateIconFromResourceEx(pResData, dwResSize,
FALSE, 0x00030000, 32, 32, LR_DEFAULTCOLOR);
The problem remains
All the instruction are successful with both types of linkage, but the last returns a valid handle only when dynamically linking to MFC. When I specify to use static MFC libraries, CreateIconFromResourceEx() cease to work and returns NULL.
Can anyone tell me why?
I tried to debug USER32 code, but it's a suicide without debug symbols.
Where can I get debug symbols for Windows 2000?
Please help!!
|
|
|
|
|
i'm working on a program that reads an open file and puts a line into a sting buffer until a newline is found, then puts the string into the clipboard. This is done through a windows WH_KEYBOARD hook... is there anyway for the read file's handle to be shared so that all processes can share the same instance of the handle?
Any non-MFC solution would be very much appreciated.
|
|
|
|
|
Can I create a MDI form with child forms WITHOUT USING MFC? If it's possible, could you show me some code to do it?
Thanks a lot in advance!
B
|
|
|
|
|
If you really want to do it without any wraper classes (i.e. MFC), get a few books like, "Windows 2000 Programming from the Ground Up" by Herbert Schildt. Herbert likes to hand crank all his stuff and will have examples on how to handle the messaging and window creation.
If you just want less complicated CWnd objects you can create a MDI application without the Document/View Architecture. This gives you the CView without the attached CDocument.
Unless you want to be able to use different compliers to compile your code, I would use window wraper classes for my development. They do make life easier.
Good Luck,
Jonathan Craig
|
|
|
|
|
Have you looked in the SDK samples? I would be quite surprised if there are not any samples there. Also I think that the Platform SDK documentation that describes MDI programs would at least have peices of a sample.
|
|
|
|
|
YES, you can. It's called WTL (Windows Template Library). It's on the Platform SDK, and it's great. You can create full-featured apps without MFC bloat and no dependencies.
|
|
|
|
|
I tried the WideCharToMultiByte function but it seems that I have no success.
I'm trying to write an XML file.
|
|
|
|
|
Uwe, here's a UTF for Linux FAQ that talks about decoding UTF-8. It should give you a start regarding going the other way.
Here's a Google search that will give you some more stuff to look at.
|
|
|
|
|
Thank you very much, Mike!
I'll post a solution as soon as I figured it out. Maybe it will help others.
|
|
|
|
|
After mailing with Markus Kuhn, the author of www.cl.cam.ac.uk/~mgk25/, he told me the following solution (function 1), which I wrapped a little bit (function 2):
static int Latin1toUTF8(TCHAR *t, const TCHAR *s, int len)
{
const TCHAR *p = s;
TCHAR *q = t;
while (p < s + len) {
if ((*p & 0x80) == 0) {
*q++ = *p++;
} else {
*q++ = 0xC0 | ((*p >> 6) & 0x3);
*q++ = 0x80 | (*p & 0x3F);
p++;
}
}
return q - t;
}
void StringToUTF8( const CString& input, CByteArray& output )
{
output.RemoveAll();
if ( input.IsEmpty() )
return;
output.SetSize(input.GetLength()*6);
const int new_length = Latin1toUTF8( (TCHAR*)output.GetData(), input, input.GetLength() );
ASSERT(new_length<=output.GetLength());
output.SetSize(new_length);
}
Thanks to Markus!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
