Scene - Feature Requests

Endercraft

Moderator
If you want a dynamic image, store said image as base64 then set in url: (example for a PNG file) data:image/png;base64,[lv=base64image]
This means the image can be dynamic and stored locally without the need to setup a web server. Of course using this with many big images may be too extreme for MacroDroid to handle.
 

sooraj

Active member
If you want a dynamic image, store said image as base64 then set in url: (example for a PNG file) data:image/png;base64,[lv=base64image]
This means the image can be dynamic and stored locally without the need to setup a web server. Of course using this with many big images may be too extreme for MacroDroid to handle.
already tried that app will crash when having such large blob of text save in variable
 

sooraj

Active member
1) AGAIN BUG is app caching the image on server image has been replaced but app dislsys same old image

2) Another thing is i alteady discarded macro created new one restatred server yet it shows old image , image that dont exist
app actually copies imafe internally and uses it, even with URL it actually dont give damm about url, purpose if url is tobhave dynamic while local file can be dynamic by logic i set mavrodroid to display local image
/sdcard/image.jpg
Now i replaced image in filesystem
with another photo but i kept name same that is image.jpg

But it show old image means file path or url doesnt matter it cache copies file internally and uses it also dont update its cache
 

pluto25

Member
Text size defined by an integer value

This would help to calculate a text size being suitable for a screen resolution (which could be read by the macro) to provide views which fit best to the screen of different users.
 

Elieston

Member
It would be interesting if scene items could activate actions without depending on variables. Something like a constraint or within the scene item you could choose and configure actions that would be executed when interacting with that item.
 

SiElyes

New member
Round edges for the overlay and dialogue scene background UI would be really cool! Also, fade in and fade out or any other sort of animations while opening/ closing a scene would also make it look more modern!
 

Winny57

Active member
Don't hesitate to post your scenes to give other members creative ideas 👍
 

Shivam.kxn

New member
Please place all feature requests and ideas for the new custom scene feature here. I am receiving many suggestions from all over the place so please keep everything here so I can more easily track everything.
1. Adding font customization and animation effects would greatly improve the visual appeal and functionality of floating text, making macros more interactive and engaging. If this feature could be considered in future updates, it would be highly beneficial.
2.You can add a negative of "if confirm then" I mean "if not confirm then" like this and also add variables for this option if you can.
 

Shivam.kxn

New member
Please place all feature requests and ideas for the new custom scene feature here. I am receiving many suggestions from all over the place so please keep everything here so I can more easily track everything.
**Feature Request: Enhanced Schedule Option and Alternative Confirmation Handling**

1. **Integrated Scheduling Option Within Scenes**

- **Objective:**
Provide users with the ability to schedule actions directly within the scene interface—functioning like a reminder or alarm. Although a similar “wait until trigger” option exists in MacroDroid, this proposal differs by integrating the scheduling mechanism directly into scenes or into actions for triggering purposes.

- **Functionality Details:**
- **Editable Clock Widget:**
Within the scene, include a clock-style or digital clock element that can be manually set and adjusted by the user. For example, if a user sets the schedule for 2:00 PM using this widget, the next macro action will execute exactly at 2:00 PM.
- **Variable Integration & Condition Features:**
Incorporate variables (e.g., true/false) and additional condition features in the scheduling system. This would enable users to decide whether certain conditions—for instance, if the screen must be on—are met before triggering the next action.

The goal is to offer a more intuitive and flexible scheduling solution that is distinctly separate from the existing “wait until trigger” action.

2. **Enhanced “If Confirmed Then” Action with an Alternative Branch**

- **Objective:**
Extend the current “if confirmed then” action so that an alternative branch can be executed when the confirmation is declined. At present, when a macro displays a prompt such as “Do you want to run this macro?”, only the “OK” (confirm) option leads to subsequent actions. If the user selects “Cancel” (not confirmed), no further actions are executed.

- **Functionality Details:**
- **Dual-Branch Execution:**
Introduce an option that allows users to specify what happens when the macro is canceled. In addition to the existing “if confirmed then” branch, a new “if not confirmed then” branch would be available, enabling a separate set of actions to run if the user selects “Cancel.”
- **Flow Control Flexibility:**
This enhancement would grant users the ability to design alternative flows within their macros. For instance, when a confirmation is sought, the user’s “OK” response could trigger one set of actions, whereas a “Cancel” could trigger a different set—thereby ensuring that undesired termination of processes does not simply result in a lack of response.
 

Dm114

Well-known member
In order to optimize display on the screen, would it be possible to display Text, Icon, Image, Slider and Progression bar in vertical mode (in addition to horizontal one)?
 

leihaoa

Member
Android 11 users
Hello development team.
I:Add a "text display box" function to display the return value.
Explanation: For example, text input box 1+text input box 2, after pressing "Calculate" button, the calculation result will be shown in the "display box", instead of closing this interface, and the display box is in a non-editable state.
Second: Add an "Exit" option to the "Keystroke" function.
Explanation: I can only close this interface when I press the "Exit" button.
C1): The customized scene interface should always be displayed in the foreground, instead of being exited when I press the "button".
Explanation:After pressing "Calculate" button, it will call macro/action to process the input data, the interface will not be closed, and the return value will be shown in the "text display box".
The customized scene will not exit when floating text/displaying notification/popup message, the popup interface will be displayed in front of the "Customized Scene". When the popup screen is closed, the customized scene is still displayed in the foreground. The custom scene page will be exited only after pressing the "Exit" button.
I'm just using it as an example, not as a calculator 😂 Looking forward to hearing back from the team. It's great to see a software getting better and stronger as a "minority shareholder". Lastly, I'm curious 🤔 what is the "date of birth" of this software?
 

leihaoa

Member
Android 11 users
Hello development team.
I:Add a "text display box" function to display the return value.
Explanation: For example, text input box 1+text input box 2, after pressing "Calculate" button, the calculation result will be shown in the "display box", instead of closing this interface, and the display box is in a non-editable state.
Second: Add an "Exit" option to the "Keystroke" function.
Explanation: I can only close this interface when I press the "Exit" button.
C1): The customized scene interface should always be displayed in the foreground, instead of being exited when I press the "button".
Explanation:After pressing "Calculate" button, it will call macro/action to process the input data, the interface will not be closed, and the return value will be shown in the "text display box".
The customized scene will not exit when floating text/displaying notification/popup message, the popup interface will be displayed in front of the "Customized Scene". When the popup screen is closed, the customized scene is still displayed in the foreground. The custom scene page will be exited only after pressing the "Exit" button.
I'm just using it as an example, not as a calculator 😂 Looking forward to hearing back from the team. It's great to see a software getting better and stronger as a "minority shareholder". Lastly, I'm curious 🤔 what is the "date of birth" of this software?
This is using Google Translate
Android 11 users
Hello, development team.
1: Add a "text display box" function to display the return value.
Note: For example, text input box 1 + text input box 2, after pressing the "calculate" button, the calculation result will be displayed in the "display box" instead of closing this interface, and the display box is in an uneditable state.
2: Add an "exit" option to the "button" function.
Note: I can only close this interface after pressing the "exit" button
3①: The custom scene interface should always be displayed in the foreground, not when I press the "button".
Note: After pressing the "calculate" button, the macro/action will be called to process the input data, the interface will not be closed, and the return value will be displayed in the "text display box".
② The custom scene will not exit when floating text/display notification/pop-up message prompts, and the pop-up interface will be displayed in front of the "custom scene". When the pop-up interface is closed, the custom scene is still displayed in the foreground. Press the "exit" button to exit the custom scene page.
I just gave an example, not used it as a calculator 😂 I look forward to the reply from the team members. As a "small shareholder", I am very pleased to see a software gradually improve and become more powerful. At the end, I am curious 🤔 When is the "birth date" of this software?
 
I've been keeping a list of feature requests for Custom Scenes since I've been testing it out lately. I'm not sure if the forum policy is to split these apart into separate messages or combine into a single, so I will default to the latter.
  • Drop Down Selector: Add ability to create a temporary Array/Dictionary, without needing to pre-create it. Similar to the Selection Dialog feature.
  • Drop Down Selector: In addition to the above, allow for user to dynamically type/add their own entry as the scene is running, which adds that string to the variable result.
  • Drop Down Selector: Add function for multi-selection, and output to be saved to var as a comma separated string.
  • New feature: Add Separator. This can be done manually now by adding a Text field and then adding dashes to it. But a premade separator would be very good, and the ability to change its color (much like how the recent beta added to the editor window).
  • New feature: Add Radio selector. This is similar but functionally different than Checkbox. A Checkbox allows multiple to be selected, but a Radio only allows one to be selected from its list. This is similar to a Drop Down Selector but visually different, making quick entries more functional.
  • Sliders: Add a title to the slider box. Currently this can be manually done by adding a Text field and adding it above the slider, but this is messy and requires managing two separate blocks which should be combined.
  • Remember Color: Currently, when a Color is selected inside of any block (e.g. Text, or Button, etc), when it is saved and then the user edits it again, the correct color is preselected but the color brightness is defaulted to the brightest on the slider. This should be remembered so that it shows the exact color when re-editing the color.
  • Variable renaming: When variables are renamed in the macro editor, they are not dynamically changed in any of the Scene actions. This should be done, as it is with other actions within the editor.
  • Text Entry: Allow for choosing to enter String OR Integer.
Seperator in v5.54
 
I've been keeping a list of feature requests for Custom Scenes since I've been testing it out lately. I'm not sure if the forum policy is to split these apart into separate messages or combine into a single, so I will default to the latter.
  • Drop Down Selector: Add ability to create a temporary Array/Dictionary, without needing to pre-create it. Similar to the Selection Dialog feature.
  • Drop Down Selector: In addition to the above, allow for user to dynamically type/add their own entry as the scene is running, which adds that string to the variable result.
  • Drop Down Selector: Add function for multi-selection, and output to be saved to var as a comma separated string.
  • New feature: Add Separator. This can be done manually now by adding a Text field and then adding dashes to it. But a premade separator would be very good, and the ability to change its color (much like how the recent beta added to the editor window).
  • New feature: Add Radio selector. This is similar but functionally different than Checkbox. A Checkbox allows multiple to be selected, but a Radio only allows one to be selected from its list. This is similar to a Drop Down Selector but visually different, making quick entries more functional.
  • Sliders: Add a title to the slider box. Currently this can be manually done by adding a Text field and adding it above the slider, but this is messy and requires managing two separate blocks which should be combined.
  • Remember Color: Currently, when a Color is selected inside of any block (e.g. Text, or Button, etc), when it is saved and then the user edits it again, the correct color is preselected but the color brightness is defaulted to the brightest on the slider. This should be remembered so that it shows the exact color when re-editing the color.
  • Variable renaming: When variables are renamed in the macro editor, they are not dynamically changed in any of the Scene actions. This should be done, as it is with other actions within the editor.
  • Text Entry: Allow for choosing to enter String OR Integer.
Seperator in v5.54
 
Request that every element have an "Is Visible" characteristic based on a boolean variable. If the variable is False then the element is not visible. If all elements in a row are not visible, the below elements should slide up and the scene should be shorter.
In v5.54
 
Top