| Did you know ... | Search Documentation: |
| Instance variables |
->border<-can_resize
sets it to @on
if this tile is stretchable in the direction of its tile<-super
and there is at least one stretchable tile below or right of this tile.
See also tile->hor_stretch, tile->hor_shrink, tile->ver_stretch
and
tile->ver_shrink.
<-ideal_width’s
of the stacked tiles. If this sum is equal to the desired total width
the stretch- and shrink-parameters are ignored. If the sum is smaller
than the desired width tile<-hor_stretch
is considered. Finally, if the sum is larger than the desired total
width the system first attempts to shrink all windows that have tile<-hor_shrink >
0 proportional to their tile<-hor_shrink
value. If this does not make the total width small enough, all windows
with tile<-hor_shrink
== 0 are made equally less wide.
Defaults: The default value is 100.
-ideal_width -hor_stretch-hor_shrink-hor_shrinkleaf-tile) it
is managing a horizontal or vertical stack of subtiles. These subtiles
are in the chain tile<-members.
Each of the subtiles’ tile<-super
points to this
tile object. The
variable tile<-orientation
is set to either horizontal or vertical.
A tile that manages a number of sub-tiles is normally created by its sub-tiles:
?- new(X, tile(box(100, 100))), new(Y, tile(box(200, 100))), send(X, right, Y).
Will create two tiles and a third, which is a tile with tile<-orientation:
horizontal and tile<-members
the X and Y tiles.
-super<-width, tile<-height
and tile->set.none, the tile is a
leaf tile controlling an tile<-object.
If horizontal, the
tile<-members
are places left-to-right. If vertical they are placed
top-to-bottom.-members