What are actions? Actions are the way in which you can add DHTML and
interactivity to your site. Actions consist of a trigger event, a message and a target. The trigger event is what happens or what
you do in order to begin your action or chain of actions. The message is the action instructions themselves: what is going to happen when the trigger event occurs. The target is the object to which the message is sent.
Sometimes the trigger event is placed on the target, but it can be anything from a mouse click or a page load, to another action completing elsewhere on the page. All actions are created through the use of the CSS and
Layers specifications in HTML 4.0 and JavaScript or Jscript. You can also create your own actions in other scripting languages if you desire. For an overview of Actions and how to apply them, see the NetObjects Fusion
User Guide, Chapter 21. For a list of all the Actions available in the actions menus see our Actions Reference Guide at: http://www.netobjects.com/support/usagenotes/unnof3
Another good source of help is our actions newsgroupsFor tips and tricks on actions visit the Workbench at: http://www.netobjects.com/workbench/actions/index.html Is there a list of what all the actions do? We have compiled a list of all the actions
available in the actions menus, when they can be triggered and what they do in our Actions Reference Guide. This is available at http://www.netobjects.com/support/usagenotes/unnof3 Why don't my actions work in Netscape 4.05? The 4.05 release of Netscape contains a known bug which
prevents many JavaScripts from executing locally on your machine. This means that many Actions, which use a combination of HTML 4.0 and JavaScript, will not work when the site is Previewed or Published locally. If the
site is Published to a web server, most Actions should function normally. Why do my actions keep repeating forever in a loop?
This is usually due to a logical error in the way the actions have been set up. Actions cannot distinguish the order in which they appear in the Actions
list for an object. Actions are triggered instead by specific messages. For example, if you have more than one fly-in action and one is set to fly-in when a fly-in action is completed, the second action repeats again
and again. In order to solve this type of problem, you must make sure that each action is unique in some way; either it is the only action of its kind in the page, or it sends a custom message which another action can
use as a trigger. For more information on how to set up custom messages, see the examples section of our User Guide, Chapter 21, Building Dynamic Pages. Another good source of help is our actions newsgroup at For tips and tricks on actions visit the Workbench
|
