diff options
Diffstat (limited to 'doc/GetPixels.3')
| -rw-r--r-- | doc/GetPixels.3 | 18 |
1 files changed, 3 insertions, 15 deletions
diff --git a/doc/GetPixels.3 b/doc/GetPixels.3 index a89c8d1..814c4eb 100644 --- a/doc/GetPixels.3 +++ b/doc/GetPixels.3 @@ -14,18 +14,14 @@ Tk_GetPixelsFromObj, Tk_GetPixels, Tk_GetMMFromObj, Tk_GetScreenMM \- translate .nf \fB#include <tk.h>\fR .sp -.VS 8.1 int \fBTk_GetPixelsFromObj(\fIinterp, tkwin, objPtr, intPtr\fB)\fR -.VE .sp int \fBTk_GetPixels(\fIinterp, tkwin, string, intPtr\fB)\fR .sp -.VS 8.1 int \fBTk_GetMMFromObj(\fIinterp, tkwin, objPtr, doublePtr\fB)\fR -.VE .sp int \fBTk_GetScreenMM(\fIinterp, tkwin, string, doublePtr\fB)\fR @@ -36,14 +32,12 @@ Interpreter to use for error reporting. .AP Tk_Window tkwin in Window whose screen geometry determines the conversion between absolute units and pixels. -.VS 8.1 br .AP Tcl_Obj *objPtr in/out String value specifies a distance on the screen; internal rep will be modified to cache converted distance. -.AP "CONST char" *string in +.AP "const char" *string in Same as \fIobjPtr\fR except specification of distance is passed as a string. -.VE .AP int *intPtr out Pointer to location in which to store converted distance in pixels. .AP double *doublePtr out @@ -53,14 +47,10 @@ Pointer to location in which to store converted distance in millimeters. .SH DESCRIPTION .PP These procedures take as argument a specification of distance on -.VS 8.1 the screen (\fIobjPtr\fR or \fIstring\fR) and compute the -.VE corresponding distance either in integer pixels or floating-point millimeters. In either case, -.VS 8.1 \fIobjPtr\fR or \fIstring\fR -.VE specifies a screen distance as a floating-point number followed by one of the following characters that indicates units: @@ -81,14 +71,13 @@ The number specifies a distance in millimeters on the screen. The number specifies a distance in printer's points (1/72 inch) on the screen. .PP -.VS 8.1 \fBTk_GetPixelsFromObj\fR converts the value of \fIobjPtr\fR to the nearest even number of pixels and stores that value at \fI*intPtr\fR. It returns \fBTCL_OK\fR under normal circumstances. If an error occurs (e.g. \fIobjPtr\fR contains a number followed -by a character that isn't one of the ones above) then +by a character that is not one of the ones above) then \fBTCL_ERROR\fR is returned and an error message is left -in \fIinterp\fR's result if \fIinterp\fR isn't NULL. +in \fIinterp\fR's result if \fIinterp\fR is not NULL. \fBTk_GetPixelsFromObj\fR caches information about the return value in \fIobjPtr\fR, which speeds up future calls to \fBTk_GetPixelsFromObj\fR with the same \fIobjPtr\fR. @@ -103,7 +92,6 @@ return value, so \fBTk_GetAnchor\fR is less efficient than \fBTk_GetPixelsFromObj\fR and \fBTk_GetPixels\fR (respectively) except that they convert the screen distance to millimeters and store a double-precision floating-point result at \fI*doublePtr\fR. -.VE .SH KEYWORDS centimeters, convert, inches, millimeters, pixels, points, screen units |