Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Parameter list in ObjectBrowser
Message
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 8
OS:
Windows XP
Miscellaneous
Thread ID:
01201138
Message ID:
01203500
Views:
16
>>Sergey and Naomi,
>>
>>I found the problem but it seems strange to me. The Methods in question both started with about 4 lines of comments before the first code line which was LPARAMETER = lcMyParameter.
>>
>>No matter what I had done previously (change the Method name, change the parameter name, recompile, etc.) the parameter list in the ObjectBrowser was empty. However, when I moved the comment lines from above the first code line to right below the first code line, everything worked and the parameter list now shows.
>>
>>Has anyone ever seen this type of behavior before?
>>
>>Ed
>
>Yes, I have heard about that before.
>
>The problem you are having must be related to the creation of the type library. That is where the object browser gets its information from. So regardless of what gets compiled, the object browser (and other clients) will only look at the type lib information.
>
>
>Markus

Markus,

Good to hear from you again. We miss you at the VFP SIG. I assume that .NET has you too occupied <g>.

I've been going through the other Methods, most of which did show the parameter list in the ObjectBrowser and noticed that the preliminary comment lines did not cause a problem if there were multiple parameters listed. There was only a problem if there was a single parameter. Also, preliminary comment lines that were empty ( ie. *| for instance) did not cause a problem but only if words followed the *| as in "*| this is a comment".

I've now gone thorough and moved type of comment, empty or not, to below the opening LPARAMETER line.

It's always something <g>.

See you later.

Ed
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform