Can we call the graphic/figure in the XPP division from the division itself. I mean, I donot want to use the graphic configuration system where the graphics needs to be put in common folder and the same path needs to be defined in the configuration specs. Is there any way to skip that process and call the graphic directly from the XPP division itself.
The way graphics work is that the call out, whether that is a pickup or and ig/igt call out looks in the Job ticket and then looks for the image chase fields to see where to look for the image. What you can do is create an folder in the job called say, images, and then do that for every job - that way the images are kept with their jobs and you always have images in the job ticket for the image chase and only have to have one rule in the graphics config file where the entry would be ../images
And to add to what Chris already said, you can also set things up to have graphics looked up in the DIV folder as well (either directly or in a sub-folder).
In all cases, however, you do need an entry in the im_config (Graphics Configuration) spec to define the lookup.
Here in XPP R&D, we typically define im_config entries for "joblocal" with path ".." and "divlocal" with path ".".
As Chris suggested, a variation could also be "joblocal" with path "../images" and "divlocal" with path "./images" (with all those "library" and folder names your choice) - in which case you can have your job or division located images all organized into a sub-folder rather than having the image files mixed in with all the other job/division files.
Here is a screenshot on how the entry might look in your im_config spec:
(corrected my earlier screenshot to comply with Jonathan's remark)
(in fact went through my im config file and removed all trailing '/.' or '/')
Actually, Bart, it's better if the defined Library Path is not entered with the trailing "/." as you have it.
The defined Library Path's should just end in a folder name, whether that be ".", "..", or a name (e.g. "images").
I think it will work as you have it, but I think any messages you might get with full paths in them will look like CLS/GRP/JOB/images/./imagename or ../images/./imagename - and so the extra (or extraneous) "/." is just noise.
Jonathan,
Thanks for this.
I don't even know why I put the trailing '/.' there.
But I went through my im config file and removed all of them - had this at several places, especially the 'local' variants
Translate
