I do the same (vast use of inheritance with Forms (with C#
2.0)) and have no
problems with VS2005. I am using the Infragisitics 2006 V1
and V2 controls
(menu's. toolbars, mditabs, the works).
---
Vince
> -----Original Message-----
> From: Discussion forum for developers using Windows
Forms to build apps
and
> controls [mailto OTNET-WI
NFORMS DISCUSS.DEVELOP.COM] On Behalf Of Dean
> Cleaver
> Sent: Wednesday, July 26, 2006 16:25
> To: DOTNET-WINFORMSDISCUSS.DEVELOP.COM
> Subject: Re: [DOTNET-WINFORMS] The event Click is
read-only and cannot be
> changed.
>
> Franklin,
>
> Without seeing your specific example I can't help, but
I can tell you I
make extensive
> use of inheritance in Forms including the toolbars (I
use Janus controls
though, not
> the standard .Net toolbars) and it does indeed work.
>
> I have a feeling I tried with the standard toolbars for
about 5 minutes,
and struck
> problems - can't remember what, because I didn't try
hard - I already had
Janus
> working and was just trying for a comparison. The team
at Janus put quite
a bit of
> effort into making their toolbars work with inheritance
for me when they
first put
> them out, and they do work well.
>
> Dino
>
> -----Original Message-----
> From: Discussion forum for developers using Windows
Forms to build apps
and
> controls [mailtoOTNET-WI
NFORMSDISCUSS.DEVELOP.COM] On Behalf Of
> Franklin Gray
> Sent: Thursday, 27 July 2006 09:16
> To: DOTNET-WINFORMSDISCUSS.DEVELOP.COM
> Subject: Re: [DOTNET-WINFORMS] The event Click is
read-only and cannot be
> changed.
>
> Closing all forms, then closing the IDE and even adding
a reboot wouldn't
solve this
> problem. I have traced it down to all forms that
inherit a basic form
that we have
> our menu and toolbar on. I think what it is having a
problem with is the
menu is on
> the parent form (form inheriting
> from) and the code for the menu items is in the child
form. Anybody know
of a
> workaround without getting ride of my inheritance?
>
>
>
>
>
> Message from Stoyan Damov
> <stoyan.damovGMAIL.COM>DISCUSS.DEVELOP.COM
> received on 07/25/2006 05:41 PM
>
> 07/25/2006 05:41 PM
>
>
>
> Stoyan Damov <stoyan.damovGMAIL.COM>DISCUSS.DEVELOP.COM
>
> Please respond to Discussion forum for developers using
Windows Forms to
> build apps and controls
> <DOTNET-WINFORMSDISCUSS.DEVELOP.COM>
> Sent by Discussion forum for developers using Windows
Forms to build apps
> and controls <DOTNET-WINFORMSDISCUSS.DEVELOP.COM>
>
>
>
> To: DOTNET-WINFORMSDISCUSS.DEVELOP.COM
> cc:
> Subject: [POSSIBLE SPAM]::Re:
[DOTNET-WINFORMS] The event
> Click is read-only and
> cannot be changed.
>
> On 7/26/06, Franklin Gray <franklin.w.grayus.abb.com> wrote:
> > Does anybody know what this is? I get several of
these on a page when
> I
> > try to open up a windows form in design mode.
> >
> >
> >
> > The event Click is read-only and cannot be
changed.
> > Hide
> >
> > at
> >
>
System.ComponentModel.Design.EventBindingService.EventProper
tyDescriptor
> .SetValue(Object
> > component, Object value)
> > at
> >
>
System.ComponentModel.Design.Serialization.CodeDomSerializer
Base.Deseria
> lizeAttachEventStatement(IDesignerSerializationManager
> > manager, CodeAttachEventStatement statement) at
> >
>
System.ComponentModel.Design.Serialization.CodeDomSerializer
Base.Deseria
> lizeStatement(IDesignerSerializationManager
> > manager, CodeStatement statement)
> >
>
> Whatever the designer error might be, it can be usually
fixed by:
> - closing *all* windows in the IDE
> - exititing the IDE
> - starting the IDE
>
> If you don't close all windows, or re-start the IDE
you'll get the error
to the 2nd
> comming. Where the fuck is ... aaaah, it's scheduled
for Q3 2006 ;)
>
> Cheers,
> Stoyan
|