Understanding Margins in Total Launcher: Defining Boundaries and Object Separation

Mastering the 'Margin' setting in Total Launcher is essential for precise spatial management and creating polished, professional home screen layouts. Because the Total Launcher interface does not utilize traditional 'padding' controls, mastering margin properties is the primary method for defining workspace boundaries and separating individual layout elements. The exact behavior of a margin depends entirely on the target element, functioning differently when applied to an entire page versus a specific graphic object:

• Page
• 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.

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.
• Positive Margin 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.
• Negative Margin Effect: A negative margin will push the page's canvas off the screen on that side. This creates an area where content can be placed but will not be visible. This is an advanced technique, sometimes used intentionally to hide parts of a layout.

The behavior of the 'Margin' setting for an object depends on whether it is

• a simple object or
• a container object

For simple, non-container objects, the margin defines the empty space outside the object's boundary but is limited to within the container 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.

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 (like 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.

Object Margin Dialog		Page Margin Dialog
	Notice the difference: ⬅️ Object: Based on the internal object container. Positive only. Page: ➡️ Allows negative margins. See discussion above.

• Link all sides: - Activate this feature to cause any side margin change to be applied to all sides.
• Left, Top, Right, and Bottom: - Each value is adjusted separately for precise control. Use the slider or the dialog above the ➕ to enter the amount manually.
• Unit and Range:
  • While not explicitly stated, the unit is best understood as dip (density-independent pixel). This ensures layouts are consistent across Android devices with different screen sizes and resolutions.
    • The default setting is 0.
    • For the 'Object', the maximum positive range is 200. There is no negative capacity.
    • For the 'Page', the maximum positive and negative range is 500.
• Positive Numbers: Increases the defined space.
  • For a Page or Container, this shrinks the usable content area. [+] Practicality limits this; setting a margin equal to the screen width will result in no viewable area.
    • For a Simple Object, this pushes other objects further away.
• Negative Numbers: Decreases the defined space, with different effects:
  • For a Page, this pushes the content canvas off-screen, making it partially or totally unviewable.
  • For a Simple Object, negative margins do not exist.

• Suggest: Tap to automatically calculate margin values, which is useful for objects with effects like a shadow to ensure the effect is not clipped.
• Cancel: Discard all input and return to the previous page.
• OK: Tap to accept the margin numbers shown.

• Item Spacing: While 'Margin' controls space around borders, 'Item spacing' is used within container objects (like Folders, Sliding Drawers, Widgets (App Drawer, App Drawer (pager), App Group, Contacts, and App Search) to control the space between the individual items inside.
• 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 (range of 0 - 200) 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).