[Fm-lisp] Exif_Get and calculated container fields

[Jens Teich]

Hi!

Am 05.08.14 09:29, schrieb James Wilson:
> Jens
>
> This is great!
>
>
> A couple of observations:
>
> The functions (on my mac!) both have an extra "Exif_" in front of the
> function name

This is intended. The first four letters are treated special by 
FileMaker. It is the FileMaker PlugIn ID.

> Exif_Get_Exif_Reference
>
> and
>
> Exif_Get_Exif_from_File
>
>
>
> For Exif_Get_Exif_Reference I can get partial results:
>
> 1.  in certain cases the full  jpeg_reference works, ie
>
> imagemac:/Macintosh HD/Users/me/Desktop/my folder/DSC01950.JPG
>
> works fine.
>
> But I am stumped by the fact that a longer pathname doesn't seem to work
>
> imagemac:/Macintosh HD/Users/me/Dropbox/Base de Dados/GPS Data/26 07/GPS
> 3/DSC01950.JPG

Is this a real local path or is there some magic with dropbox going on? 
I tested a longer path on my mac (with blanks) and it works.

Regards
Jens

> does not work. I am sure this path is correct as its the very same that
> is used in a calculated container field, and the image is visible in the
> record.
>
>
>
> 2. There seems to be a similar issue with Exif_Get_Exif_from_File.
>
> The unix path
>
> /Users/me/Desktop/my folder/DSC01950.JPG
>
> works fine,
>
> but the same file in a different location does not return Exif data.
>   The path
>
> /Users/me/Dropbox/Base de Dados/GPS Data/26 07/GPS 3/DSC01950.JPG
>
> does not work. I have checked permissions and have Read & Write
> privileges over the file in both locations
>
>
>
> Best regards
>
> James
> (message not copied to list, if this a bug I would guess that you would
> prefer to post a solution, rather than for me to post a problem)
>
>
>
> On 4 Aug 2014, at 19:08, Jens Teich <info at jensteich.de
> <mailto:info at jensteich.de>> wrote:
>
>> Am 04.08.14 09:54, schrieb James Wilson:
>>> Hi
>>>
>>> When the images are inserted into a database via a conventional
>>> container field, the Exif_Get plugin works just fine.  However it
>>> doesn't appear to work when the container field is a calculated
>>> field, accessing images that are resident outside of the database.
>>>  Is this possible in some way, or a limitation of the plugin?
>>>
>>>
>>> My apologies if this topic has been discussed here before, but the
>>> archive link from the webpage is not working
>>
>> Hi,
>>
>> this was indeed a limitation. But I made a new version (for Mac)
>> today: 0.3.0. It has the ability to extract Exif data also from
>> container fields with images stored as reference.
>>
>> External jpg files are also accessible.
>>
>> Win version, improved example file and documentation are following soon.
>>
>> The link is:
>> http://jensteich.de/wp-content/exif-plugin/ExifPlugIn-0.3.0.Mac.zip.
>>
>> There are two new functions:
>>
>> Get_Exif_Reference( jpeg_reference ; tag )
>>
>> which wants a FileMaker container field with jpg images stored as
>> reference as first parameter and the exif tag as second.
>>
>>
>> Get_Exif_from_File( unix_path ; tag )
>>
>> this function expects a unix path as first parameter:
>> '/Users/me/Desktop/myfunnypic.jpg'
>>
>> ~Jens
>>
>