3 Replies Latest reply on Jul 21, 2014 8:44 AM by DanielShanahan

    Custom Theme


      I want to create my own theme so looked up how to do so. Seemed easy enough (made the format changes and saved the layout), but when I tried to save the theme, the inspector options for doing this were not available (ie grey). Like this.



      Then eventually (after leaving the layout and coming back after a while) I was able to save it as a new theme and give it a name. But when I went to apply it, I was unable to find it in the list of themes.


      I let it go and decided to simply use the classic theme and then modify the formatting of the field manually as I have done in the past with other themes. I was able to change fonts and size but CAN'T get the field to display borders in Preview. I do see the borders in BROWSE. Other objects such as rectangles accept any format I want but fields will not display the fill colour or line size.


      Then it occured to me that perhaps one cannot use "classic" as a starting point upon which to build a new theme, perhaps has something to do with using it in WD. So I used the GREEN theme as a starting point, and was able to achieve what I want but now the blasted inspector options are not available again to save those formats as a new theme!


      Any takers?


      PS I have quit FM and relaunched the app; hopefull not corruption.

        • 1. Re: Custom Theme

          The order of proceedings needs to be to change styles, then save changes to theme. If there are no style changes on the layout then there is no need to save any change to the theme, as there are none. Equally, if you have made changes to one or more objects (field, text, button, label, layout part, tab panel, etc) BUT HAVE NOT SAVED THE CHANGES either as new styles or as changes to the default, then the Theme options will be greyed out. The layout will happily deal with this forever, but will warn you if you try to switch to a new theme when there are unsaved changes to the existing one.

          And yes, you are right I beleive, Classic behaves somewhat differently from other themes—it is a sort of non-theme—and is best not used as a starting point for a custom theme.

          • 2. Re: Custom Theme

            Adding to keywords note about Classic, there are a few bugs that occur on Classic exclusively, so I tend to stray from it, even if moving to a custom theme. As keywords says, it is best to start with one of the other default themes.

            • 3. Re: Custom Theme

              Also, when you change a style, then the theme, I have found it best to do this regularly.  That is, every time you make a style, save it and then save the theme.  You can make changes to style in a batch, but don't leave without changing it. 


              For example, you can change a field's font, size, field, and padding at one time, but don't leave that field without changing or updating that theme (red inverted triangle) and then immediately save the changes to the theme.


              Otherwise, if you leave that field without making changes, there is no UI indicator that you have an unsaved style until/unless you select that object again.