In message <Marcel-1.53-0626115135-064ZSTv@xxxxxxxxxx>, Anthony Hilton <ajh@xxxxxxxxxxxxxxxxx> writes
David Pilling - Is there any way to use a dummy path (even OvationPro$Dir)
when reading a DDL file with relative picture references so that the
{filepath} can be resolved when the file has been saved and is re-opened?
My first thought is that when a DDL file is loaded, things work as if a new document had been created - just like if you click on the icon bar icon. The point being that such a new document does not have a {filepath} - because it has never been saved.
One idea is that you set the RISC OS CSD in such a way that if {filepath} evaulates to the null string references work.
So:
{filepath}.^.sa00"}
would evaluate to
"".^.sa00
the CSD (set via F12 or a task window using the dir command) would have
to be one level below the file sa00 - e.g. create a temporary folder and
set the CSD to it.
Obviously you could edit the DDL, but that means losing the relative paths, although you could get them back again using the collect feature.
I think one of the original ideas was that these paths can contain macro expansions ({filepath} of course is an example) which can involve system variables.
So you could define a macro - call it myfilepath with a body of
{filepath}
when you want to use something other than filepath you just redefine the
macro body as
<MyPics$Dir> -- David Pilling email: david@xxxxxxxxxxxxxxxxxxx web: http://www.davidpilling.net post: David Pilling P.O. Box 22 Thornton Cleveleys Blackpool. FY5 1LR UK fax: +44(0)870-0520-941
