Home > Software engineering >  The trouble with ExtTextOutW output problem
The trouble with ExtTextOutW output problem

Time:09-29

Recently in the Windows API, using Detours library intercept in intercepted ExtTextOutW output string is garbled, when someone pointed out that this is due to network
FuOption ExtTextOutW function parameter specifies the ETO_GLYPH_INDEX, MSDN interpretation is as follows:
The lpString array refers to an array returned from GetCharacterPlacement and should be parsed directly by GDI as no further language-specific processing is required. Glyph indexing only applies to TrueType fonts, but the flag can be used for bitmap and vector fonts to indicate that no further language processing is necessary and GDI should process the string directly. Note that all glyph indexes are 16-bit values even though the string is assumed to be an array of 8-bit values for raster fonts.
But when the intercept to intercept GetCharacterPlacement isn't this function? Someone explain the characters of the index is how to get it??

CodePudding user response:

By ExtTextOutW DrawText calls

CodePudding user response:

reference 1st floor hurryboylqs response:
ExtTextOutW might be DrawText called


Tried, also not be, I also saw the disassembly, have no, I don't know what's the matter,

CodePudding user response:

I also encountered this problem, help the top!

CodePudding user response:

Download
" Windows graphics programming source code \ Samples \ Chapt_04 \ Patcher \ main CPP"
  • Related