Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problems with child class
Message
From
13/12/2006 12:28:59
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
13/12/2006 11:06:06
Calvin Smith
Wayne Reaves Computer Systems
Macon, Georgia, United States
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Miscellaneous
Thread ID:
01177142
Message ID:
01177255
Views:
16
>Mike,
>I am a little confused by your reply. Do you mean that if I edit the class and press any key while it is open and then save it, then the default will no longer fire.

The above.

> Or do you mean that if I edit the class, do not hit any key, and then save it the default will no longer fire.

No.

>
>I understand that a space, tab, or enter key will fool the compiler into thinking something is there, but when I opened this the cursor was blinking at the end of the parameter with nothing in between. In any case, this is a good argument for requiring something like an 'override' keyword. The 100 or so customers that downloaded this update will have a difficult time understanding that their application no longer functions correctly even though no code was changed ( at least not willingly ).
>
>I just looked at the code in the class browser and in the old definition of the grandchild class there is nothing except the class name. However, in the version that I sent out on Monday there is the recal function with a parameter. This is really really a bad feature in VFP. I certainly did not indend to do this and the interface did not tell me that I had.
>
>We are struggling with rewriting our app. I have been doing fox since 1989 but it may be time to move to a compiled language that will enforce good programming habits.

I can't advise you on that. Personally I don't want a computer to tell me what to do. I want it to help me, if I tell it to. Programming smarts into the system *always* bites someone!

I would have preferred a button to tell it to get the lparameters line, and not just do it automatically and then have to undo it, if *it* decides(?!?!?) I didn't want to keep the line.

However, if I see a line with just LPARAMETERS, I know there's something wrong. If I wrote anything in that method it would be like this:

LPARAMETERS one, two, three
LOCAL lcParms
lcParms = x5pitems("one, two, three",PCOUNT())
RETURN EVAL("DODEFAULT("+ m.lcParms + ")")

x5pitems returns a string consisting of "" up to the number of parameters passed.
Previous
Reply
Map
View

Click here to load this message in the networking platform