or the FDK.
Rick Quatro
Carmen Publishing
585-659-8267
www.frameexpert.com
- Original Message - From: O'CONNOR Mark
[EMAIL PROTECTED]
To: Rick Quatro [EMAIL PROTECTED]
Sent: Thursday, May 24, 2007 11:19 AM
Subject: RE: Help decoding Running H/F variables with attibutes
Hi Rick,
The format
At 10:28 -0400 24/5/07, Rick Quatro wrote:
I am trying to figure out how attribute-based Running H/F variables work. Here
is are examples of a couple in a document I have:
$attribute[Booktitle:book]
$attribute[Revision:book]
I assume that the first is looking for the value of the Booktitle
: Thursday, May 24, 2007 11:19 AM
Subject: RE: Help decoding Running H/F variables with attibutes
Hi Rick,
The format is [attribute name:element name]. If you don't specify the
element name, the first occurrence of the attribute on the page will be
used (blank if there are no occurrences). If you
As I understand what you are stating, each book
component will store the value of the book file title
attribute value which existed the last time the
generate/update action was taken on the book file.
Thus, if the value of the attribute in the book file
is changed but the generate/update action is
At 10:28 -0400 24/5/07, Rick Quatro wrote:
>I am trying to figure out how attribute-based Running H/F variables work. Here
>is are examples of a couple in a document I have:
>
><$attribute[Booktitle:book]>
><$attribute[Revision:book]>
>
>I assume that the first is looking for the value of the
> At 10:28 -0400 24/5/07, Rick Quatro wrote:
> >I am trying to figure out how attribute-based
> Running H/F variables work. Here is are examples of
> a couple in a document I have:
> >
> ><$attribute[Booktitle:book]>
> ><$attribute[Revision:book]>
=
I may be missing
ot;Rick Quatro"
Sent: Thursday, May 24, 2007 11:19 AM
Subject: RE: Help decoding Running H/F variables with attibutes
Hi Rick,
The format is [attribute name:element name]. If you don't specify the
element name, the first occurrence of the attribute on the page will be
used (blank if there ar
As I understand what you are stating, each book
component will store the value of the book file title
attribute value which existed the last time the
generate/update action was taken on the book file.
Thus, if the value of the attribute in the book file
is changed but the generate/update action is
Hello All,
I am trying to figure out how attribute-based Running H/F variables work.
Here is are examples of a couple in a document I have:
$attribute[Booktitle:book]
$attribute[Revision:book]
I assume that the first is looking for the value of the Booktitle attribute
on the book element,
Hello All,
I am trying to figure out how attribute-based Running H/F variables work.
Here is are examples of a couple in a document I have:
<$attribute[Booktitle:book]>
<$attribute[Revision:book]>
I assume that the first is looking for the value of the Booktitle attribute
on the book element,
10 matches
Mail list logo
