That stuff happens all the time when using the VB Project Converter...So I
just build from scratch as it eliminates that problem.
Regards,
Dave
From: Chuck Pelto <[EMAIL PROTECTED]>
Reply-To: Getting Started <[email protected]>
To: Getting Started <[email protected]>
Subject: Re: Super Class Confusion (Updated & Solved - Sort Of....)
Date: Sat, 7 Jan 2006 12:36:50 -0700
The problem seems to have stemmed from it forgetting it was a Push Button.
It was compounded by not being able to find PushButton in the combobox
menu of superclasses. So I had to manually type PushButton back into the
superclass. Then I had to retitle and reconfigure the button.
Fortunately, what little code there was in each button so conflicted was
not lost in all of this.
Looks like something of a minor bug somewhere in the system. Other windows
that were so moved didn't seem to have this particular problem.
The buttons involved had been copied and pasted and modified from another
window in the first project. Not sure if that's significant.
Might be a good idea to add control object superclasses to the combobox
list in the properties.
Regards,
Chuck
On Jan 7, 2006, at 12:09 PM, Chuck Pelto wrote:
I copied and pasted a window from one project to another.
There was not much code involved as the project is in it's early stages
of development.
Now, the windows objects are getting error messages during compile that
say that events ACTION or TEXT CHANGED are not legit events of their
super class. The verbiage of the text is as follows...
pbUpdate on winInformation implements the event "Action", but its
superclass does not declare such an event.
Looking at the object pbUpdate in the properties view, it is set to
PushButton.
What's the problem here and how is it corrected?
Regards,
Chuck
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
