The same project, on the other computer operation is a success, but copied to your computer will go wrong, and shows an assertion fails, like I ordered retry after it triggered a breakpoint, showed that yellow icon place has a problem, I don't know how to solve, is there a big help to see see! Just to BBS, score is not much, also, every brother please forgive me

CodePudding user response:

This error should be no handle to get to the dialog box or controls, you can debug

CodePudding user response:

MFC version will be the problem? Can be statically compiled?

CodePudding user response:

refer to the second floor SuperDay response:

MFC version will be the problem? Can be statically compiled?

No, static compilation was assertion failure problem, and are VS2012 version

CodePudding user response:

reference 3 floor IT chicken dishes of the new reply:

Quote: refer to the second floor SuperDay response:

MFC version will be the problem? Can be statically compiled?

No, static compilation was assertion failure problem, and are VS2012 version

but it is possible that other places error caused by the hills in the

CodePudding user response:

reference 1st floor kuangbao9 response:

this error should be no access to the dialog box or control to handle, you can debug to see

According to the process of debugging the program, I found here is to not bottom go to, is there will be an assertion fails, but it's too dishes, at reading,

CodePudding user response:

Estimation is the lack of any control or window created and registered and failure, and resources under the edit box controls useful to what?

CodePudding user response:

It looks like is HWND handle is invalid, you open the call stack under Debug, first find the error function call, first ~

CodePudding user response:

Should be the window to create unsuccessful cases, calls the GetClientRect () interface, where they are in the call, to determine whether to create success, if you don't succeed, see what reason, usually is the use of the controls, but the lack of control leads to the window created on the target computer failure, can check it in the output window of vs, see if there was any failure of the print

CodePudding user response:

refer to the eighth floor of red - fly reply:

create unsuccessful cases should be a window, call the GetClientRect () interface, where they are in the call, to determine whether to create success, if you don't succeed, see what reason, usually is the use of the controls, but the lack of control leads to the window created on the target computer failure, can check it in the output window of vs, to see if there was any failure of print

Is this why? In another program to realize the same function, has been showed me unregistered Activex controls, but I have to manually add a success, tried many ways can't, before the

CodePudding user response:

reference IT, 9/f, chicken dishes sprout new response:

is the reason? In another program to realize the same function, has been showed me unregistered Activex controls, but I have to manually add a success, tried many ways can't, before the

This control is failure control window used in your program? If so, then at least there's a reason for that