Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
B

boxmonkey

@boxmonkey
About
Posts
5
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Design dialog for various resolutions without switching to that resolution
    B boxmonkey

    I'm trying to make a dialog that fits on screen resolutions 800*600 and up. My resolution is 1600*1200. When I was originally designing my dialogs I foolishly assumed that the number Visual Studio gives in the lower right hand corner is the size of the dialog in pixels, so I designed it to be less than 700. Lo and behold, it's way too big for an 800*600 resolution. How the heck do I know what numbers to keep the size under? Thanks, Jay

    C / C++ / MFC csharp css visual-studio design question

  • !UPDATED! Debug works but release crashes (this one's tricky)
    B boxmonkey

    You, sir, are a life saver. I assumed that: a) Since Visual Studio generated the message handler for me, it must be right (ha!) and b) Since CFormHelperDlg calls CDialog::OnInitDialog(), it would be ok My understanding of how all this stuff works starts to get pretty cloudy when it comes to areas like this. Thanks again for the help.

    C / C++ / MFC help announcement database debugging tutorial

  • !UPDATED! Debug works but release crashes (this one's tricky)
    B boxmonkey

    Alas, I had already read this article, to no avail.

    C / C++ / MFC help announcement database debugging tutorial

  • !UPDATED! Debug works but release crashes (this one's tricky)
    B boxmonkey

    Call stack looks like this: CWnd::GetStyle(const CWnd * const 0x0012f758 {CJailDialog hWnd=0x002d0b20}) line 195 + 1 byte _AfxHandleActivate(CWnd * 0x0012f758 {CJailDialog hWnd=0x002d0b20}, unsigned int 1, CWnd * 0x00323fc0 {CMainFrame hWnd=0x003f011c}) line 145 + 11 bytes MFC42! 5f401be9() CWnd::WindowProc(CWnd * const 0x0012f758 {CJailDialog hWnd=0x002d0b20}, unsigned int 6, unsigned int 1, long 4129052) line 1596 + 27 bytes AfxCallWndProc(CWnd * 0x0012f758 {CJailDialog hWnd=0x002d0b20}, HWND__ * 0x00000000, unsigned int 6, unsigned int 1, long 4129052) line 218 AfxWndProc(HWND__ * 0x002d0b20, unsigned int 6, unsigned int 1, long 4129052) line 377 + 16 bytes AfxWndProcBase(HWND__ * 0x002d0b20, unsigned int 6, unsigned int 1, long 4129052) line 220 + 21 bytes USER32! 77d43a50() USER32! 77d43b1f() USER32! 77d444f5() USER32! 77d44525() NTDLL! 77f75da3() 58000080() I don't know about you, but that doesn't seem very helpful to me...

    C / C++ / MFC help announcement database debugging tutorial

  • !UPDATED! Debug works but release crashes (this one's tricky)
    B boxmonkey

    Original message: I have read the codeproject article about Finding crash information using the MAP file, which was helpful, but I'm stuck. I have a very complex program full of dialog boxes that are derived from a class that is derived from CDialog. Inside these dialogs are a bunch of edit boxes of type CTableFieldEdit, which is derived from CEdit. The program works beautifully in debug mode, but crashes in release mode some time between when I create the dialog item and when I call DoModal() From what I've been able to determine, the crash happens in MFC42.dll, but it crashes in two different places, depending on which dialog I'm calling. Some of the dialogs crash at the address for GetStyle and some of them crash after the address for ScrollWindowEx, according to the map file. I have already turned off all optimizations. I'm stuck. What might I be doing wrong? I can post some or all of the code if it will help. I can even post the entire project if you like, but you won't be able to run the program as it connects to a database. Thanks! Update: The problem seems to be related to how I handle message maps in my derived dialog classes, but I don't know how to fix it or why it works correctly in Debug mode, but not Release mode. Here's what's happening: My Dialog boxes are derived from CFormHelperDlg, which is a class I made to reduce code redundancy. CFormHelperDlg is derived from CDialog. There are certain messages I want to handle in CFormHelperDlg rather than in the class for each given dialog (since all the code is redundant), so I set up my message maps as such: In CJailDialog (which is derived from CFormHelperDlg): BEGIN_MESSAGE_MAP(CJailDialog, CFormHelperDlg) //{{AFX_MSG_MAP(CJailDialog) //}}AFX_MSG_MAP END_MESSAGE_MAP() In CFormHelperDlg (which is derived from CDialog): BEGIN_MESSAGE_MAP(CFormHelperDlg, CDialog) //{{AFX_MSG_MAP(CFormHelperDlg) ON_BN_CLICKED(IDC_BUTTON_JAN, OnButtonJan) ON_BN_CLICKED(IDC_BUTTON_FEB, OnButtonFeb) ON_BN_CLICKED(IDC_BUTTON_MAR, OnButtonMar) ON_BN_CLICKED(IDC_BUTTON_APR, OnButtonApr) ON_BN_CLICKED(IDC_BUTTON_MAY, OnButtonMay) ON_BN_CLICKED(IDC_BUTTON_JUN, OnButtonJun) ON_BN_CLICKED(IDC_BUTTON_JUL, OnButtonJul) ON_BN_CLICKED(IDC_BUTTON_AUG, OnButtonAug) ON_BN_CLICKED(IDC_BUTTON_SEP, OnButtonSep) ON_BN_CLICKED(IDC_BUTTON_OCT, OnButtonOct) ON_BN_CLICKED(IDC_BUTTON_NOV, OnButtonNov) ON_BN_CLICKED(IDC_BUTTON_DEC, OnButtonDec) ON_BN_CLICKED(IDC_MANAGER_SIGNOFF, OnManagerSignoff) ON_ME

    C / C++ / MFC help announcement database debugging tutorial
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups