wsprintfW

[SolidCode]

This is a question to Mr. Hutchesson.

I was unable to link wsprintfW from user32.lib that comes with MASM32v8. user32.inc never knew about it either. So I had to add this proto to INC and use user32.lib from Visual Studio.

What would you say about it? Did I miss something? ::)

[hutch--]

Nope,

the include files are produced by a tool that only creates STDCALL prototypes. For wsprintfA, I have the prototype in the windows.inc file but I have not written one manually for the unicode version. What you have done is fine.

[SolidCode]

Hello, Steve!

Thank you very much for the answer. :8) At least I know I did not break a law or something. So I can use this solution now. But can we hope that in the future versions you will have this call implemented so that writing applications that can be compiled as ANSI or Unicode versions would be easier?
:clap: And I also would like to express that MASM32 is the best tool for software development. It is the best combination of HLL features with pure Assembler. Thus it gives me power over each byte in code and data of each application I am creating and yet invoke, if-else-endif, repeat and other similar things help the code to be easier to read, but I can always change it with pure assembler opcodes if I want something custom.
Now I try to force myself to study VC++. :( It is soooooo limiting. :'( I spent several hours trying to convert from const string to uchar. Finally I quit, made an inline asm block and did it through lstrcpy, which was not limiting in asm. :dance: I know it was not the best solution. But I was sick and tired of fighting with the tool that is supposed to help me. Yet Visual C++ is the best HLL out of Delphi, Basic, Java, Fortran, Lisp, FoxPro, Clipper etc. :boohoo:

[hutch--]

 :bg

Sounds like you are hooked already. The strong typing in C++ pisses a lot of people off but its there to keep the idiots at bay. This is not a problem in assembler as idiots don't last long but with a bit of practice you can circumvent the strong typing with over-rides where you need to.

When is a HANDLE != to a UINT ?

When you use a DWORD in MASM.  :toothy