In response to the user action an applet can change the provided graphic content.

Any user action with the editor can generate a request.

The second component, sometimes called latency, is time required for an application to respond to a user action.

Animations can be triggered by external events, including user action.

The exact technique involved depends on the game itself; however, most games follow a certain pattern of user actions.

The most effective methods in typical use are those that do not depend upon regular user action.

It allows to combine user actions with events at run time.

It's regarded as not requiring any specific user action.

However, some impressions may not be counted, such as a reload or internal user action.

The suggestions and user actions are stored in a large database.