[softwarelist] Re: OPW - referencing pictures

On Mon, 01 Dec 2008 18:17:03 -0000, David Pilling <flist@xxxxxxxxxxxxxxxxxxx> wrote:
In message <op.ulhl74ij7kyep4@xxxxxxxxxxxxxxx>, Clive Bonsall <cbonsall@xxxxxxx> writes
No ... after dropping the picture into the frame, I opened the reference picture window. But the path writable icon was blank, i.e. nothing to reference. 

The process is:

hold down ctrl+shift, drop picture into frame
window appears with reference and proxy buttons - (and important) displaying the path to the file
you tick "reference", click OK and the picture is then loaded and should become visible. 

That's all useful information. I can see the benefits of doing it that way.
If when you select reference from the picture menu the path icon in the resulting window is blank I would think the picture was not referenced. Clicking on the button to the right of the path will let you navigate on disc to a graphic file, having "opened" it, you can then click on the "Reference" button.
The point I'm labouring is that this is the way to set up the path if there is something wrong.
You can select reference from the picture menu on any selected picture frame, navigate to a graphic file, then click on Reference Picture and the graphic should load (replacing the picture previously in the frame). 

Good to know for future reference.
On a couple of occasions when the same thing has happened, I have tried to save the file as DDL thinking it would resolve any problems in the file itself.
It would be interesting to have a look at the DDL because the path to the referenced graphic should be easily visible within it.
However, trying to open the DDL with OPW resulted in an error message along the lines of "cannot open a file that has not been saved ... [something about] document path" (sorry can't remember the wording exactly).
On other occasions, a path has appeared in the writable icon, but clicking <collect referenced pictures> has created a Pictures directory that was empty. 

I'm inclined to think there is something about the path.
Earlier on today I wondered if it might be something like a maximum size of path somewhere - going back to RISC OS one often limited paths to 256 characters. Windows is full of maximum sizes of paths but they're bigger than 256 characters.
However it may be something else, perhaps odd characters in the path, sometimes mixing / and \ upsets things, or just some oddity in the paths to the destination device. 

OK, here's an example path from the DDL ...

PICTURE_805={picture
{reference "F:\\1 FAT32\\My Documents\\OPWdocs\\IGconference\\All_Final\\09_Dimitrijevic\\Pictures\\Fig01.tif"} 
}
As far as I can see, this is correct. But OPW couldn't recogize the picture at that location. Correct me if I'm wrong, but once I'd collected the referenced pictures, shouldn't the path have become(?): 

{reference "{filedir}\\Pictures\\Fig01.tif"}
If so, then for some reason the pictures in certain documents haven't been collectively referenced ... it's not clear to me why "collecting" references worked with some documents and not others. I may not have been using the methods you describe, but I was using the same method for every document.
Anyway, I've now gone thru' the problem documents following your advice, and as far as I can see the pictures are referenced and collected. 
--
C.B.
To unsubscribe or subscribe goto: http://www.freelists.org/list/davidpilling

Other related posts: