2 Replies Latest reply on Jun 17, 2014 10:24 AM by TSGal

    THEMES : Copying and pasting themes does not work as one expects

      Summary

      THEMES : Copying and pasting themes does not work as one expects

      Product

      FileMaker Pro

      Version

      13

      Operating system version

      Win/Mac

      Description of the issue

      Copy & pasting themes works extremely differently to copy & pasting all other FileMaker object types.

      Here is a summary of the perceived differences:

      FM-objects:     Importing or copying and pasting FileMaker objects (Tables, Scripts, Custom Functions) produce the same result - it DOESN'T MATTER which you use.
      FM-themes:      It DOES MATTER which you use: Whereas Importing a theme produces an identical, updatable theme copying and pasting produces a non-updatable THEME IMPOSTOR

      FM-objects:     Copying and pasting matches all referenced objects BY NAME
      FM-themes:      Copying and pasting matches all referenced objects BY INTERNAL NAME (=> leads to IMPOSTORS)

      FM-objects:     You can visually check all references before you paste, to make sure it will work.
      FM-themes:      You CAN'T visually check all references before you paste, to make sure it will work, (BECAUSE the internal names are invisible - and because you cannot see which styles a theme contains).

      FM-objects:     You CAN copy and paste the contents of objects in order to update them (e.g. you can update a script by pasting new script steps into it; ditto tables + fields ).
      FM-themes:      You CAN'T copy and paste styles in order to update a theme. (You can only paste layout objects - and should you

      FM-objects:     You CAN'T update an object by re-importing/pasting the same object into FileMaker - You HAVE TO paste its CONTENTS.
      FM-themes:      You CAN UPDATE a them by re-importing (but not pasting) the same object into FileMaker - You CANNOT paste its CONTENTS.

      FM-objects:     You CAN rename objects without breaking references-by-id to them. (Ref-by-name of course breaks, but NOT Ref-by-id)
      FM-themes:      You CAN'T rename themes without breaking reference-by-id to them - After renaming update is no longer possible - EVER AGAIN.

      FM-objects:     You CANNOT copy and paste objects between languages without breaking them.
      FM-themes:      You CAN copy and paste themes between languages without breaking them.

      @TSGal: please treat all these entries about themes & styles as a single packet and pass on to development. It may not be a single bug, but it is all relevant to the big picture, thank you.

      Russell Watson

      Steps to reproduce the problem

      Copy and paste themes between files; copy and paste other objects between files, compare the differences in behavior (see description)

      Expected result

      I expect the theme clipboard to work (pretty much) like any other FileMaker object clipboard (see description)

      Actual result

      It works very differently (see description)

      Exact text of any error message(s) that appear

      -

      Configuration information

      -

      Workaround

      -

        • 1. Re: THEMES : Copying and pasting themes does not work as one expects
          TSGal

               MrWatson:

               I have sent all seven differences to our Development and Testing departments for review.  When I receive any feedback, I will let you know.

               TSGal
               FileMaker, Inc.

          • 2. Re: THEMES : Copying and pasting themes does not work as one expects
            TSGal

                 MrWatson:

                 Here is some feedback from Testing and Development.

                 1. For Tables, Scripts, Custom Functions, FileMaker Pro does not need to have a unique ID, so no impact on pasting.  Themes do have an internal ID and they are required to be unique. Importing theme won’t change the internal ID but copy pasting will.  This is by design.

                 2. Same reason above.

                 3. The Theme ID is not available, but you can always see what a theme contains by checking the Style tab in the Inspector.

                 4. You CAN copy and paste the contents of objects in order to update them (e.g. you can update a script by pasting new script steps into it; ditto tables + fields ).  You can copy steps inside a script and paste it to another script but you cannot copy a whole script and replace another one.  You CAN'T copy and paste styles in order to update a theme.  You can only paste layout objects.  You cannot copy/paste style definition to  another Theme, but you can copy an object applied with that style to a layout using another theme and save the style to that theme.

                 5. This is exactly opposite to #4.  By design.

                 6. If a field name or script name is changed, the reference in another place won't be affected and the reference is still there.  It's the same with Themes.  Multiple layouts will still use that theme after you rename the theme.  For importing, because the theme ID is changed due to the renaming, it's a different theme to the other file.

                 7. Testing and Development are able to copy objects between files in different languages.  Can you describe "breaking"?  Or, do you have an example of what is occurring?

                 TSGal
                 FileMaker, Inc.