Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualL. Spiro

Posted 29 November 2012 - 02:36 PM

Now the application isn't breaking/crashing at this point, it's breaking at another method called "UpdateSentence" which you can see in the screenshot here:

Then why don’t you show the code for UpdateSentence()?

Also, sentence3 is garbage when it is passed to UpdateSentence(). I assume it is a member of the Text class.
Naming conventions such as m_ would go a long way to help people realize from where variables are coming.
It needs to be initialized—this has nothing to do with the functions listed in the topic.


L. Spiro

#3L. Spiro

Posted 29 November 2012 - 02:35 PM

Now the application isn't breaking/crashing at this point, it's breaking at another method called "UpdateSentence" which you can see in the screenshot here:

Then why don’t you show the code for UpdateSentence()?

Also, sentence3 is garbage when it is passed to UpdateSentence(). I assume it is a member of the Text class.
Naming conventions such as m_ would go a long way to help people realize from where variables are coming.
It needs to be initialized.


L. Spiro

#2L. Spiro

Posted 29 November 2012 - 02:34 PM

Now the application isn't breaking/crashing at this point, it's breaking at another method called "UpdateSentence" which you can see in the screenshot here:

Then why don’t you show the code for UpdateSentence()?

Also, sentence3 is garbage when it is passed to UpdateSentence(). I assume it is a member of the Text class.
Naming conventions such as m_ would go a long way to help people realize from where variables are coming.


L. Spiro

#1L. Spiro

Posted 29 November 2012 - 02:32 PM

Now the application isn't breaking/crashing at this point, it's breaking at another method called "UpdateSentence" which you can see in the screenshot here:

Then why don’t you show the code for UpdateSentence()?


L. Spiro

PARTNERS