manual kerning with winAPI
-
I'm working on a program that needs to be able to detect when the user has clicked on a font glyph - the actual filled part of the glyph, not just its bounding box. I'm trying to do this by analyzing the outline produced by GetGlyphOutlineW for each glyph. In this program, most glyphs are drawn by passing a single codepoint to TextOutW, but there is one case where I pass multiple codepoints. I understand that in this case, I have to take kerning into account in order for my analysis of the glyph outlines to match up with what TextOutW draws. Keeping in mind that I want to stick to C API's since the program is actually in another language and calling winAPI through a foreign function interface, are the GetKerningPairs functions the only way to get the necessary information to account for the kerning? In particular, do I have to iterate through all the kerning pairs for the entire font and check each one for whether it matches the pair I'm trying to kern rather than, say, asking Windows for the kerning pair for a particular pair of characters, if one exists?