Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link Templates: Using child template with application templates 1998-10-24 -- Phillip Carroll Newsgroups: TopSpeed.Topic.Templates
Editors note: Please note that some lines may wrap in the template code.
In article <3630e749.10670386@TSNews.Clarion.Com>, Arnor Baldvinsson
wrote:
> I have a very small template that works fine as a procedure extension
> template. It stuffs one variable into the #LOCALDATA and then one or
> two lines of code to put data into this variable. If I change this to
> global extension template, the #LOCALDATA is not generated. If I
> change it to put the variable into a local declaration embed it works
> fine, but then this variable doesn't show up on the field list. This
> variable can't be global as it must be procedure based, not thread
> based and it must be available in the local data field list. Any
> ideas?
>
Arnor, why not use:
#EXTENSION(),APPLICATION(child(chain))
In the child procedure extension template, you can use #LOCALDATA.
Phil Carroll
Paragon Design & Development
http://www.paragondandd.com
Today is May 6, 2024, 7:00 am This article has been viewed 35114 times. Google search has resulted in 9 hits on this article since January 25, 2004.
|
|