🚀 go-pugleaf

Num passado n�o muito distante, Alan Bellingham disse...
> (The whole of Windows relies on it to show text. It's documented as
> being usable as far back as Windows NT 3.51 and Windows 95.)

  Yes. I know.
 
> If you're trying to set the text of something in a different process,
> then using the WM_SETTEXT message may work better. However, this is
> unlikely to sort out any 95/NT differences.

  See my other post.

> What won't work is a Unicode SetWindowText() under Windows 95. If your
> program is Unicode, then there's a whole lot of functions that don't do
> anything in the mixed 16/32-bit variants of Windows. If your program IS
> Unicode, then use the specifically non-Unicode SetWindowTextA()
> function.

  I tried SetWindowTextA(), but unsuccessful.

> (Happily for me, those operating systems are now unsupported by
> Microsoft, and I don't need to worry about them. The project I'm on has
> always required the 32-bit OS. I remember Microsoft promising that
> there'd only be Windows 95 as a transitional OS, and that by 1996,
> everyone would be moving over to NT. Oh yes, Vista was supposed to be
> here in 2004.)

  Unfortunately, in Brazil, we have a lot of machines running windows
  98, 95 and Me. Particularly, I have intention to stop with these
  old OS. But, for while... :)

  Thanks.

  []'s