meta data for this page
  •  
Translations of this page:
  • en

This is an old revision of the document!


:section:section-object-margin <insert previous page>

Object - Margin

Understanding Margins in Total Launcher

In Total Launcher, the 'Margin' setting is a fundamental tool for managing space. Its specific function, however, depends on what it is being applied to: a Page or an Object. This guide explains how to use margins in both contexts. The term 'padding' is not used in the Total Launcher interface; all space management of this type is controlled via 'Margin' or 'Item spacing' settings.

Page Margins

When applied to a Page, the margin defines the boundary of the usable area inside the physical screen edges. Think of it as creating an invisible frame around the canvas where objects can be placed.

  • Purpose: The primary use for page margins is to prevent objects from being placed in areas where they might be obscured or interfere with system elements. This includes screen notches, status bars, navigation bars, or gesture areas at the edges of the screen.
  • Effect: Increasing the margin values (e.g., for 'top', 'bottom', 'left', or 'right') will shrink the available workspace, pushing all content inward, away from that respective edge. A value of '0' allows content to be placed right up to the very edge of the device's screen.

Object Margins

The behavior of the 'Margin' setting for an object depends on whether it is a simple object or a container object.

The Margins Dialog for Pages and Objects.

Simple Objects (e.g., Icons, Text, Images)

For simple, non-container objects, the margin defines the empty space outside the object's boundary.

  • Purpose: This margin is used to create separation between one object and its neighbors. It prevents objects from touching or overlapping.
  • Effect: A positive margin pushes other objects away from it. A negative margin reduces this space, allowing the object to move closer to, and potentially overlap, adjacent objects.

Container Objects (e.g., Folders, Sliding Drawers, Widgets)

For objects that act as containers for other items, the 'Margin' setting functions exactly like a Page Margin. It defines the usable space inside the container's own borders.

  • Purpose: This margin controls the internal “inset” or border area within the container. It determines how close the items inside (e.g., app icons within a folder) can get to the container's edge.
  • Effect: Increasing the margin value shrinks the area where the container's contents can be placed, pulling them inward from the container's edges. This ensures the contents do not touch the visual border of the folder or widget itself.

Margin Dialog Controls

The dialog for adjusting margins is consistent for both Pages and Objects.

  • left, right, top, and bottom: - Each value is adjusted separately, allowing for precise and asymmetrical control over spacing.
  • Positive Numbers: Increase the defined space. For a Page or Container, this shrinks the content area. For a Simple Object, this pushes other objects further away.
  • Negative Numbers: Decrease the space. This is only applicable to Simple Objects and will cause them to expand beyond their cell boundaries, creating an overlap effect.
  • Suggest: - Tap to automatically calculate margin values. This is useful when an object has effects like a shadow that extend beyond its normal boundaries, ensuring the effect is not clipped.
  • OK: - Tap to accept the margin numbers shown.

While 'Margin' controls space around the borders, a different setting, 'Item spacing', is used within container objects like Folders and Sliding Drawers.

  • Description: This setting exclusively controls the amount of empty space between the individual items held inside a container. It does not affect the container's margin (the space between the items and the container's edge).
  • Analogy: This feature can be thought of as applying a 'padding' between each item in the grid, spreading them out from each other.
  • How to Choose a Value: The input quantity (e.g., from 0-288) is determined by visual preference and usability. There is no single “correct” value. A user should adjust the number and observe the result, balancing aesthetic appearance (a clean, airy look) with usability (ensuring icons are not so close that they are hard to tap accurately).

Discussion

Enter your comment. Wiki syntax is allowed:
Please solve the following equation to prove you're human. 212 -8 =