Initial commit of OpenSPARC T2 design and verification files.

[OpenSPARC-T2-DV] / tools / perl-5.8.0 / man / man3 / Tk::place.3

.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sh \" Subsection heading
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  | will give a
.\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
.\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.tr \(*W-|\(bv\*(Tr
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.if \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.\"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.hy 0
.if n .na
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "PLACE 1"
.TH PLACE 1 "2000-12-30" "perl v5.8.0" "User Contributed Perl Documentation"
.SH "NAME"
Tk::place \- Geometry manager for fixed or rubber\-sheet placement
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
\&\ \fI$widget\fR\->\fBplace\fR?(\fI\-option\fR=>\fIvalue\fR?, \fI\-option\fR=>\fIvalue\fR, ...)?
.PP
\&\ \fI$widget\fR\->\fBplaceForget\fR
.PP
\&\ \fI$widget\fR\->\fBplaceInfo\fR
.PP
\&\ \fI$master\fR\->\fBplaceSlaves\fR
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
The placer is a geometry manager for Tk.
It provides simple fixed placement of windows, where you specify
the exact size and location of one window, called the \fIslave\fR,
within another window, called the \fI$master\fR.
The placer also provides rubber-sheet placement, where you specify the
size and location of the slave in terms of the dimensions of
the master, so that the slave changes size and location
in response to changes in the size of the master.
Lastly, the placer allows you to mix these styles of placement so
that, for example, the slave has a fixed width and height but is
centered inside the master.
.IP "\fI$slave\fR\->\fBplace\fR?(\fI\-option\fR=>\fIvalue\fR?, \fI\-option\fR=>\fIvalue\fR, ...?)?" 4
.IX Item "$slave->place?(-option=>value?, -option=>value, ...?)?"
The \fBplace\fR method arranges for the placer
to manage the geometry of \fI$slave\fR.
The remaining arguments consist of one or more \fI\-option\fR=>\fIvalue\fR
pairs that specify the way in which \fI$slave\fR's
geometry is managed.
If the placer is already managing \fI$slave\fR, then the
\&\fI\-option\fR=>\fIvalue\fR pairs modify the configuration for \fI$slave\fR.
The \fBplace\fR method returns an empty string as result.
The following \fI\-option\fR=>\fIvalue\fR pairs are supported:
.RS 4
.IP "\fB\-in\fR => \fI$master\fR" 8
.IX Item "-in => $master"
\&\fI$master\fR is the reference to the window relative
to which \fI$slave\fR is to be placed.
\&\fI$master\fR must either be \fI$slave\fR's parent or a descendant
of \fI$slave\fR's parent.
In addition, \fI$master\fR and \fI$slave\fR must both be descendants
of the same top-level window.
These restrictions are necessary to guarantee
that \fI$slave\fR is visible whenever \fI$master\fR is visible.
If this option isn't specified then the master defaults to
\&\fI$slave\fR's parent.
.IP "\fB\-x\fR => \fIlocation\fR" 8
.IX Item "-x => location"
\&\fILocation\fR specifies the x\-coordinate within the master window
of the anchor point for \fI$slave\fR widget.
The location is specified in screen units (i.e. any of the forms
accepted by \fBTk_GetPixels\fR) and need not lie within the bounds
of the master window.
.IP "\fB\-relx\fR => \fIlocation\fR" 8
.IX Item "-relx => location"
\&\fILocation\fR specifies the x\-coordinate within the master window
of the anchor point for \fI$slave\fR widget.
In this case the location is specified in a relative fashion
as a floating-point number:  0.0 corresponds to the left edge
of the master and 1.0 corresponds to the right edge of the master.
\&\fILocation\fR need not be in the range 0.0\-1.0.
If both \fB\-x\fR and \fB\-relx\fR are specified for a slave
then their values are summed.  For example, "\fB\-relx\fR=>0.5, \fB\-x\fR=\-2"
positions the left edge of the slave 2 pixels to the left of the
center of its master.
.IP "\fB\-y\fR => \fIlocation\fR" 8
.IX Item "-y => location"
\&\fILocation\fR specifies the y\-coordinate within the master window
of the anchor point for \fI$slave\fR widget.
The location is specified in screen units (i.e. any of the forms
accepted by \fBTk_GetPixels\fR) and need not lie within the bounds
of the master window.
.IP "\fB\-rely\fR => \fIlocation\fR" 8
.IX Item "-rely => location"
\&\fILocation\fR specifies the y\-coordinate within the master window
of the anchor point for \fI$slave\fR widget.
In this case the value is specified in a relative fashion
as a floating-point number:  0.0 corresponds to the top edge
of the master and 1.0 corresponds to the bottom edge of the master.
\&\fILocation\fR need not be in the range 0.0\-1.0.
If both \fB\-y\fR and \fB\-rely\fR are specified for a slave
then their values are summed.  For example, \fB\-rely\fR=>0.5, \fB\-x\fR=>3
positions the top edge of the slave 3 pixels below the
center of its master.
.IP "\fB\-anchor\fR => \fIwhere\fR" 8
.IX Item "-anchor => where"
\&\fIWhere\fR specifies which point of \fI$slave\fR is to be positioned
at the (x,y) location selected by the \fB\-x\fR, \fB\-y\fR,
\&\fB\-relx\fR, and \fB\-rely\fR options.
The anchor point is in terms of the outer area of \fI$slave\fR
including its border, if any.
Thus if \fIwhere\fR is \fBse\fR then the lower-right corner of
\&\fI$slave\fR's border will appear at the given (x,y) location
in the master.
The anchor position defaults to \fBnw\fR.
.IP "\fB\-width\fR => \fIsize\fR" 8
.IX Item "-width => size"
\&\fISize\fR specifies the width for \fI$slave\fR in screen units
(i.e. any of the forms accepted by \fBTk_GetPixels\fR).
The width will be the outer width of \fI$slave\fR including its
border, if any.
If \fIsize\fR is an empty string, or if no \fB\-width\fR
or \fB\-relwidth\fR option is specified, then the width requested
internally by the window will be used.
.IP "\fB\-relwidth\fR => \fIsize\fR" 8
.IX Item "-relwidth => size"
\&\fISize\fR specifies the width for \fI$slave\fR.
In this case the width is specified as a floating-point number
relative to the width of the master: 0.5 means \fI$slave\fR will
be half as wide as the master, 1.0 means \fI$slave\fR will have
the same width as the master, and so on.
If both \fB\-width\fR and \fB\-relwidth\fR are specified for a slave,
their values are summed.  For example, \fB\-relwidth\fR=>1.0, \fB\-width\fR=>5
makes the slave 5 pixels wider than the master.
.IP "\fB\-height\fR => \fIsize\fR" 8
.IX Item "-height => size"
\&\fISize\fR specifies the height for \fI$slave\fR in screen units
(i.e. any of the forms accepted by \fBTk_GetPixels\fR).
The height will be the outer dimension of \fI$slave\fR including its
border, if any.
If \fIsize\fR is an empty string, or if no \fB\-height\fR or
\&\fB\-relheight\fR option is specified, then the height requested
internally by the window will be used.
.IP "\fB\-relheight\fR => \fIsize\fR" 8
.IX Item "-relheight => size"
\&\fISize\fR specifies the height for \fI$slave\fR.
In this case the height is specified as a floating-point number
relative to the height of the master: 0.5 means \fI$slave\fR will
be half as high as the master, 1.0 means \fI$slave\fR will have
the same height as the master, and so on.
If both \fB\-height\fR and \fB\-relheight\fR are specified for a slave,
their values are summed.  For example, \fB\-relheight\fR=>1.0, \fB\-height\fR=>\-2
makes the slave 2 pixels shorter than the master.
.IP "\fB\-bordermode\fR => \fImode\fR" 8
.IX Item "-bordermode => mode"
\&\fIMode\fR determines the degree to which borders within the
master are used in determining the placement of the slave.
The default and most common value is \fBinside\fR.
In this case the placer considers the area of the master to
be the innermost area of the master, inside any border:
an option of \fB\-x\fR=>\fB0\fR corresponds to an x\-coordinate just
inside the border and an option of \fB\-relwidth\fR=>1.0
means \fI$slave\fR will fill the area inside the master's
border.
If \fImode\fR is \fBoutside\fR then the placer considers
the area of the master to include its border;
this mode is typically used when placing \fI$slave\fR
outside its master, as with the options
\&\fB\-x\fR=>\fB0\fR, \fB\-y\fR=>\fB0\fR, \fB\-anchor\fR=>\fBne\fR.
Lastly, \fImode\fR may be specified as \fBignore\fR, in which
case borders are ignored:  the area of the master is considered
to be its official X area, which includes any internal border but
no external border.  A bordermode of \fBignore\fR is probably
not very useful.
.Sp
If the same value is specified separately with
two different options, such as \fB\-x\fR and \fB\-relx\fR, then
the most recent option is used and the older one is ignored.
.RE
.RS 4
.RE
.IP "\fI$slave\fR\->\fBplaceSlaves\fR" 4
.IX Item "$slave->placeSlaves"
The \fBplaceSlaves\fR method returns a list of all the slave
windows for which \fI$master\fR is the master.
If there are no slaves for \fI$master\fR then an empty list is
returned.
.IP "\fI$slave\fR\->\fBplaceForget\fR" 4
.IX Item "$slave->placeForget"
The \fBplaceForget\fR method causes the placer to stop managing
the geometry of \fI$slave\fR.  As a side effect of this method call
\&\fI$slave\fR will be unmapped so that it doesn't appear on the
screen.
If \fI$slave\fR isn't currently managed by the placer then the
method call has no effect.
\&\fBplaceForget\fR returns an empty string as result.
.IP "\fI$slave\fR\->\fBplaceInfo\fR" 4
.IX Item "$slave->placeInfo"
The \fBplaceInfo\fR method returns a list giving the current
configuration of \fI$slave\fR.
The list consists of \fI\-option\fR=>\fIvalue\fR pairs in exactly the
same form as might be specified to the \fBplace\fR
method.
If the configuration of a window has been retrieved with
\&\fBplaceInfo\fR, that configuration can be restored later by
first using \fBplaceForget\fR to erase any existing information
for the window and then invoking \fBplace\fR with
the saved information.
.SH "FINE POINTS"
.IX Header "FINE POINTS"
It is not necessary for the master window to be the parent
of the slave window.
This feature is useful in at least two situations.
First, for complex window layouts it means you can create a
hierarchy of subwindows whose only purpose
is to assist in the layout of the parent.
The ``\fIreal children\fR'' of the parent (i.e. the windows that
are significant for the application's user interface) can be
children of the parent yet be placed inside the windows
of the geometry-management hierarchy.
This means that the path names of the ``\fIreal children\fR''
don't reflect the geometry-management hierarchy and users
can specify options for the real children
without being aware of the structure of the geometry-management
hierarchy.
.PP
A second reason for having a master different than the slave's
parent is to tie two siblings together.
For example, the placer can be used to force a window always to
be positioned centered just below one of its
siblings by specifying the configuration
.PP
\&\ \fB\-in\fR=>\fI$sibling\fR, \fB\-relx\fR=>0.5, \fB\-rely\fR=>1.0,
\&\fB\-anchor\fR=>'n', \fB\-bordermode\fR=>'outside'
.PP
Whenever the \fI$sibling\fR widget is repositioned in the future, the slave
will be repositioned as well.
.PP
Unlike many other geometry managers (such as the packer)
the placer does not make any attempt to manipulate the geometry of
the master windows or the parents of slave windows (i.e. it doesn't
set their requested sizes).
To control the sizes of these windows, make them windows like
frames and canvases that provide configuration options for this purpose.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
Tk::form
Tk::grid
Tk::pack
.SH "KEYWORDS"
.IX Header "KEYWORDS"
geometry manager, height, location, master, place, rubber sheet, slave, width