Filemaker optimal layout size1/2/2024 Let's look at some examples of how to make the best use of card windows:Ī database is entirely useless without a way to retrieve the data stored within. Pound-for-pound, card windows beat out popovers when a dialog message is required to overlay the screen. It also lowers the learning curve for new users looking to make modern apps. This reduced complexity is key when prototyping or building apps quickly. Lastly, card windows require a lot less scripting and layout development than modal popovers (see 7-step process above!). It also keeps the app thinner, since less schema is required. This is the ideal way to ensure optimized performance is achieved. In contrast, popovers would need to be created on each layout they appear, requiring duplicate development work.Īnother huge advantage of a card window is it can display records from other tables, without the need for joins or portals. This means that the dialog screen can be set up in a single layout, and then referenced from any other screen in the app. The primary advantage is that the card window is completely independent layout from the original layout. So which is better? All other things being equal, card windows have a number of powerful advantages.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |