What is lresult

How hard would it really be to port to Windows 8? All times are GMT The time now is AM. Copyright TechnologyAdvice. CodeGuru Home. Visual Basic. VB Forums. Active Oldest Votes. Improve this answer. Hans Passant Hans Passant k gold badges silver badges bronze badges. Tiny correction on the origin of Systems Hungarian as used by the SDK header files and documentation: The documentation folks apparently introduced "some serious readability changes" , and the rest is history. Wow, Microsoft is not that evil!

Felice Pollano Felice Pollano L meant "long" and W meant "word" but you should clarify that these days they are all bit or bit depending on the platform. JonathanPotter: Thanks for the correction, I was about to check. I believe the type sizes used to be different in the Win16 API, so I suppose the Hungarian prefixes in these names have a historical background.

There's a lot of history about Hungarian notation and how this version became the version that everyone knows about and is not how the inventor intended the prefixing system to work. See princeton. Community Bot 1 1 1 silver badge. Jitendra Jitendra 4, 4 4 gold badges 42 42 silver badges 63 63 bronze badges. Sign up or log in Sign up using Google.

Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Not very exciting, it's basically to get the hang of handling messages. Just make sure you've got your break; after each one. As you can see we added another case into our switch. Now we want something to happen when we get to this part of our program. First I will present the code we want to add that will show the user the filename of our program and then I will integrate it into our program.

Later on I will probably just show you the code and let you integrate it into your program. Another change happen when windows64 bit came out.

Please have a look here in MSDN to have a complete list. You can see basically the types eventually pointing to the same size bits: the only real difference is if you are using windows 32 or In term of usage meaning, they are general pourpose parameters you can use depending on what the window procedure needs to do.

The actual meaning of the wParam and lParam parameters' content depends on the particular message being sent; they are just generic buckets for message parameters. So it's quite likely that you won't be able to circumvent unsafe type casts.

So I need to use them as IntPtr. Am I safe with int or better IntPtr?