rtLib — Notes Rich Text Management Library Documentation of rtLib — Notes Rich Text Management Library Download rtLib — Notes Rich Text Management Library FAQ of rtLib — Notes Rich Text Management Library Purchase rtLib — Notes Rich Text Management Library Feedback about rtLib — Notes Rich Text Management Library

Handling of Rich Text objects

Hotspots and buttons

Start search Mail feedback Back to Description

rtHotspot is parent class of all specific hotspot types like rtPopup, rtButton, rtSection and rtHotLink. Action hotspots ( rtHotspot) or buttons ( rtButton) can run either simple action, formula, javascript or lotusscript.

Simple action and lotusscript hotspots' code can not be created or modified.

Any hotspot object that can not be resolved to particular subclass will be represented by generic rtHotspot object. Example is an embedded view. Use HotspotType property to identify the hotspot.

Buttons are represented by rtButton class. It has Formula and Javascript properties that can be modified (see class help) and Label ( rtLabel) to manipulate button text.

Prior to Domino release 5.0.8 code in hotspots could not be signed programmatically. As a result it was possible to use within buttons only some neutral code that does not write fields and documents (or alternative being the enabling of "No Signature" ECL setting that was not a good choice from security point of view).

As default rtLib attempts to keep the existing signatures, but in case the code gets edited or created anew, it signs the code when running on 5.0.8 or greater. For earlier releases it removes the signature for edited hotspots. The default behaviour can be overriden using Sign method.

New in version 1.1 is rtActiveObject class that handles Java Appplets. This class also inherits from rtHotspot.

Area hotspots on images are handled by rtMap (representing a collection of links and hotspots for particular image) and rtHotLink class.