Note: forwarded message attached.
===
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
Ok - I've not made any significant changes to my base form for a while, other
than adding a new button or tow, and thus some new virtual functions to be
overridden. I try to never change the size of the form, as that can have
effects, but then it need never be changed anyway really.
-Origi
If we modify the base form in any significant way, the generated code
in inherited forms or their resource files will often become corrupted
and we have to correct the situation by hand. This can be a very time
consuming and frustrating process. If the base form is left alone,
then it will be fine
Sébastien Lorion <[EMAIL PROTECTED]> wrote:
> After losing my hairs one too many times, I really think composition
> works better than inheritance. Inheritance sounds cool but our
> experience is that it really sucks.
Maybe the implementation is at fault?
Visual Form Inheritance in Delphi has wo
Janus GridEX is pretty good for it - I worked closely with them on the release
of their Janus Suite to ensure it worked in inheritance situations, and they
have done a really nice job of it.
Dino
-Original Message-
From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On
Well, I've probably gone the worst way possible then - I visually inherit both
UserControls and Forms. The visual inheritance on Forms is to maintain a
consistent user interface, and for UserControls it allows code generated
controls to be visually modified for aesthetic reasons.
As I've mentio
You shouldn't have to do that, because I don't.
Those exceptions below I get occasionally too, and sometimes it's a control
that's just not built for visual inheritance, like the Menus and Toolbars I
think.
-Original Message-
From: Discussion of advanced .NET topics. [mailto:[EMAIL PRO
I'd say stick with what you have if it works.
The new ftp classes are subclassed off of the associated web classes...as
such I had a booger of a time getting them to work properly in a NAT
environment. I don't remember what the exact exception was, but I do
remember thinking "of *course* there is
After losing my hairs one too many times, I really think composition
works better than inheritance. Inheritance sounds cool but our
experience is that it really sucks. If you use a control (commercial
or not) that does not behave well in inheritance scenarios, you are in
for a lot of troubles. Dat
My old problem is easily re-creatable.
1) create a new winforms project.
2) add a menu on the form with an iteam
3) build
4) add another form that inherits the first form
5) add code to handle the click event of the menu item in the other form.
6) try to open the second form in design time
You w
Okay, I have been through this hell myself and generally in my app I can
solve it in one of three ways. It took me a long time and a lot of patience
to come up with these crazy ways of making the problem go away. And it comes
back sometimes, but I just do my magic incantations and I'm good to go
ag
tried that and it didn't work. It still wouldn't let me go into design
mode. What I was doing worked in vs2003 just fine.
Message from Shawn Hempel <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM
received on 07/28/2006 03:11 PM
07/28/2006 03:11 PM
Shawn Hempel <[EMAIL PROTECTED]>@DISCUSS.DEVELOP
I have a pretty complicated base form and for the most part inheritance works
pretty well for me. The worst thing I have come across is that some controls
are deliberately designed so that you cannot modify them in the derived form -
most notably the MenuStrip, ToolStrip and TableLayoutPanel.
If I understand your issue correctly -- you don't /have/ to subscribe to
inherited events like that.
Microsoft recommends you just override the base class' event handlers.
Very OOP friendly.
::
http://msdn2.microsoft.com/en-us/library/system.windows.forms.control.onenter.aspx
::
The *OnEnter*
We have opted to stay far away from Form inheritance and use
exclusively UserControls instead. So far, it has proven tolerable.
Besides, the model is much like ASP.NET so it makes it easier to
design for both when there is such a need.
Sébastien
On 7/28/06, Franklin Gray <[EMAIL PROTECTED]> wrot
Sorry all for my outburst. I've never had so much pain in going to the
next version before except when moving from COM to dotnet and that was
expected. At least then the IDE didn't have much problems. It really
buggs me that I have to put events into my base form that I inherit from
and catc
Humm, consider yourself lucky to not have worked with VS 2005 BETA 2.
RTM is rock stable compared to it ! Btw, BETA 1 was mostly fine, so
wtf happened between ?
Sébastien
On 7/28/06, Frans Bouma <[EMAIL PROTECTED]> wrote:
> http://www.windowsforms.net/articles/debuggingwsod.aspx
White
> http://www.windowsforms.net/articles/debuggingwsod.aspx
White Screen of 'Darn' ??? :) haha :)
To Franklin: yes it sucks. MS has released some patches, call PSS for
the patches. Yes that sucks even more, we all ask MS
year after year to release patches early, but that's not
http://www.windowsforms.net/articles/debuggingwsod.aspx
http://www.apa.org/topics/controlanger.html?imw=Y
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray
Sent: Friday, July 28, 2006 1:05 PM
To: ADVANCED-DOTNET@DISCUSS.DEVE
I've been working on trying to get ONE form to show in design mode FOR
DAYS and each time I figure out something that this piece of sh1t software
doesn't like and I make a workaround for it, I run into another one. I
HATE VS2005!! I recomment to everybody who is using
VS2003
Hi Eddie
>> you don't know how to receive a message asynchronously from a responsequeue.
>> If this is your problem, keep in mind that response queues are justregular
>> queues that are user created. You would retrieve the response withBeginPeek
>> and BeginReceive. If you need sample code, I
21 matches
Mail list logo
