Minimize Flashing in WebDirect: do as little as possible

Since layout redraw is one of the slowest things a WebDirect (WD)  layout can do, you’ll want to do whatever you can to minimize those redraws (which can appear your users as flashing or as a spinning busy icons).

upload-1So, “do as little as possible”. This often means wrapping your commands in If() statements to see if they’re necessary. We don’t need to do this in Pro because we don’t notice things like “Revert Record” if they’re not needed. But in Web Direct, you really see Revert Record even if there is no record to revert.

Interestingly, “Commit Record” doesn’t cause a layout redraw when called unnecessarily.

We’ve also had great results using RefreshObject instead of RefreshWindow when we need a particular part of a layout to redraw. Refresh window is often substantially slower, to the point that never use it in WD. (You can gather the objects you want to refresh into refresh enclosures to make this simpler.)

Most of our thoughts on Web Direct are coming from porting our Pro Calendar to WebDirect. We’re also doing this for SeedCode Complete (!) so stay tuned.

Featured Posts

Follow Along

Stay up to date with the latest news & examples from SeedCode

Leave a Reply

Your email address will not be published. Required fields are marked *

Check out some of our other posts ...

FileMaker Summer Camp – Recap

Unconference Sessions If you missed Pause in October, here’s a look at the sessions that attendees hosted. All the sessions are listed in this post

Subscribe to DayBack Updates & Status

Subscribe to DayBack’s latest features and example code at our new site: You’ll find new features and documentation, as well as the status and

DayBack Calendar in Claris Pro

DayBack for FileMaker 19 works great in Claris Pro with no changes required. The older DayBack Classic also works in Claris Pro, but requires a few changes.



Stay up to date with the latest news & examples from SeedCode

© 2023 SeedCode, Inc.