|
ID_FILE_CLOSE and other standard MFC menu commands etc are defined inside the MFC headers. These shouldn't be changes otherwise you stop the MFC from working so that why thier not in your resource.h.
When adding your own ID's manually (unlike what Shog9 said), if you were to use the next available ID specified by
#define _APS_NEXT_RESOURCE_VALUE 131
You would have to increment this #define in the file so that the next autmatically added one would not clash with the one you just added manually.
#define ID_FILE_MYCOMMAND 131
#define _APS_NEXT_RESOURCE_VALUE 132
Roger Allen
Sonork 100.10016
If I had a quote, it would be a very good one.
|
|
|
|
|
My thanks to both of you. I appreciate your input tremendously,
ns
|
|
|
|
|
Hi
Is there anyway that i can make my application have the looks of Outlook?? If yes, then where will i get that class?
Thanks alot!!!
|
|
|
|
|
how about searching this site for articles that have "outlook" in the title?
--
Help me! I'm turning into a grapefruit!
|
|
|
|
|
sorry, i should've done this before!!! 
Thanks for the advise 
|
|
|
|
|
I checked all the doc/view classses but didnt find a handler for the pre-existing VC ID_FILE_OPEN menu item. Which class handles the COMMAND for this ID? If it were the view class, and I wanted to remotely trigger this menu, could I say:
AFxGetMAinWnd()->SendMessage(WM_COMMAND, ID_FILE_OPEN)?
Does it matter who is handling this command? CAn this work even if any class were to be handling it?
Thanks,
ns
|
|
|
|
|
CWinApp does, or your CWinApp derived class does.
You should find these entries in your CWinApp derived class's message map
// Standard file based document commands
ON_COMMAND(ID_FILE_NEW, CWinApp::OnFileNew)
ON_COMMAND(ID_FILE_OPEN, CWinApp::OnFileOpen)
Roger Allen
Sonork 100.10016
If I had a quote, it would be a very good one.
|
|
|
|
|
Thank you. So why do we send a message to the AfxGetMainWnd() object rather than AfxGetApp()? THe former works. Havent tried the latter.
One odd thing I found is that if my menu item is handled locally by the class thats sending the message, I dont have to Afx -> sendmessage it, just a direct sendmessage (since its to this->). So looks like the message has to be sent to the class that handles the command. In retrospect thats obvious....
So why AfxGetMainWnd (which returns the mainframe right? )and not AfxGetApp who is handling the ID?
Thanks,
ns
|
|
|
|
|
I got the error:
C:\swanke\A20\WzdView.cpp(124) : error C2039: 'SendMessageA' : is not a member of 'CWinApp'
So I suppose we have no choice but to send it to MAinWnd......I wonder why we cant send messages to the app???
|
|
|
|
|
The CWinApp object itself is not a window and cannot "receive the message" itself. What happens I think is that the CMAinFrame command router pass's it through a message map belonging to the app/mainframe/doc/view (these may not be in the right order here) in order looking for the first one that handles the call.
So AfxGetMainWnd()->SendMessage() will get to the app object due to the internal MFC routing mechanism.
Roger Allen
Sonork 100.10016
If I had a quote, it would be a very good one.
|
|
|
|
|
MAny thanks. I need to read more about the message passing mechanism. SO I'm gathering that AfxGetMAinWnd is giving us back an object even hif=gher than the app object (which I thought was the highest) . The name makes it sound like its going to give back a CMAINFRAME * object, which I thought was aminframe object. Anywaqys sorry if this sounds confused...I'll do some reading. APpreciate your help!
ns
|
|
|
|
|
Both CWnds and CWinApps are CCmdTargets and are therefore capable of providing handlers for commands. Note that true window messages (WM_mumble) can only be sent/posted to CWnds. The command routing mechanism of the doc/view architecture works like this:
- The
CView object gets first dibs at handling the message.
- If it doesn't handle it, the enclosing frame window gets a chance.
- If it doesn't handle it, the
CDocument attached to the view gets a chance.
- If it doesn't handle it, the
CWinApp object gets the message.
Many standard commands are "automagically" handled because CWinApp provides handlers for them. Examples are File|Open,Save, Exit, Help, etc.
/ravi
Let's put "civil" back into "civilization"
http://www.ravib.com
ravib@ravib.com
|
|
|
|
|
Actually, the order is like this:
1. The active view gets the first shot at processing the message
2. Then the document associated with the view gets it's chance
3. The document template is next.
4. The mainframe get's its chance now.
5. Finally, the application object gets it's chance.
6. If noone handled this message it goes to ::DefWndProc( );
This applies to WM_COMMAND and WM_NOTIFY messages.
|
|
|
|
|
Ooops - you're right! Thanks!
/ravi
Let's put "civil" back into "civilization"
http://www.ravib.com
ravib@ravib.com
|
|
|
|
|
Hello,
I need to implement database access in my application. MS SQL server will be used. What are your reccomanadtions about technology to use: ODBC, OLEDB, ADO?? What something else MS Platform provide?
I thinked about ADO, but frankly I preffer to avoid the COM stuff in my app.
But, I think OLEDB is also a COM thing, is it true?
And if I shall use ODBC, I should need a long development time?
Please send me your advice.
Thanks,
MN
|
|
|
|
|
Ok Don,
Since your looking for answers. Can you handle the truth?
I finally decided to go with ADO for a recent project. I'm pretty new to database stuff in C++ and wanted to go with one of the technologies that should be around for at least another month or two. Our company already had an out of date ODBC library that I hated and DAO is simply going the way of the birds. One big reason for going with ADO was Carlos Antollini's fine ADO libraries or articles on this site. It is a great starting place and the class structures work well with my application. ADO just seemed like the right strategy for my work. Take a look at Carlo's articles and see if it is right for your project.
|
|
|
|
|
Robert Vista wrote:
Take a look at Carlo's articles and see if it is right for your project.
Thanks Robert, I forgoten to mention that large amount of free tutorials
could also be a factor in decision.
Robert Vista wrote:
out of date ODBC library
what do you mean? I thinked at backward compatibility, and so on, I think
ODBC will be supported long time from now by Windows, and will evolve also...
And another thing: which of the layer support transactions better??
Thanks.
|
|
|
|
|
I have a simple yes or no question: is the Calendar Control broken(hence all the wrapper controls)
And what I mean by that is that you cannot control the fact that it changes months when the grayed out numbers are clicked
More importantly when you select multiple days that painting is horrible.
Is there any 'know' bugs?
|
|
|
|
|
My application (Win32, no MFC) has the following window structure:
dlgA (main window, CreateDialog)
dlgB (data area, CreateDialog, owned by dlgA)
wndC (input window, CreateWindow, owned by dlgB)
wndD (another input window, CreateWindow, owned by wndC)
Now here's what happens:
I close wndD and the focus switches back to wndC (as expected)
I close wndC and the focus switches to the desktop (unexpected)
If I give wndD the WS_CHILD style dlgB gets the focus after closing wndC, but I want it to have the WS_POPUP style instead, because it is a popup generated by wndC should be drawn outside of its client area (as it can be considerably larger than wndC).
If I close wndC without ever opening wndD (which is created only when I click a certain button in wndC), it also works correctly.
Any idea what this can be? It's driving me crazy.
|
|
|
|
|
Hello,
I looked for sample code on the web and msdn to see how to use this to make buttons show up dynamically. I'm not sure how to use this function. CAn someone give me a sample of how to use this?
I tried:
void CMainFrame::OnAddbutton()
{
TBBUTTON tbButton[2];
tbButton[1].fsStyle = TBSTYLE_BUTTON;
m_wndToolBar.GetToolBarCtrl().AddButtons(2,tbButton);
}
but I'm sure I'm missing something.
Thanks you,
ns
|
|
|
|
|
Try this:
CToolBarCtrl* pBar = &(m_wndToolBar.GetToolBarCtrl());
tbbuttonStruct.iBitmap = pBar->AddBitmap(1, pBitmapNew);
/* pBitmapNew is a pointer on a dynamically allocated CBitmap,
containing the button image, it should be freed at the end of the program */
tbbuttonStruct.idCommand = ID_MY_COMMAND;
/* user define */
tbbuttonStruct.dwData = 0 /*Image Index*/;
tbbuttonStruct.fsState = TBSTATE_ENABLED;
pBar->AddButtons(1, &tbbuttonStruct);
HTH,
K.
We do not inherit the Earth from our ancestors. We borrow it from our children.
Antoine de Saint Exupéry (1900-1944)
|
|
|
|
|
I want to display the thumbnails of images in some folder, using VC++. I tried using the IExtractImage interface, provided by the shell (supposedly!)
I get a compile-time error about the interface not being found. I use Windows2000, so I believe it's not a problem with the shell version. I could not find IExtractImage in shlobj.h.
Is there any way for getting the thumbnails?
Thanks.
Logic is a systematic method of coming to the wrong conclusion with
confidence.
|
|
|
|
|
Please click and go the following link for your reference. Good luck!
http://netez.com/2xExplorer/shellFAQ/bas_infos.html
Golden Lee
|
|
|
|
|
It's this site which I have been referring to. I tried out the sample code given therein, and am getting the compile-time error about IExtractImage interface.
http://netez.com/2xExplorer/shellFAQ/bas_infos.html
-Karthika
Logic is a systematic method of coming to the wrong conclusion with
confidence.
|
|
|
|
|
If I remember well, you should install first the Core SDK to use IExtractImage interface.
HTH,
K.
We do not inherit the Earth from our ancestors. We borrow it from our children.
Antoine de Saint Exupéry (1900-1944)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
