Hi
I think you should be abel to refferance an attribute directly but as you
have expirenced it some times gives problems, specially if the attriubte
contains some off the special tcl carracters \ # ; {} etc.
So the best way is to use the fme tcl functions ex FME_GetAttribute etc and
then embed it all in at proc
proc myLog {}{
FME_LogMessage fme_inform [FME_GetAttribute message]
}
note the use off [] rather than ()
in the tcl function you then call the proc @Tcl2(myLog)
Peter Laulund
>From: "mark2atsafe" <[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: [fme] Re: Writing a Message to FME LOG file
>Date: Sat, 05 Aug 2006 16:58:46 -0000
>
>I don't think you could put an attribute in there directly - you'd
>need to use the FME-TCL option to return it; in this case
>FME_GetAttribute <attributeName>
>
>So experiment with something like...
>
>FME_LogMessage fme_inform (FME_GetAttribute message)
>
>I assume you can nest these functions in this way. Again check out
>@Tcl2 in the FME Functions + Factories manual (in Workbench Help) for
>other functions like this and for the possibility of a good example.
>
>Regards,
>
>Mark
>
>Mark Ireland, Senior Product Specialist
>Safe Software Inc. Surrey, BC, CANADA
>[EMAIL PROTECTED] http://www.safe.com
>Solutions for Spatial Data Translation, Distribution and Access
>
>
>--- In [email protected], "mhabarta" <[EMAIL PROTECTED]> wrote:
> >
> > Thanks Mark for the tip ...
> >
> > I tried and the next problem I run into is with any blank space
> > in the message. It ends with the first blank.
> >
> > My parameter line in TCL Caller is:
> >
> > FME_LogMessage fme_inform &message
> >
> > where "message" is the attribute holding the message.
> >
> > I can't seem to find a quoting method to bypass the blank space
> > problem... I tried:
> > "&message"
> > {&message}
> > '&message'
> >
> > ... seems my TCL insight is too small ...
> >
> >
> > Michael
> >
> >
> > --- In [email protected], "mark2atsafe" <mark.ireland@> wrote:
> > >
> > > Hi Michael,
> > > The Logger won't do it, because the @Log() function only writes
> > > feature info with the message.
> > >
> > > However - the @Tcl2() function is the one you need - and can be run
> > > from the TCLCaller.
> > >
> > > In the TCLCaller set the TCL Expression to:
> > >
> > > FME_LogMessage fme_inform xxxx
> > >
> > > ...where xxxx is the message you want logging. Check the @Tcl2()
> > > function in the FME Functions, Factories and Transformers manual for
> > > the different options that are available (eg call it ERROR or WARNING
> > > instead of INFORM).
> > >
> > > Good question - I didn't realize you could do this until I checked
> > it out.
> > >
> > > Regards,
> > >
> > > Mark
> > >
> > > Mark Ireland, Senior Product Specialist
> > > Safe Software Inc. Surrey, BC, CANADA
> > > support@ http://www.safe.com
> > > Solutions for Spatial Data Translation, Distribution and Access
> > >
> > >
> > > --- In [email protected], "mhabarta" <mhabarta@> wrote:
> > > >
> > > > Hallo
> > > >
> > > > Anybody has an idea, how to write a message to the FME LOG ?
> > > >
> > > > LOGGER writes a feature to the log, but I want to write a text
>message
> > > > to the LOG.
> > > >
> > > > Thanks Michael
> > > >
> > >
> >
>
>
>
>
>
>
>
>Join us at the FME Worldwide User Conference Sept. 21-22, 2006 Vancouver BC
>Canada. For more information, visit www.safe.com/2006uc.
>Yahoo! Groups Links
>
>
>
>
>
>
_________________________________________________________________
Del dine store filer uden problemer med MSN Messenger:
http://messenger.msn.dk
Join us at the FME Worldwide User Conference Sept. 21-22, 2006 Vancouver BC
Canada. For more information, visit www.safe.com/2006uc.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/fme/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
