Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _055cfbbcba33d052436c1b6f9c5f1f9e < prev next >

Wrap

Text File | 2000-03-23 | 20.8 KB | 409 lines

<HTML> <HEAD> <TITLE>Tk::form - Geometry manager based on attachment rules</TITLE> <LINK REL="stylesheet" HREF="../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> Tk::form - Geometry manager based on attachment rules </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <LI><A HREF="#specifying attachments">SPECIFYING ATTACHMENTS</A></LI> <UL> <LI><A HREF="#abbreviations:">ABBREVIATIONS:</A></LI> </UL> <LI><A HREF="#using springs">USING SPRINGS</A></LI> <LI><A HREF="#algorithm of form">ALGORITHM OF FORM</A></LI> <LI><A HREF="#circular dependency">CIRCULAR DEPENDENCY</A></LI> <LI><A HREF="#bugs">BUGS</A></LI> <LI><A HREF="#see also">SEE ALSO</A></LI> <LI><A HREF="#keywords">KEYWORDS</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> Tk::form - Geometry manager based on attachment rules <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Linux</LI> <LI>Solaris</LI> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> $widget->form?(args)? $widget->formOption?(args)? <HR> <H1><A NAME="description">DESCRIPTION</A></H1> The form method is used to communicate with the form Geometry Manager, a geometry manager that arranges the geometry of the children in a parent window according to attachment rules. The form geometry manager is very flexible and powerful; it can be used to emulate all the existing features of the Tk packer and placer geometry managers (see <A HREF="../../../site/lib/Tk/pack.html">pack</A>, <A HREF="../../../site/lib/Tk/place.html">place</A>). The form method can have any of several forms, depending on Option: <DL> <DT><A NAME="item_form">$slave->form?(options)?</A> <DD> Sets or adjusts the attachment values of the slave window according to the -option=>value argument pairs. <DL> <DT><A NAME="item_%2Db_%3D%3E_attachment">-b => attachment</A> <DD> Abbreviation for the -bottom option. <DT><A NAME="item_%2Dbottom_%3D%3E_attachment">-bottom => attachment</A> <DD> Specifies an attachment for the bottom edge of the slave window. The attachment must specified according to <A HREF="#specifying attachments">SPECIFYING ATTACHMENTS</A> below. <DT><A NAME="item_%2Dbottomspring_%3D%3E_weight">-bottomspring => weight</A> <DD> Specifies the weight of the spring at the bottom edge of the slave window. See <A HREF="#using springs">USING SPRINGS</A> below. <DT><A NAME="item_%2Dbp_%3D%3E_value">-bp => value</A> <DD> Abbreviation for the -padbottom option. <DT><A NAME="item_%2Dbs_%3D%3E_weight">-bs => weight</A> <DD> Abbreviation for the -bottomspring option. <DT><A NAME="item_%2Dfill_%3D%3E_style">-fill => style</A> <DD> Specifies the fillings when springs are used for this widget. The value must be x, y, both or none. <DT><A NAME="item_%2Din_%3D%3E_%24master">-in => $master</A> <DD> Places the slave window into the specified $master window. If the slave was originally in another master window, all attachment values with respect to the original master window are discarded. Even if the attachment values are the same as in the original master window, they need to be specified again. The -in flag, when needed, must appear as the first flag of options. Otherwise an error is generated. <DT><A NAME="item_%2Dl_%3D%3E_attachment">-l => attachment</A> <DD> Abbreviation for the -left option. <DT><A NAME="item_%2Dleft_%3D%3E_attachment">-left => attachment</A> <DD> Specifies an attachment for the left edge of the slave window. The attachment must specified according to <A HREF="#specifying attachments">SPECIFYING ATTACHMENTS</A> below. <DT><A NAME="item_%2Dleftspring_%3D%3E_weight">-leftspring => weight</A> <DD> Specifies the weight of the spring at the left edge of the slave window. See <A HREF="#using springs">USING SPRINGS</A> below. <DT><A NAME="item_%2Dlp_%3D%3E_value">-lp => value</A> <DD> Abbreviation for the -padleft option. <DT><A NAME="item_%2Dls_%3D%3E_weight">-ls => weight</A> <DD> Abbreviation for the -leftspring option. <DT><A NAME="item_%2Dpadbottom_%3D%3E_value">-padbottom => value</A> <DD> Specifies the amount of external padding to leave on the bottom side of the slave. The value may have any of the forms acceptable to Tk_GetPixels. <DT><A NAME="item_%2Dpadleft_%3D%3E_value">-padleft => value</A> <DD> Specifies the amount of external padding to leave on the left side of the slave. <DT><A NAME="item_%2Dpadright_%3D%3E_value">-padright => value</A> <DD> Specifies the amount of external padding to leave on the right side of the slave. <DT><A NAME="item_%2Dpadtop_%3D%3E_value">-padtop => value</A> <DD> Specifies the amount of external padding to leave on the top side of the slave. <DT><A NAME="item_%2Dpadx_%3D%3E_value">-padx => value</A> <DD> Specifies the amount of external padding to leave on both the left and the right sides of the slave. <DT><A NAME="item_%2Dpady_%3D%3E_value">-pady => value</A> <DD> Specifies the amount of external padding to leave on both the top and the bottom sides of the slave. <DT><A NAME="item_%2Dr_%3D%3E_attachment">-r => attachment</A> <DD> Abbreviation for the -right option. <DT><A NAME="item_%2Dright_%3D%3E_attachment">-right => attachment</A> <DD> Specifies an attachment for the right edge of the slave window. The attachment must specified according to <A HREF="#specifying attachments">SPECIFYING ATTACHMENTS</A> below. <DT><A NAME="item_%2Drightspring_%3D%3E_weight">-rightspring => weight</A> <DD> Specifies the weight of the spring at the right edge of the slave window. See <A HREF="#using springs">USING SPRINGS</A> below. <DT><A NAME="item_%2Drp_%3D%3E_value">-rp => value</A> <DD> Abbreviation for the -padright option. <DT><A NAME="item_%2Drs_%3D%3E_weight">-rs => weight</A> <DD> Abbreviation for the -rightspring option. <DT><A NAME="item_%2Dt_%3D%3E_attachment">-t => attachment</A> <DD> Abbreviation for the -top option. <DT><A NAME="item_%2Dtop_%3D%3E_attachment">-top => attachment</A> <DD> Specifies an attachment for the top edge of the slave window. The attachment must specified according to <A HREF="#specifying attachments">SPECIFYING ATTACHMENTS</A> below. <DT><A NAME="item_%2Dtopspring_%3D%3E_weight">-topspring => weight</A> <DD> Specifies the weight of the spring at the top edge of the slave window. See <A HREF="#using springs">USING SPRINGS</A> below. <DT><A NAME="item_%2Dtp_%3D%3E_value">-tp => value</A> <DD> Abbreviation for the -padtop option. <DT><A NAME="item_%2Dts_%3D%3E_weight">-ts => weight</A> <DD> Abbreviation for the -topspring option. </DL> <DT><A NAME="item_formCheck">$master->formCheck</A> <DD> This method checks whether there is circular dependency in the attachments of the master's slaves (see <A HREF="#circular dependency">CIRCULAR DEPENDENCY</A> below). It returns the Boolean value TRUE if it discover circular dependency and FALSE otherwise. <DT><A NAME="item_formForget">$slave->formForget</A> <DD> Removes the slave from its master and unmaps its window. The slave will no longer be managed by form. All attachment values with respect to its master window are discarded. If another slave is attached to this slave, then the attachment of the other slave will be changed to grid attachment based on its geometry. <DT><A NAME="item_formGrid">$master->formGrid?(x_size, y_size)?</A> <DD> When x_size and y_size are given, this method returns the number of grids of the $master window in a pair of integers of the form (x_size, y_size). When both x_size and y_size are given, this method changes the number of horizontal and vertical grids on the master window. <DT><A NAME="item_formInfo">$slave->formInfo?(-option)?</A> <DD> Queries the attachment options of a slave window. -option can be any of the options accepted by the form method. If -option is given, only the value of that option is returned. Otherwise, this method returns a list whose elements are the current configuration state of the slave given in the same option-value form that might be specified to form. The first two elements in this list list are ``-in=>$master'' where $master is the slave's master window. <DT><A NAME="item_formSlaves">$master->formSlaves</A> <DD> Returns a list of all of the slaves for the master window. The order of the slaves in the list is the same as their order in the packing order. If master has no slaves then an empty string is returned. </DL> <HR> <H1><A NAME="specifying attachments">SPECIFYING ATTACHMENTS</A></H1> One can specify an attachment for each side of a slave window managed by form. An attachment is specified in the the form ``-side => [anchor_point, offset]''. -side can be one of -top, -bottom, -left or -right. Offset is given in screen units (i.e. any of the forms acceptable to Tk_GetPixels). A positive offset indicates shifting to a position to the right or bottom of an anchor point. A negative offset indicates shifting to a position to the left or top of an anchor point. Anchor_point can be given in one of the following forms: <DL> <DT><A NAME="item_Grid_Attachment">Grid Attachment</A> <DD> The master window is divided into a number of horizontal and vertical grids. By default the master window is divided into 100x100 grids; the number of grids can be adjusted by the formGrid method. A grid attachment anchor point is given by a % sign followed by an integer value. For example, '%0' specifies the first grid line (the top or left edge of the master window). '%100' specifies the last grid line (the bottom or right edge of the master window). <DT><A NAME="item_Opposite_Side_Attachment">Opposite Side Attachment</A> <DD> Opposite attachment specifies an anchor point located on the opposite side of another slave widget, which must be managed by form in the same master window. An opposite attachment anchor point is given by the name of another widget. For example, ``$b->form(-top=>[$a,0])'' attaches the top side of the widget $b to the bottom of the widget $a. <DT><A NAME="item_Parallel_Side_Attachment">Parallel Side Attachment</A> <DD> Opposite attachment specifies an anchor point located on the same side of another slave widget, which must be managed by form in the same master window. An parallel attachment anchor point is given by the sign & follwed by the name of another widget. For example, ``$b->form(-top=>['&',$a,0])'' attaches the top side of the widget $b to the top of the widget $a, making the top sides of these two widgets at the same vertical position in their parent window. <DT><A NAME="item_No_Attachment">No Attachment</A> <DD> Specifies a side of the slave to be attached to nothing, indicated by the keyword none. When the none anchor point is given, the offset must be zero (or not present). When a side of a slave is attached to ['none', 0], the position of this side is calculated by the position of the other side and the natural size of the slave. For example, if a the left side of a widget is attached to ['%0', 100], its right side attached to ['none', 0], and the natural size of the widget is 50 pixels, the right side of the widget will be positioned at pixel ['%0', 149]. When both -top and -bottom are attached to none, then by default -top will be attached to ['%0', 0]. When both -left and -right are attached to none, then by default -left will be attached to ['%0', 0]. </DL> Shifting effects can be achieved by specifying a non-zero offset with an anchor point. In the following example, the top side of widget \$b is attached to the bottom of \$a; hence \$b always appears below \$a. Also, the left edge of \$b is attached to the left side of \$a with a 10 pixel offest. Therefore, the left edge of \$b is always shifted 10 pixels to the right of \$a's left edge: $b->form(-left=>[$a,10], -top=>[$a,0]); <H2><A NAME="abbreviations:">ABBREVIATIONS:</A></H2> Certain abbreviations can be made on the attachment specifications: First an offset of zero can be omitted. Thus, the following two lines are equivalent: $b->form(-top=>[$a,0], -right=>['%100',0]); $b->form(-top=>[$a], -right=>'%100'); In the second case, when the anchor point is omitted, the offset must be given. A default anchor point is chosen according to the value of the offset. If the anchor point is 0 or positive, the default anchor point %0 is used; thus, ``$b->form(-top=>15)'' attaches the top edge of $b to a position 15 pixels below the top edge of the master window. If the anchor point is ``-0'' or negative, the default anchor point %100 is used; thus, ``$a->form(-right=>-2)'' attaches the right edge of \$a to a position 2 pixels to the left of the master window's right edge. An further example below shows a method with its equivalent abbreviation. $b->form(-top=>['%0',10], -bottom=>['%100',0]); $b->form(-top=>10, -bottom=>-0); <HR> <H1><A NAME="using springs">USING SPRINGS</A></H1> To be written. <HR> <H1><A NAME="algorithm of form">ALGORITHM OF FORM</A></H1> form starts with any slave in the list of slaves of the master window. Then it tries to determine the position of each side of the slave. If the attachment of a side of the slave is grid attachment, the position of the side is readily determined. If the attachment of this side is none, then form tries to determine the position of the opposite side first, and then use the position of the opposite side and the natural size of the slave to determine the position of this side. If the attachment is opposite or parallel widget attachments, then form tries to determine the positions of the other widget first, and then use the positions of the other widget and the natural size of the slave determine the position of this side. This recursive algorithmis carried on until the positions of all slaves are determined. <HR> <H1><A NAME="circular dependency">CIRCULAR DEPENDENCY</A></H1> The algorithm of form will fail if a circular dependency exists in the attachments of the slaves. For example: $c->form(-left=>$b); $b->form(-right=>$c); In this example, the position of the left side of $b depends on the right side of $c, which in turn depends on the left side of $b. When a circular dependency is discovered during the execution of the form algorithm, form will generate a background error and the geometry of the slaves are undefined (and will be arbitrary). Notice that form only executes the algorithm when the specification of the slaves' attachments is complete. Therefore, it allows intermediate states of circular dependency during the specification of the slaves' attachments. Also, unlike the Motif Form manager widget, form defines circular dependency as ``dependency in the same dimension''. Therefore, the following code fragment will does not have circular dependency because the two widgets do not depend on each other in the same dimension ($b depends $c in the horizontal dimension and $c depends on $b in the vertical dimension): $b->form(-left=>$c); $c->form(-top=>$b); <HR> <H1><A NAME="bugs">BUGS</A></H1> Springs have not been fully implemented yet. <HR> <H1><A NAME="see also">SEE ALSO</A></H1> <A HREF="../../../site/lib/Tk/grid.html">Tk::grid</A> <A HREF="../../../site/lib/Tk/pack.html">Tk::pack</A> <A HREF="../../../site/lib/Tk/place.html">Tk::place</A> <HR> <H1><A NAME="keywords">KEYWORDS</A></H1> geometry manager, form, attachment, spring, propagation, size, pack, tix, master, slave <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> Tk::form - Geometry manager based on attachment rules </TD></TR> </TABLE> </BODY> </HTML>