8 Replies Latest reply on Mar 28, 2009 1:58 PM by raybaudi

    data:image/gif;base64 on windows

    raybaudi

      Title

      data:image/gif;base64 on windows

      Post

      Hi all friends

       

      I found that, due to the inability of IE to work with base64 code, FileMaker decodes it and places a really .gif file into the Temporary Folder with a name like: FMTEMPFM49c7d8220005.gif.

       

      The exact path and name can be viewed right-clicking into the WebViewer ( Properties ), so one can assume that the "source" is that... but NO, GetLayoutObjectAttribute ( "WV" ; "source" ) returns the base64 code.

       

      How can  get the name of the .gif file ( other that manually ) ?

        • 1. Re: data:image/gif;base64 on windows
          TSGal

          raybaudi:

           

          Thank you taking the time to report this problem.  Unfortunately, I do not have a 64-bit machine to work with here, so I cannot try to duplicate the problem.  However, I have forwarded your entire post to our Development and Software Quality Assurance (Testing) departments for review.  If I receive any information, I will let you know.

           

          TSGal

          FileMaker, Inc. 

          • 2. Re: data:image/gif;base64 on windows
            raybaudi
              

            Thank you TSGal.

             

            Out of curiousity, really don't you have a pc ?

            • 3. Re: data:image/gif;base64 on windows
              TSGal

              Daniele:

               

              Yes, I do have a PC running XP.

               

              I just received some additional information from our Testing team...

               

              ============

               

              If I am correct, the user is trying to get the name of the GIF image from the web viewer's code.  We need more information to understand this bug better.

              1) What is the full URL in the Web Viewer.

              2) A test file would be helpful.

               

              I believe that base64 as referenced by the customer refers to how the URL is represented, not the processor.  He might need to parse the URL to get the code, but a temp file name is not predictable, and the name and its length will change.

               

              It is hard to answer this question, for it is not clear.  I am guessing what the customer wants.

               

              ============

               

              So, yes... I was assuming base64 had to do with the processor.

               

              If you have a test file, we would like to see it.  I have sent you a private message with instructions where to send the file.

               

              TSGal

              FileMaker, Inc. 

              • 4. Re: data:image/gif;base64 on windows
                raybaudi
                  

                TSGal wrote:

                 

                If you have a test file, we would like to see it.  I have sent you a private message with instructions where to send the file.

                 

                TSGal

                FileMaker, Inc. 


                At this time I have still no PM.

                 

                And yes, I have an example file to send you.

                 

                BTW: I'm clearly speaking of the Web Viewer. FileMaker Inc. made a good job when he made the FMP9: due to the fact that Internet Explorer can't manage data coded in base64, he creates a DECODED file and puts it into the Temp folder.

                 

                It is very easy to try:

                 

                1) create an empty DB
                2) in layout mode drag an object Web Viewer ( with 'Allow interaction...' checked )  and insert this as the url:
                "data:image/gif;base64,R0lGODlhFwAMAKEAAL+/v///AAAAUwAAACH5BAEAAAAALAAAAAAXAAwAAAI7hBGHapHcXJKPumizpigI+QliSH0XIjokWJ6oB4+qt0Zmaqpjesxz7st1YD8ZEbhJajAuDgfSYTx60wIAOw=="

                3) the WV will show a jellow point with the text: New
                4) If you now right-click into the WV and see: properties, you'll know the DECODED name of the file and its path.
                5) this fact lets me think that NOW the 'source' isn't more the one I inserted into the Web Viewer
                6) but an unstored calc field with calc: GetLayoutObjectAttribute ( "wv" ; "source" ) still gives me the base64 code

                 

                So, the question is: there is a way to know the name of the DECODED file that FileMaker creates ?



                • 5. Re: data:image/gif;base64 on windows
                  TSGal

                  raybaudi:

                   

                  Sorry for the delay, but the private message finally went through, and I did receive your file and explanation.  I see what you are talking about, and I have forwarded the information back to the tester.  When I receive more information, I will let you know.

                   

                  TSGal

                  FileMaker, Inc. 

                  • 6. Re: data:image/gif;base64 on windows
                    TSGal

                    raybaudi:

                     

                    Here is the information from the Developers...

                     

                    > Is there a way to know the name of the DECODED file that FileMaker creates?

                     

                    No, not currently.  The temporary file is just that... TEMPORARY.  It is not meant to be used in a solution.  It is a workaround due to the limitations of Microsoft Internet Explorer.  As a result, it could easily change or disappear.

                     

                    =============

                     

                    TSGal

                    FileMaker, Inc. 

                    • 7. Re: data:image/gif;base64 on windows
                      raybaudi
                        

                      TSGal:

                       

                      Many thanks to you and to Developers

                      • 8. Re: data:image/gif;base64 on windows
                        raybaudi
                          

                        raybaudi wrote:

                         

                        ... due to the inability of IE to work with base64 code...


                        I'm back on this post just to say that what I said isn't more the true.

                         

                        The last version ( 8 ) of Internet Explorer finally can handle base64 code. ;)