Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

strokeinstall(3) [redhat man page]

StrokeInstall(3)					     Library Functions Manual						  StrokeInstall(3)

NAME
StrokeInstall - Enable Strokes in a Widget SYNOPSIS
#include <Stroke.h> void StrokeInstall(Widget W); void StrokeRemove(Widget W); void StrokeSetButton(Widget W, int button); int StrokeGetButton(Widget W); void StrokeSetDebug(Widget W, Boolean Debug); Boolean StrokeGetDebug(Widget W); void StrokeSetMapping(Widget W, String Map); String StrokeGetMapping(Widget W); DESCRIPTION
Enable Strokes to be recognized in the given widget. It first retrieves the resources and installs an Xt event for button press, release and, motion on the given widget and all of its children. Therefore this function should not be called until all of the widgets children have been added. Resources Resources are specified as if they belong to the widget that the strokes are enabled in. strokes: stroke action [[,stroke action]...] This provides a mapping of strokes to actions. By default the action `Stroke-456' is called for stroke `456'. strokeSlop: int This is used to define a buffer zone between the boxes of the grid. The amount of slop tolerated is actually the resulting box dimension divided by this slop number. Therefore the larger the slop number the more accurate your strokes must be. A value approaching 3 will make it all but impossible to recognize a stroke. The default value is currently 20. Run the stroke(1) program with StrokeDebug turned on to show what this means. strokeDebug: True | False Turns on `stroke debug mode'. In this mode the strokes are not erased from the screen when the button is released and a grid is drawn around the stroke. Try the stroke(1) program to see what I mean. strokeButton: 1 | 2 | 3 | 4 | 5 Specifies the button to be used to draw strokes. By default Btn3 is used. strokeSound: sound file If given, the contents of this resource will be provided as an argument to the `PlaySound' action at the conclusion of the stroke. If the PlaySound action is not defined in your application do not specify this resource. Specifically the following call is made: XtCallActionProc(W, "PlaySound", NULL, "sound file", 1); AUTHOR
Rick Scott <rwscott@alumni.uwaterloo.ca> Check out LessTif at http://www.LessTif.org SEE ALSO
stroke(1) StrokeInstall(3) StrokeRemove(3) StrokeSetButton(3) StrokeGetButton(3) StrokeSetDebug(3) StrokeGetDebug(3) StrokeSetMapping(3) StrokeGetMapping(3) StrokeInstall(3)

Check Out this Related Man Page

XtClass(3)							   XT FUNCTIONS 							XtClass(3)

NAME
XtClass, XtSuperclass, XtIsSubclass, XtCheckSubclass, XtIsObject, XtIsRectObj, XtIsWidget, XtIsComposite, XtIsConstraint, XtIsShell, XtIs- OverrideShell, XtIsWMShell, XtIsVendorShell, XtIsTransientShell, XtIsTopLevelShell, XtIsApplicationShell, XtIsSessionShell - obtain and verify a widget's class SYNTAX
WidgetClass XtClass(Widget w); WidgetClass XtSuperclass(Widget w); Boolean XtIsSubclass(Widget w, WidgetClass widget_class); void XtCheckSubclass(Widget widget, WidgetClass widget_class, String message); Boolean XtIsObject(Widget w); Boolean XtIsRectObj(Widget w); Boolean XtIsWidget(Widget w); Boolean XtIsComposite(Widget w); Boolean XtIsConstraint(Widget w, Boolean XtIsShell(Widget w); Boolean XtIsOverrideShell(Widget w); Boolean XtIsWMShell(Widget w); Boolean XtIsVendorShell(Widget w); Boolean XtIsTransientShell(Widget w); Boolean XtIsTopLevelShell(Widget w); Boolean XtIsApplicationShell(Widget w); Boolean XtIsSessionShell(Widget w); ARGUMENTS
w Specifies the widget. widget_class Specifies the widget class. message Specifies the message that is to be used. DESCRIPTION
The XtClass function returns a pointer to the widget's class structure. The XtSuperclass function returns a pointer to the widget's superclass class structure. The XtIsSubclass function returns True if the class of the specified widget is equal to or is a subclass of the specified class. The wid- get's class can be any number of subclasses down the chain and need not be an immediate subclass of the specified class. Composite widgets that need to restrict the class of the items they contain can use XtIsSubclass to find out if a widget belongs to the desired class of objects. The XtCheckSubclass macro determines if the class of the specified widget is equal to or is a subclass of the specified widget class. The widget can be any number of subclasses down the chain and need not be an immediate subclass of the specified widget class. If the speci- fied widget is not a subclass, XtCheckSubclass constructs an error message from the supplied message, the widget's actual class, and the expected class and calls XtErrorMsg. XtCheckSubclass should be used at the entry point of exported routines to ensure that the client has passed in a valid widget class for the exported operation. XtCheckSubclass is only executed when the widget has been compiled with the compiler symbol DEBUG defined; otherwise, it is defined as the empty string and generates no code. To test if a given widget belongs to a subclass of an Intrinsics-defined class, the Intrinsics defines macros or functions equivalent to XtIsSubclass for each of the built-in classes. These procedures are XtIsObject, XtIsRectObj, XtIsWidget, XtIsComposite, XtIsConstraint, XtIsShell, XtIsOverrideShell, XtIsWMShell, XtIsVendorShell, XtIsTransientShell, XtIsTopLevelShell, XtIsApplicationShell, and XtIsSession- Shell. The SEE ALSO
XtAppErrorMsg(3), XtDisplay(3) X Toolkit Intrinsics - C Language Interface Xlib - C Language X Interface X Version 11 libXt 1.1.3 XtClass(3)
Man Page