>All,
>
>If you're like me, you want to have intellisense on your public objects, for example your applic object. Now of course you could do,
>
>
LOCAL m as mdot, Applic as Applic OF source\classes\applic.prg
>
>But then of course you are creating a new variable in stead of using the global object. And of course you can create a second variable and assign the applic object to it
>
>
LOCAL m as mdot, lApplic as Applic OF source\classes\applic.prg
>
>lApplic = Applic
>...
>
>But that is really a painfull workarround. I found a glitch in the intellisense mechanism so we can fool it.
>
>
LOCAL m as mdot OF
>
>Intellisense does not see the && and continues to read the expression after it, while the VFP compiler sees anything after the && as a comment and therefore does not create a local applic variable. So you now can use the applic object directly with intellisense.
Maybe you could put these two tips together as an article on this site?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
