#BASEELEMENTS THEMES FILEMAKER PDF#
#BASEELEMENTS THEMES FILEMAKER UPGRADE#

I also was able to locate the 'Prefs Icon' Style I had previously used and as you can see, it's now used on 0 objects.

It turns out that I had a whole Theme ( Enlightened ) that was still there and not being used, and a bunch of other Styles that weren't used. Your solution has 365 Styles in total and fully 238 of them are no longer being used. Run a DDR of the solution, and import into BaseElements and what does it tell you ? What other Styles might I not be using?.Is this Prefs Style used somewhere else as well that I'm not aware of?.Did I change them all, or did I accidentally skip a layout or mis some?.So why would I use BaseElements to help here? There's a lot of layouts in BE, but it's easy enough to do. So I needed to go through and select the Prefs icon, and choose the correct Style. Which wasn't good, I wanted them to be the same, and for any future changes to be picked up in both Objects. So the icon on the right had slightly different highlights to the icon on the left. I was developing in BaseElements and realised I had a different Style for the preferences icon, vs other icons in the toolbar : But like lots of things in FileMaker, it's easy to accumulate Styles that are no longer in use. We use a recent feature in FileMaker to have a dynamic file path, and calculate the path to the prefs folder on startup.Styles in FileMaker are a huge timesaver for making adjustments to a whole solution worth of items in one go. We do this by keeping the ClipManager file in the preferences folder, instead of alongside the three main BaseElements files.

#BASEELEMENTS THEMES FILEMAKER UPGRADE#

Where are the clips stored?Īnything you put in the ClipManager is kept even if you upgrade to a new version of BaseElements. Just remember to set the Type field on the top right if you want to copy them in FileMaker format. Cool thanks - I was looking at using the python ctypes to call the dll so that may be the ticket. You can create your own Clips and store in them whatever you want. Make a VB script or some other app that can do what you want with the DLL’s, the call the app via to the Filemaker script step Send event You can write out data or parameters to a text file and have your VP suck them up to work on. Especially useful for things like script steps or Custom Functions. If all the items are of the same type, you can then copy multiple items and paste them at once back into FileMaker. You can select multiple items by shift clicking in the portal on the left. The Copy icon will copy the currently selected to the clipboard using the FileMaker internal type, so they can be copied back into a FileMaker solution. The Delete icon will delete the current record.

The Find ( magnifying glass ) icon in the toolbar brings up the FileMaker Find and Replace dialog, so you can replace some text in the local field, or even across all the records.

#BASEELEMENTS THEMES FILEMAKER PDF#

I've pasted an object, some Scripts and some Custom Functions, and currently there is an Object selected, which also shows the PDF representation of the object at the time it was copied.įrom here you can do all the usual things you can do with a FileMaker text field. What does Clip Manager look like?īelow is an example of what you can put into Clip Manager in BaseElements 17. If you're working in another file, BaseElements could be purely a Clip Manager storage location for you. You don't even need to have a DDR from that solution in BE. If the cursor is not in a field, it will create a new record with your copied object as XML. There's nothing to it really, open Clip Manager by clicking it's icon, and then just hit Paste ( CMD-v / Ctrl-v ). How do I get to Clip Manager?Īny time you want to open the Clip Manager, just click the icon in the toolbar. The best thing about the Clip Manager is that your clips are kept in a separate FileMaker file in your Preferences folder, so you can upgrade to new versions of BE or switch copies, or move from local to server and the clips you've previously used are retained. BaseElements version 17 introduces a new Clip Manager function to allow you to store copied FileMaker data inside BaseElements for future use.įor example, if you're working in a solution and need a script or a set of script steps that you're going to repeat a few times, you can paste them into BE and then copy them back out at any time.

Baseelements themes filemaker