meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
section:section-windows [2026/08/04 21:05] – dorepssection:section-windows [2026/08/05 14:46] (current) – doreps
Line 1: Line 1:
-====== Understanding and Using Windows ====== +====== Total Launcher Window Management: Building Pop-Up Drawers, Widgets, and Variables ====== 
-  * A comprehensive guide to the window layout element+ 
 +Window containers in Total Launcher function as dynamic pop-up layers and floating pages positioned above the main desktop canvas. Using window resources allows the creation of modular interface elements—such as custom app drawers, floating widget shelves, and contextual pop-up menus—without occupying permanent homescreen space. Understanding the distinction between modal and non-modal behaviors, along with proper gesture triggers and animation properties, provides the foundation for building highly responsive, multi-layered Android layouts. The following documentation details window creation methods, structural property options, and advanced automation workflows.
  
 This section explains the concept of windows within Total Launcher, detailing creation methods, property configuration, and practical applications for customized screen layouts. This section explains the concept of windows within Total Launcher, detailing creation methods, property configuration, and practical applications for customized screen layouts.
Line 103: Line 104:
 While windows serve as functional layout containers out of the box, integrating them with variables and automated actions unlocks highly dynamic behaviors. While windows serve as functional layout containers out of the box, integrating them with variables and automated actions unlocks highly dynamic behaviors.
  
-=== Passing Variables === +==== Passing Variables ==== 
-Variables permit a single window design to display completely different text or imagery depending on what action opened it. This reduces the need to build dozens of identical windows. +Variables permit a single window design to display completely different text or imagery depending on what action opened it. This reduces the need to build numerous identical windows. 
-  * **The Concept:** - Rather than creating five separate windows for five different notifications, create one master window template. An external tool passes data into the launcher, updating the template before the window appears. +  * **The Concept:** - Rather than creating multiple separate windows for different notifications, create one master window template. An external tool passes data into the launcher, updating the template before the window appears. 
-  * **Implementation:** - Insert a text object inside the window and format its text as a launcher variable (e.g., ''$notification_text''). Utilize automation apps like Tasker or MacroDroid (often via the Total Launcher plugin or intent broadcasts) to push updated text to the ''$notification_text'' variable. Following the variable update, the automation app triggers the window to open, displaying the freshly injected data.+  * **Implementation:** - Insert a text object inside the window and format its text to call a launcher variable using angular brackets (e.g., ''<notification_text>''). The angular bracket format (''<name>'') is a native Total Launcher syntax requirement; it instructs the launcher to evaluate the string as a dynamic variable rather than rendering it as literal text. Utilize automation apps like Tasker or MacroDroid via the Total Launcher plugin to push updated text to the target variable. Note that when configuring the target variable name within the automation app's plugin interface, the angular brackets must be omitted (e.g., entered only as ''notification_text''). Following the variable update, the automation app triggers the window to open, displaying the freshly injected data.
  
 === Chaining Windows === === Chaining Windows ===