c++.mfc - outstanding
- bw (11/11) Sep 15 2002 wow this is great! tell you what, it sure was worth the learning curve ...
- Jan Knepper (3/11) Sep 18 2002 Probably because members of CWinApp that GetProfileInt uses not being
- bw (11/16) Sep 18 2002 maybe an uninitialed something being deleted? i do have some old docume...
- Jan Knepper (3/22) Sep 18 2002 I would suggest looking into the CWinApp code and see what it does with ...
- bw (2/4) Sep 18 2002
wow this is great! tell you what, it sure was worth the learning curve to get the mfc classes setup. i finally figured the default compile and link options do pretty fine really... not a lot of difference i can see. been playing a little bit with the new stuff, i have some inspiration now! the invalid page fault on exit in the one app i was porting from mfc2.0 was because there was some code in the main class file using GetProfileInt() during the InitInstance() function. beats me why this was a problem but i replaced it with the SDK version GetPrivateProfileInt() works fine now. well, i'm off to look for hints & tips & other stuff. L8r, bw
Sep 15 2002
bw wrote:wow this is great! tell you what, it sure was worth the learning curve to get the mfc classes setup. i finally figured the default compile and link options do pretty fine really... not a lot of difference i can see. been playing a little bit with the new stuff, i have some inspiration now! the invalid page fault on exit in the one app i was porting from mfc2.0 was because there was some code in the main class file using GetProfileInt() during the InitInstance() function. beats me why this was a problem but i replaced it with the SDK version GetPrivateProfileInt() works fine now.Probably because members of CWinApp that GetProfileInt uses not being initialized...
Sep 18 2002
maybe an uninitialed something being deleted? i do have some old documentation. i set m_pszProfileName="theapp.ini" in InitInstance() and it works fine in mfc2.0 maybe i should do that in the constructor? there's an appwizard generated call to LoadStdProfileSettings() and i'm not real sure what it does? if i should set the profile name before it's call or after... there's no info in my ini file it would want anyway. i've been looking over the mfc source, looks like there's still a ways to go before we get to use the sfc50.dll but everything i've tried using the nafxcw.lib works great and i'm having a lot of fun!! thanks JAK! In article <3D889EC4.16D488C7 smartsoft.cc>, Jan Knepper says...because there was some code in the main class file using GetProfileInt() during the InitInstance() function. beats me why this was a problem but i replacedProbably because members of CWinApp that GetProfileInt uses not being initialized...
Sep 18 2002
I would suggest looking into the CWinApp code and see what it does with regards to certain members. bw wrote:maybe an uninitialed something being deleted? i do have some old documentation. i set m_pszProfileName="theapp.ini" in InitInstance() and it works fine in mfc2.0 maybe i should do that in the constructor? there's an appwizard generated call to LoadStdProfileSettings() and i'm not real sure what it does? if i should set the profile name before it's call or after... there's no info in my ini file it would want anyway. i've been looking over the mfc source, looks like there's still a ways to go before we get to use the sfc50.dll but everything i've tried using the nafxcw.lib works great and i'm having a lot of fun!! thanks JAK! In article <3D889EC4.16D488C7 smartsoft.cc>, Jan Knepper says...because there was some code in the main class file using GetProfileInt() during the InitInstance() function. beats me why this was a problem but i replacedProbably because members of CWinApp that GetProfileInt uses not being initialized...
Sep 18 2002
excellent idea, just as soon as i find it... :-) In article <3D88BE72.9FC64B3 smartsoft.cc>, Jan Knepper says...I would suggest looking into the CWinApp code and see what it does with regards to certain members.
Sep 18 2002