Re: messabebox(...) v afxmessanebox
- From: "Tom Serface" <tom.nospam@xxxxxxxxxxxxx>
- Date: Thu, 28 Feb 2008 17:22:24 -0800
Yeah, I know that. I was just wondering why you would store MFC resources in vectors when the resource file concept is so handy. Maybe you only have "strings" to deal with and not dialogs, icons, bitmaps, toolbars, menus, and strings. In that case doing it externally may be easier, but ...
Of course, the nice thing about programming is we can all do it "our way" and it still works if our way works.
Tom
"Roger Rabbit" <roger@xxxxxxxxxx> wrote in message news:OfBjM9meIHA.3724@xxxxxxxxxxxxxxxxxxxxxxx
Vectors are a Standard Template way of dealing with strings. There are so many ways to manage strings.
"Tom Serface" <tom.nospam@xxxxxxxxxxxxx> wrote in message news:6F65A111-BA66-46AE-BB5B-1B12EF520941@xxxxxxxxxxxxxxxxvectors to store resources? Why not just use the resource string tables? Now I'm curious :o)
Tom
"Roger Rabbit" <roger@xxxxxxxxxx> wrote in message news:uT9sWpmeIHA.5296@xxxxxxxxxxxxxxxxxxxxxxxI was contemplating a slightly different approach using vectors.
"Tom Serface" <tom.nospam@xxxxxxxxxxxxx> wrote in message news:AC61D2D6-2D60-4975-B937-452CBA667E9E@xxxxxxxxxxxxxxxxDoing multiple languages is almost always where professional applications end up so it's good to plan on it ahead of time. If you use MFC you may find a function like this to be useful:
CString GRS(int uID)
{
CString cs;
cs.LoadString(uID);
return cs;
}
This is not so useful in AfxMessageBox since you can pass in an ID directly, but for other thing where you want to get a string from the resource table like:
CString myString = GRS(IDS_STRING_I_WANT);
Would get the one for the correct language.
I also strongly recommend using FormatMessage() in your strings so you can change variable arguments positions based on language.
Tom
"Roger Rabbit" <roger@xxxxxxxxxx> wrote in message news:659D6338-56AF-4899-9828-1447CA4688EA@xxxxxxxxxxxxxxxxThank you everyone for the ideas, from the other work I have done, it now makes afxmessagebox the obvious choice my programming is multithreaded and I do like the idea of being able to use tables of messages so I have the potential to easily add Multilanguage capabilities.
"Alexander Grigoriev" <alegr@xxxxxxxxxxxxx> wrote in message news:OrePEJbeIHA.148@xxxxxxxxxxxxxxxxxxxxxxxMessageBox(NULL,...) unfortunately doesn't disable your main frame, which may lead to nasty recursion.
"AliR (VC++ MVP)" <AliR@xxxxxxxxxxxxx> wrote in message news:YEjxj.9716$5K1.303@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxJust to note something obvious. AfxMessageBox does not require a window handle, which is a cleaner than having to type
::MessageBox(NULL,.....); when you want to display a message box from code that is not a window, like a thread.
AliR.
"Roger Rabbit" <roger@xxxxxxxxxx> wrote in message news:4D883F27-FC5A-4BF1-90F7-81F79474C6BA@xxxxxxxxxxxxxxxxany material difference between messagebox and afxmessagebox to display a message for development testing?
.
- References:
- messabebox(...) v afxmessanebox
- From: Roger Rabbit
- Re: messabebox(...) v afxmessanebox
- From: AliR \(VC++ MVP\)
- Re: messabebox(...) v afxmessanebox
- From: Alexander Grigoriev
- Re: messabebox(...) v afxmessanebox
- From: Tom Serface
- Re: messabebox(...) v afxmessanebox
- From: Roger Rabbit
- Re: messabebox(...) v afxmessanebox
- From: Tom Serface
- Re: messabebox(...) v afxmessanebox
- From: Roger Rabbit
- messabebox(...) v afxmessanebox
- Prev by Date: Re: messabebox(...) v afxmessanebox
- Next by Date: Re: C++ VS 2005 Application works in Debug, not in Release Mode
- Previous by thread: Re: messabebox(...) v afxmessanebox
- Next by thread: Re: messabebox(...) v afxmessanebox
- Index(es):
Relevant Pages
|
