Keys & Gestures

Gestures in Total Launcher provide a method for executing commands, launching applications, or manipulating the user interface without relying on visible buttons. These interactions are divided into two primary categories: global gestures that apply to the entire launcher environment, and object-specific gestures attached to individual items.

Introduction to Gestures Total Launcher supports a wide array of inputs, including standard swipes, multi-touch interactions, and device sensor triggers (shaking or flipping the device). Configuring these allows for a minimalist design by hiding complex functionality behind invisible triggers.

Keys & Gestures dialog :

Navigate to: Launcher Options > Key & Gestures.
Scope: - Applies to the home screen and other launcher windows unless overridden by an object.

Global gestures are detected on the background of the launcher (empty space) and are not tied to specific objects. These are managed within the main launcher settings.

The Key & Gestures menu separates inputs into standard touch gestures, landscape-specific overrides, and sensor-based actions.

The Gestures Landscape section allows for a distinct set of actions when the device is rotated.

• Different actions for landscape: - Enabling this toggle allows the user to assign unique actions to the gestures listed above when the device is in landscape orientation.

Additional configuration options are available at the bottom of the Key & Gestures menu.

• Gesture animation: - Toggles the visual feedback when a gesture is recognized.
• Gesture vibration: - Toggles haptic feedback when a gesture is executed.
• Disable long-press background: - Prevents the long-press action from opening the launcher menu. Note that the menu can still be accessed via the Pinch out gesture (or Pinch in depending on configuration) even if this is enabled.
• Disallow page transition by touch: - Prevents touching to change pages, requiring navigation via buttons, sequences or other links.

Gestures can also be assigned to individual objects, such as app icons, graphic images, or text. This allows a single object to perform multiple functions.

• Configuration: - Select an object in Edit mode, then navigate to the object's Action menu .
• Swipe Actions: - Determines what happens when the user swipes directly on the specific object.
  • Direction: - Directions for object swipes are generally limited to the four cardinal directions (Up, Down, Left, Right) relative to the object.

Examples of object-specific configurations:

1. Folder Emulation: - Tapping an icon opens the app; swiping up on the same icon opens a folder. An example may be tap to open a Finance folder containing all financial-related apps while a swipe left would open the ABC Bank or a swipe right would open the primary credit card.
2. Widget Control: - Swiping on a music widget change the media volume.

For theme designers, gestures offer a way to maintain a clean aesthetic while retaining complex functionality. Advanced implementation often involves the use of invisible objects or “hotspots.”

• Invisible Hotspots: - Places a transparent Graphic object (opacity set to 0) over a specific area of the wallpaper.
• Layering (Z-Index): - Ensures the invisible object intercepts touch events by placing it above other elements. This is achieved by selecting the object in Edit mode and using the “Bring to front” or “Order” commands to move it to the top layer.
• Action Assignment: - Assigns a Tap or Swipe action to this invisible object to trigger the desired command.

This technique is useful for:

1. Stealth Navigation: - Creating secret tap zones to reveal hidden windows.
2. Custom Controls: - Overlaying gesture areas on top of static wallpapers to simulate interactive buttons.
3. Conflict Resolution: - If a widget has internal touch controls that conflict with a global swipe gesture, placing a container or invisible object on top can manage how the touch is intercepted.

Note: When Edit mode is active, some gestures may be disabled or modified to allow for object selection and movement. Testing should always be performed in Use mode.