Thanks for the link, it really helped me. However, the original question
still remains: wouldn't it have been easier to start with a good design in
the first place at MS, so that people wouldn't have been forced to re-invent
the wheel?
Thanks again,
Ovidiu Platon.

-----Original Message-----
From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of
Graeme Foster
Sent: Sunday, May 19, 2002 10:26 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Toolbar problem: Can't teach an old developer new
tricks?


The built in toolbars are pretty weak. However, it's a great platform
for rolling your own solutions where it doesn't meet your needs, and as
it happens, you don't always need to... We're using Lutz Roeder's
CommandBar for .NET and the results are great.

http://www.aisto.com/roeder/dotnet/

HTH,
G.


-----Original Message-----
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Ovidiu Platon
Sent: 19 May 2002 18:50
To: [EMAIL PROTECTED]
Subject: Toolbar problem: Can't teach an old developer new tricks?


Hello everybody,
So far, I like the current .NET implementation from Microsoft. However,
I have noticed some problems that make me think the people at Microsoft
haven't really moved to a modern way of doing this programming stuff
we're all in. What's my problem, you'll say... Well, the other day I was
working with the ToolBar control from the Windows Forms namespace. All
cool, create an image list, create buttons and so on... When I
double-click a button in the forms designer, I notice that the event
handler is named myToolBar_OnClick; I click another button and I get to
the same handler. To make the long story short: I wonder why the
ToolBarButton class doesn't raise a Click event of its own. The MSDN
docs say "create a switch structure and identify the button that was
clicked". It looks to me like the people at Microsoft haven't got rid of
the WndProc idiom (or I may be totally wrong, who knows?).
Unfortunately, this makes me think .NET isn't (yet) the component
oriented platform everyone's been waiting for. What do you think about
it?

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to