 |
|
 |
Isn't this visual inheritance much ado about nothing? For as far as i can see it is exactly the same as making a "new form" and, instead of deriving from "System.Windows.Form", deriving from another form. So, the whole thing just saves you from manually changing 1 word in source code. Big deal.
Or did i miss something?
Regards,
Philippe
Philippe Dykmans
Software developpement
Advanced Bionics Corp.
|
|
|
|
 |
|
 |
Interesting but, walkthrough would be nice to have for VS 2008.
Jon
|
|
|
|
 |
|
 |
Hi,
I have read your artical. It was very helpful. But I have a problem: I created a base form lets call frmBaseForm. In this form i have a part like "dataGridView1.Rows[getrowIndexmetod("ROW_NAME")].Cells[0].Value". And I created an inherited form, lets call frmChildForm, that using this base form. At the run time I dont have a problem. But at the design time an error prevents me to see frmChildForm. It says "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index". I have to get row index at the runtime by using "getrowIndexmetod" metod. There is no way that I can know at the design time. So what can I do?
Many thanks
Sengul
|
|
|
|
 |
|
 |
Great Form Inheritance tutorial. just what i have been looking for. Thanks! T
Age is a consequence of experience
|
|
|
|
 |
|
 |
I mean, I put ImageList containing Images, that I want to use through the whole application, in my base form, and then I want to use images from this list in ComboBox in inherited form. But inherited ImageList is not visible in property designer. Any ideas?
Krzysiek
|
|
|
|
 |
|
 |
Hi,
Visual Inheritance is quite pretty buy seems not work, when you port you base form into a code library ( "DLL"), if you make that your client application would complain saying that doesn't find the resource...
It's that a bug ?
|
|
|
|
 |
|
 |
Is your directory path where the DLL is located have a '#' in it somewhere? My project directory used to be named C:\Projects\VS.NET\C#\ProjectDir and I would get the problem you describe all the time. I renamed the 'C#' dir to 'CSharp' and now it works 100% of the time without the "cannot find resource" error.
Try changing the path where the DLL is located and it should work. For some reason, it does not like having a '#' in the path with visual inheritance. Not sure why, but it fixed it for me.
-Ryan
|
|
|
|
 |
|
 |
what are we supposed to type in...?
great article, thanks!
|
|
|
|
 |
|
 |
I've been using Visual Inheritance for years
in Borland Delphi. I can understand why M$
copied it. The question is not whether you
can use Visual Inheritance, but whether you
can override published properties of inherited
components in descendent forms, as you can in
Delphi.
For example, in Delphi I can create the exact
same 'virtual base' form class, and then
create any number of forms derived from it.
On each derived form, I can then change various
properties of inherited components (which is
like something like 'overriding' their values
in the base class), to for example, change the
size or location of a list box or picture.
Well, what you've demonstrated might sound cool
to VB/C# fans, but for us Delphi hackers, it's
taken for granted.
|
|
|
|
 |
|
 |
Because some of us are paid to work with Microsoft tools.
|
|
|
|
 |
|
 |
maybe you could convince youer employer to use a superior product...
|
|
|
|
 |
|
 |
Ms has always delivered much user friendly and more powerful IDE than any other.
Also I deal with a stubborn boss, so it might cost me my job.
It is a personal choice (a bit like a religion), whether Borland or Ms. Both have there strength and weakness.
Let people choose what they like and believe in.
j.y.a
|
|
|
|
 |
|
 |
Soon we all, MS, Borland and others fans, will start writing for the .NET environment, same way we all are writing for COM and Win32 nowdays. And then we may have great fun if we could read these threads ))
I could complete the saying like that: Let people choose what they like and believe in, since all they are writing for the .NET and the language is a matter of personal choice
S.T.A.
(nothing to do with the STA ))) )
|
|
|
|
 |
|
 |
MS releasing a user-friendly RAD? Ha!
|
|
|
|
 |
|
 |
Visual Studio isn't a true two way RAD. Delphi is the only one to make it correcly, and it is very, very much user friendly.
The conceptor of C# can confirm this. He is the conceptor of Delphi.
|
|
|
|
 |
|
 |
Go drink some bleach you troll.
|
|
|
|
 |
|
 |
I doubt anyone in their right mind would argue against the fact that Borland has always delivered innovative and cleaver tools. The problem is that they have never been able to attain critical mass to be taken seriously.
Yes, the idea of visual inheritance is not new to Delphi hackers. However, those of us who attempt to make a living at this do not really want to fight the continual battle of educating our customers.
My clients do not really care what tool I use to create their solution, they do care that they will be able to EASILY find someone to support the solution if I disappear. That is why as a professional I am reluctant to bet my income on Borland.
Besides MS provides a variety of tools to attack a variety of problems. I know many delphi types who think that it is the ONLY solution. Oh well, I guess when all they have is a hammer we should probably forgive them for seeing every problem as a nail.
|
|
|
|
 |
|
 |
If you did your homework, you would know that .NET was headed by Anders Hejlsberg, who headed Delphi. If you really looked at C#, you would see that it contains a lot of Delphi in it. Anders is all over this thing. That means that all the good stuff from Delphi is now in C#.
|
|
|
|
 |
|
 |
COBOL, FORTRAN, ... or better.. the fastest and the best one Assembly...
It's a pity that borland has not the power that it had years ago, I mean Turbo Pascal, was quite good... but now... M$ has the power
|
|
|
|
 |
|
 |
Can you tell me what version(s) of Delphi? Thanks!
|
|
|
|
 |
|
 |
Here's why not: VS.NET has more momentum than any other IDE ever - Borland is going to be left behind along with C++.
|
|
|
|
 |
|
 |
I can appreciate everyone's passion on the subject, but the best language to use is purely subjective, and usually close-minded individuals have the "your language sucks" mentality.
Companies that choose MS products do so for 3 reasons. The IDE (i.e. higher productivity), the support from the company & initial cost, and the size/quality of the talent pool. If a minority of developers use a language, it's too expensive/difficult to find good folks.
Honestly, I've hired tons of MS and Java people and zero delphi folks (in fact, i've never seen a resume with delphi on it).
And let's all be honest, Delphi didn't invent visual inheritance. Early adoption does not equal invention. OOP academics have been talking about visual inheritance since before OOP was accepted. I have the same argument when Java guys think C# is a copy of Java. I'm quick to remind them that Java, like C#, is a C-based language, both borrowing syntax entirely from C.
Again, just because you did it first, doesn't mean you invented it, any more than saying your bank invented money since that's where you've been getting it for years.
Angelo
|
|
|
|
 |