Jump to content

  • Log In with Google      Sign In   
  • Create Account

#Actualunbird

Posted 29 November 2012 - 02:16 PM

I don't think the values disappear, I rather suspect they were not there in the first place.

The code looks semantically the same like rasterteks, so the problems lies probably elsewhere. The debug values -842150451 and -4.3160208E+08 are 0xCDCDCDCD in hex, which is a well known magic wordnumber from the visual studio C++ debug runtime, marking uninitialized heap memory.

I guess your not really loading that glyph description file (wrong path ?) in LoadFontData. Either that or you corrupt your heap elsewhere.

Edit: Hmmm, scratch that, I wasn't looking closely enough. Looks like the >> parsing fails for some reason. Check the state of the of the stream after parsing each value.

#3unbird

Posted 26 November 2012 - 05:58 PM

I don't think the values disappear, I rather suspect they were not there in the first place.

The code looks semantically the same like rasterteks, so the problems lies probably elsewhere. The debug values -842150451 and -4.3160208E+08 are 0xCDCDCDCD in hex, which is a well known magic word from the visual studio C++ debug runtime, marking uninitialized heap memory.

I guess your not really loading that glyph description file (wrong path ?) in LoadFontData. Either that or you corrupt your heap elsewhere.

Edit: Hmmm, scratch that, I wasn't looking closely enough. Looks like the >> parsing fails for some reason. Check the state of the of the stream after parsing each value.

#2unbird

Posted 26 November 2012 - 05:58 PM

I don't think the values disappear, I rather suspect they were not there in the first place.

The code looks semantically the same like rasterteks, so the problems lies probably elsewhere. The debug values -842150451 and -4.3160208E+08 are 0xCDCDCDCD in hex, which is a well known magic word from the visual studio C++ debug runtime, marking uninitialized heap memory.

I guess your not really loading that glyph description file (wrong path ?) in LoadFontData. Either that or you corrupt your heap elsewhere.

Edit: Hmmm, scratch that, I wasn't looking closely enough. Looks like the >> parsing fails for some reason. Check the state of the of the stream after parsing each value.

#1unbird

Posted 26 November 2012 - 05:02 PM

I don't think the values disappear, I rather suspect they were not there in the first place.

The code looks semantically the same like rasterteks, so the problems lies probably elsewhere. The debug values -842150451 and -4.3160208E+08 are 0xCDCDCDCD in hex, which is a well known magic word from the visual studio C++ debug runtime, marking uninitialized heap memory.

I guess your not really loading that glyph description file (wrong path ?) in LoadFontData. Either that or you corrupt your heap elsewhere.

PARTNERS