meta data for this page
- en
This is an old revision of the document!
Feature Requests And Status
Total Launcher users can request new features be considered for addition to the app by submitting a #FeatureRequest. This area of the uiTLM wiki will track Feature Requests, monitor their status, and provide users and the developer, ChYK, with a consolidated source of requests.
Actual Feature Requests are not to be made at this wiki. Instead, all Feature Requests are to be made at the Official Total Launcher Telegram Group in the following format:
● HOW TO SUBMIT A FEATURE REQUEST You can send feature requests to ChYK by adding #FeatureRequest to the beginning of your post then feature and reason for that feature.
Will I get any feedback ?
#FeatureRequests are read by the Dev for consideration and if implemented, actioned through the Playstore update mechanism, it would be an unrealistic, expectation of chYK to respond, individually and in person, to every request.
Use this Page's Table of Contents to see a listing of recorded Feature Requests or scroll manually through the list below.
Launch Action to Un-Hide Object
Date: 20250531
By: Doreps
Method: Telegram Official Total Launcher Group
Description
Current: The Object Action dialog offers the option “Invisible when edit mode is off,” which 'hides' any object when Edit Off is effective and the launcher is running. If the object has an action link, such as opening an app, tapping the area will still trigger the action and the app will open. This is great for hidden actions.
Requested:
Add a Launcher Action to reverse the current setting in the Object Action dialog. A “toggle” Launcher action and a discreet “Hide”/“Show” selection would provide many customization options for setup designers and users.
Why the current workarounds are inefficient: While this behavior can currently be simulated, the workarounds introduce significant design friction:
• Using a Window: Requires creating a separate, transparent window container to hold and toggle a single object.
• Using Multi-Page Swaps: Requires cloning layouts and globally enabling “Disable page transition by touch” under >Key & Gesture, which sacrifices normal page swiping for the rest of the layout.
• Using Invisible Overlays: Stacking an invisible object on top of a visible one works for launching apps, but cannot dynamically reveal/hide graphic elements on command.
Example Use Case:
A user could create a clean, minimalist home screen with a single discreet button. Tapping that button triggers the Launcher Action to “Show” a hidden group of favorite app icons or widgets, and tapping it again toggles them back to “Hide,” eliminating the need for complex multi-page or window setups.
Status
No report
Discussion