|
I am a rookie in the MFC game , and am having some awful problems in creating a Popup window. From the parent windows OnCreate i try to create the popupwindow with createEx(...). Have tried all combinations (also excluding WS_CHILD) but nothing seems to work. I receive an assert error upon launch. If I keep the window simple (WS_CHILD), no problemo. I cannot seem to find any documentation on the subject. Can anyone HELP ME.
Thanks
|
|
|
|
|
Can you say what is your assertion failor? which source file and line?
A. Riazi
|
|
|
|
|
we need to migrate a huge project overseas - or to other OS.
the project works fine on pure english OS, but crashes on other OS which use different languages, i.e. Italian and Chinese windows.
we don't need to modify the project at all because people there know english - but it crashes there.
it is too hard to find why in the moment.
any experience, hint or comment to fix the problem is useful, thx in advance.
includeh10
|
|
|
|
|
Well, is it just not starting, or do you need to do something special, like entering a special character etc?
All of my programs, developed with english OS wrk great on german windows. they even tolerate the umlauts.
My opinions may have changed, but not the fact that I am right.
|
|
|
|
|
Is your project use OS resources (any strings, bitmaps, icons, ...)?
A. Riazi
|
|
|
|
|
yes, many.
bitmap, menu (which uses string), icon ...
is this possible reason?
includeh10
|
|
|
|
|
If program wants to load string (or any other resources) from resource but not found it, program will be crashed.
A. Riazi
|
|
|
|
|
If I were to press the "Print Screen" key on my keyboard, and capture whatever screen image my monitor might be showing, does window assign a filename to that screen image for later use?
Normally, that image would go to the clipboard from which you can 'Paste' it on to another screen to get the image. However, not all applications have the 'Paste' icon available (or the means for it to be used).
What I need to do, is capture a screen image, compress it, and send it as an attachment in an email message.
Thanks for any help. I appreciate it.
William
|
|
|
|
|
*print screen*
-->Open MS Paint
*paste*
*crop* (if necessary) [aside] You can use alt + print screen to capture the current window. [/aside]
File-->save as:
Select jpg format if you don't have a compression utility like win zip. Or you can choose bmp and zip it afterwards.
*attach file to e-mail*
*send*
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
Also you can press Alt+Print Screen to capture "Active Window".
use paint to paste bitmap!
A. Riazi
|
|
|
|
|
A. Riazi wrote:
Also you can press Alt+Print Screen to capture "Active Window".
He said that! 
Rickard Andersson@Suza Computing
C# and C++ programmer from SWEDEN!
UIN: 50302279
E-Mail: nikado@pc.nu
Speciality: I love C#, ASP.NET and C++!
|
|
|
|
|
Here's my suggestion: read the data directly from the clipboard. The format of the data in the clipboard is Device Independant Bitmap (CF_DIB).
There's a MFC sample that retrieve a DIB from the clipboard. Search for DIBLOOK in MSDN.
Once you have the DIB you can save it in an other format. We used Stringray SECJpeg class a few years ago but you can surely find great code for that on the net (if not on this site...).
Good luck.
|
|
|
|
|
I have a class derived from CListCtrl, and I want it send a customized message to its parent window(which is derived from CDialog) when in need. So I defined a message ID, say, "#define WM_SOMETHING WM_APP + 100" in my project and handle this message by the following way:
void CMyListCtrl::OnSomething
{
CWnd* pParent = GetParent();
if (pParent != NULL)
pParent->PostMessage(WM_SOMETHING, 0, 0);
}
afx_msg void OnSomethingHappened();
BEGIN_MESSAGE_MAP(CMyDlg, CDialog)
ON_MESSAGE(WM_SOMETHING, OnSomethingHappened)
END_MESSAGE_MAP()
void CMyDlg::OnSomethingHappened()
{
}
Now, in debug mode it works great, but in release mode it crashes. If I remove the "PostMessage..." code from implementation of CMyListCtrl, it will not crash so the problem must be there... What am I doing wrong? Thank you.
|
|
|
|
|
Your message handler function has to have the form
LRESULT CMyWnd::OnMyMessage(WPARAM WParam, LPARAM LParam)<br />
{<br />
return (LRESULT)0;<br />
}
If your app crashes in release mode the cause should be your wrong function declaration.
|
|
|
|
|
|
As a note, take a look at RegisterWindowMessage() as any WM_SOMETHING message defined using
#define WM_SOMETHING WM_USER + x
can be problematic as the message number may be in use my one of the new common controls. WHich can give possible unpredictable behaviour to your app at a later time (especially when their implementation changes)
Roger Allen
Sonork 100.10016
WHats brown and sticky?
A stick or some smelly stuff!
|
|
|
|
|
I think it doesn't matter as long as your messages are only to be used in your application, not system-wide. As MSDN says:
WM_APP through 0xBFFF: Messages available for use by applications.
Beside that fact I think in our case RegisterWindowMessage() has not been used, as in that case we'd to take on_registered_message instead of on_message.
|
|
|
|
|
did you try ::SendMessage?
A. Riazi
|
|
|
|
|
How can I get the text to a CString from a list box
with out select anything?
\Larsson
|
|
|
|
|
I think CListBox::GetText should work.
|
|
|
|
|
Well Sorry!,
I don't get the text from the Listbox.
And if i do how can a get al that is listed in the listbox?
|
|
|
|
|
Here's an example how to get all items' text:
CListBox lb;
...
CString str;
int n;
for ( int i = 0; i < lb.GetCount(); i++ )
{
n = lb.GetTextLen( i );
lb.GetText( i, str.GetBuffer(n) );
str.ReleaseBuffer();
}
or
CListBox lb;
...
CString str;
for ( int i = 0; i < lb.GetCount(); i++ )
{
lb.GetText( i, str );
}
should work, too. In both cases str holds the current item's text.
|
|
|
|
|
Thank's you are a star.
\Larsson
|
|
|
|
|
Hi,
in the past, when our application were pure C based, we had our own malloc and free routines. These were called by simply re-#defining malloc and free as C-macro's and 'route' them to our own PrivateMalloc and PrivateFree routines.
Now, in C++, we want of course to reuse our memory manager (which has some peculiar advantages for us), however, we see some problems:
- In our old software, the memory pools were initialized when the application started up (as first action). Now, in C++, new can already be executed before the main is actually called (e.g. in the constructor of a global variable). However, we think we can solve this by performing the initialisation of the memory pools in the first call to 'new'.
- In our old software, leaked memory was reported at the end. Since global variables' destructors are executed after the application has finished, we cannot report memory leaks at the end of the application, since the list will always contain memory that still needs to be deleted by the global variables' destructors.
- MFC seems to have their own new and delete implementation. We aren't sure that MFC doesn't rely on some specific part of their implementation. Can we simply ignore the MFC new/delete and use our own implementation?
I don't know how other memory managers solve that problem.
Maybe anyone of you have already written their own new/delete implementation; then, how have you done that? And did you encounter any problems with MFC?
Thanks in advance.
Patje.
Enjoy life, this is not a rehearsal !!!
My Articles:
- Implementing a Subject/Observer pattern with templates
|
|
|
|
|
1. The approach you are suggesting is just right.
2. Use atexit.
3. In release mode, MFC uses the same new as everybody. In debug mode, new is a macro that resolves to an overload of new specifying the file and the line where the call occurs. Don't know how this can be ridden of.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
