Re: Re:[GD-Windows] Windows in .NET :(

[Javier A. <ja...@py...>]

Joe Collins <jo...@mu...> wrote:

> Well adding an empty wndproc wasn't enough. I had to set the cursor
> and icon as well. Looks like
> it still complains about an invalid menu handler but it doesn't crash
> anymore :)

Clearing all fields to zero is definitely a good idea. You don't want to
have a random window proc, a random icon handle or such stuff in your window
class.

For a dummy window, ::DefWindowProc() as the window proc should be good
enough, but quite frankly, I have never done that myself (even for the
dumbest of hello world apps I at least add a check for ESC). I have no clue
if a NULL WndProc is supposed to work.

> I guess .NET is a bit pickier than vc6 libs.

Uninitialized variables are always broken no matter the compiler. It's just
that sometimes they happen to not blow up in your face. :)

> As far as .NET being horribly broken... well one could argue that the
> change from workspaces
> to solutions is broken. It definately does not behave the same as vc6
> workspaces. ;)

I don't particularly care about solutions vs. workspaces, but I definitely
agree that many tasks in the new IDE are much more cumbersome than in VC6:

 - They require more mouse clicks for just about everything,
 - Some hotkeys like Alt-F7 are now context-dependent,
 - The advanced editor mode has a tendency to start eating your source code
away.

If you're doing non-.NET C++ projects then it's definitely a good idea to
stick with VC6 (that's what I do) and wait for future, more refined versions
of the new environment. But it doesn't hurt to play with it on the side
(.NET forms are _cool_, MFC be gone for good!) to minimize the future
transition.

  Javier Arevalo
  Pyro Studios