While Im using subForms in my Options Dialog, i want to read out the Controls Data, like text out of a CEdit Ctrl. Normally i would do this with DDX and Classwizard -> with result I have a variable which i can use. But with the use of subForms I have no scope anymore to these subForm Dialog Elements.
I have tried something like this what you have wrote.
Problem of your Code above is that the compiler will generate an error
cause of CDialog has no member m_myEditCtrl. Now i had the Idea to deriver the CDialog Class with my Dialog Class e.g. mySubFormDlgClass. The Code look something like this
with this Construction there is no error but an Assert @ runtime! So this is not the way. Another Problem is that if i insert some AFX Messages with Classwizard into my mySubFormDlgClass,set breakpoints in this Event Functions and want to debug - there is no interruption. The Event does not occur.
So only a ShowWindow takes places, no DoModal() function. Maybe there is the Problem. If i do a DoModal the Dialog opens but must be closed if i want to use my MainDialog while the other is open. I will research some time on this. Maybe you have some ideas.
triggerdie wrote: cause of CDialog has no member m_myEditCtrl
... Of course your CDialog has no m_myEditCtrl variable !!! I cannot guess your variable names !! This was only an exemple. Sorry for the misunderstanding. I think the articla was just a basis, you have to work on it to get your data retrieved. The easiest way to do this is the one I gave you. So, let's take it again. Change this in the code of SubFormCollection.h :
CArray<CDialog*, CDialog*> m_Forms; // array with all forms
CArray<CDialog*, CDialog*> m_Forms; // array with all formsprotected:
This will enable you to get at the m_Forms table by setting m_Forms as public.
Now you should have a main dialog, let's say CMainDlg, a CSubFormCollection, and some child dialogs, let's say CChildDlg1 and CChildDlg2 with respectively ressource IDD_SUBFORM1 and IDD_SUBFORM2 (Go in the properties of your dialogs in the ressource editor to set that). Replace these names by your variable names if they are different !!.
First, follow all the steps given in the article, especially step 5 :
(this in the MainDlg.h file.
and step 6
(GetDlgItem(IDC_SUBFORM_FRAME))->GetWindowRect(&r); // get the position for the subforms// m_SubForms.SetRelPos(r); // if the positioning is absolute use this, else the next line
m_SubForms.SetCenterPos(r); // centers the subdialog within the static IDC_SUBFORM_FRAME
m_SubForms.CreateSubForm(IDD_SUBFORM1,this); // create the sub forms
(this in the CMainDlg::OnInitDlg() file.)
Now you have two subForms, with index 0 and 1.
Then, as an example, place an edit box on the ressource of CChildDialog1, open the class wizard, add a member variable m_myEditCtrl of type CEdit.Close the class wizard.
in your code (in CMainDlg::OnInitDlg() for instance), to show the first subForm.
You can now retrieve the text entered in the edit box by the user with :
OK. So i made a project and tested the article code, and found out it is totally crap. it is unfinished, sometimes even wrong (under NT, my subFroms were not getting docked in the main dialog) and the Table pointer is not reliable. Drop it !
As for your code sample, it was because you have cast the pointer on a CDialog, and not on your CDialog name (dlgOpt_ServerPort).
on the close routine of the options dialog. you send the text you wand to you parent and save it there.
(i dont take a look on the childdlg.asp) if you use a normal dlg. with DoModal. then create your dialog on the stack not on the heap. mydialog* blub = new mydialog; blub->DoModal(); CString myvar = blub->mycstringvar; delete blub;
I don't know what you mean with SubForm, but if the subform is a dialog placed as a control inside a parent dialog, you can use member functions in the child dialog always...
I mean that is better to use member functions to get the values than getting the values directly by calling SubForm.m_CstringInEditCtrl if you use member functions (GETxxx and SETxxx in order to obtain and modify values) you'll always will be able to readapt the returned value or format the sent value as is desired...
then I would do:
1. from the parent dialog/window/... you'll always have access to the childs.
2. Using the previous premise, you'll be able to call members/methods/functions from the class of the child dialog.
3. I would call methods/functions of the subform in order to get/set the desired values and in order to make it safely.
Hope this helps.
Get and set are only prefixes that I use in order to use the hungarian notation and know what the function do before reading its content.
Thanx for your fast reply. Is it possible do change dynamicly from the parentsDialog to the ChildDialog without to destroy the ChildDialog.
I want to change the HIDE and SHOW behaviour of several Child Dialogs.
How can I do this? Without using of DoModal() only with ShowWindow().
Cause if i do a DoModal() i can not make any interaction with my parentDialog while the ChildDialog is open. Wihtout a DoModal and just ShowWindow it does not work. Assert @ runtime. So i dont know how to solve this Problem. I want to use the Std Afx Message Functions of each Child Dialog. Maybe you have an advice.
First _int64 is Microsofht specific.
Second _int64 represents a 64-bit interger.
If you do a search on MSDN, for _int64, you will find at lease 31 seperate entries. If you search for "microsoft _int64" on google you will find over 200 entries, many of which appear to do with porting. I know of no other sources of information on _int64.
ColumnVi->cx = 35;
Title = "Nr.";
ColumnVi->pszText = Title.GetBuffer(3); m_PersCtrl.InsertColumn(0,ColumnVi);
//Insert the column into the clistctrl
The width of column i've set to 35, i tested it out and changed the value until it looked good. but the caption can change at some time .. so how can i know how much pixels 1 char. takes or anyone have other ideas to make it more dynamic?
I have a client reporting that some of my code crashes on a few of his machines; I can't reproduce the problem on my end (what else is new) and all I have to work with is the crash address he's reporting.
I've had a look at Wouter Dhondt's excellent article on .MAP files[^]...and if I'm following the steps properly, the crash occurs in a memcpy() call...great, according to a search in my project's .cpp files, I'm calling it explicitely 74 times. Since I can't reproduce the crash there's hardly any point in stepping through all of them. Besides, if I understand correctly, the call to memcpy() might not necessarily be any of my own (ie, another C runtime library function might be doing it; who knows which one it is).
Taking it to the next step, I tried to determine what file/line the crash occurs in according to the .MAP file. Again based on the article, subtracting the load address (0x00400000) and the 0x1000 bytes PE header from the crash address (0x00459083), I end up with 0x00058xxx, which is nowhere near any of the addresses listed in the bottom part of the .MAP file. And since I'm within 0x004xxxxx, I'm pretty confident the crash doesn't occur in a DLL. I *know* I'm using the proper .MAP file as I've rebuilt the project (this time set to generate the .MAP file) and sent the client the recompiled EXE (which turned out to be identical to the previous one anyway).
I've tried to get the client to send me Dr. Watson logs and crash dumps, but none seem to ever get generated despite the options being selected (he's on Win2K SP2).
What next? I don't like the idea of sending a client an EXE with MsgBox() calls...
Run your release version in debug and and the break the program. Use the debugger to see if you have anything at the address in question. If your release program doesn't have any debug information, it would help to enable the program database debug information.
I'm going to patent thought. I have yet to see any prior art.
Yeah, the one entitled "rva+base". Given my crash address (0x00459113), here's what I have:
0001:00058080 __mbsrchr 00459080 f LIBC:mbsrchr.obj
0001:000580e0 _memcpy 004590e0 f LIBC:memcpy.obj
0001:00058415 __onexit 00459415 f LIBC:onexit.obj
...so the crash seems to occur in memcpy().
I understand the mapping back to the file/line number in Wouter's article...however in my case I don't have anything close to 0x00058113 (or close to that range) in the section where the .MAP file iterates through each source file (in the bottom half of the .MAP file). I'm wondering if there might be another offset I have to take into account that wasn't discussed in the article...my assumption is that I should be able to find an entry similar to:
...where nnn is the line number in the source file being mapped.
I hope my description is a little clearer.
Last Visit: 31-Dec-99 19:00 Last Update: 4-Dec-21 17:04