🚀 go-pugleaf

"Richard Casten" <richard.casten@aero.org> wrote in message
news:4422D533.32E31292@aero.org...

> If I could find the length of any string in the font that is
> being used in the message box, I could figure out what
> the character position of the asterisk needs to be.

There isn't any native way to do that.  The easiest thing to do is to just
make your own dialog.  Then you can calculate the length of the strings that
you display.

> How would I get the device context given that I am using
> the MessageBox function to display the text?

The only way to gain any kind of access to the MessageBox's internals is to
install a hook via SetWindowsHookEx() for the calling thread before then
calling MessageBox().  When the hook notifies your code that new windows are
being created, you can check for the specific HWND of the text field, and
then use GetWindowDC() to get its HDC.  Even better, you can use this
technique to manipulate the MessageBox() window itself in order to expand
its dimensions, move its buttons around, add custom controls, etc.  You
could even hook the window procedure for the dialog and draw your asterik
directly onto it, rather than manipulating the string to make an asterik
fall into the desired location.


Gambit