Everything Else
Using Background Pictures

Using background graphics can turn a dull view into a lively one, and provide helpful visual clues to the users.

Performance Considerations

One drawback to background graphics is that performance can lag on a view with many background graphics. To increase the speed of a form with background graphics, combine graphics into grouped elements.

This background graphic appears as distinct graphics, but is actually a single graphic. The detail can be seen in the design of the help, phone and save buttons:

In the illustrated example, we could have created separate pictures for the logo, the buttons and the Field titles. Instead, we create one picture containing all the elements.

Place all the rectangles on top of this one background picture on the Template:

The resulting screen appears seamless and draws more quickly than if several separate background pictures were used:

Client/Server Addendum

In the case of Client/Server Helix, it is important to note that the Client structure does not retain elements that exceed 32K in size. If you create very large graphics for use in a Client/Server database, performance may actually suffer, as the large elements will be transferred from the Server to Client (where they are held in memory) each time they are required. You can avoid this in part by being sure to convert the graphic to PICT format and to use only the required bit depth.