note/desc field to the "start" blocks

92 views
Skip to first unread message

Ahmet K

unread,
Mar 1, 2023, 6:12:14 AM3/1/23
to Automate
Can you add a note/desc field to the "start" blocks?
Please see the attached scrshot.

Flow start
App start
App shortcut start
Service start
Etc.. 
01.png

Henrik "The Developer" Lindqvist

unread,
Mar 1, 2023, 7:54:20 AM3/1/23
to Automate
A note and/or descriptions field would make little sense since no other block has/would have them.
Resolve and show the flow title instead of URI is a feature on the to-do list, but i've been hesitant to implement it since could be very slow to do so, especially on the flowchart view. Also, the information of which Flow beginning block would be hidden/lost.

Ahmet K

unread,
Mar 1, 2023, 10:42:59 AM3/1/23
to Automate
Actually I think for each block there should be a "note field" which functions as a "remark" as in programming languages.

Henrik "The Developer" Lindqvist

unread,
Mar 1, 2023, 11:03:55 AM3/1/23
to Automate
Some way to comment the flowchart is already on the to-do list, but it will likely not be additional fields on the block configuration screen.

Kantachart Chawchumnum

unread,
Mar 1, 2023, 3:35:53 PM3/1/23
to automa...@googlegroups.com

เมื่อ พ. 1 มี.ค. 2566 เวลา 22:42 Ahmet K <ahka...@gmail.com> เขียนว่า:
Actually I think for each block there should be a "note field" which functions as a "remark" as in programming languages.

--
You received this message because you are subscribed to the Google Groups "Automate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automate-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/CAEfOJjwhnjD8v8Z3zgnwuq0Gy7ZETGb3xr9a3xzc4bCGW14_Wg%40mail.gmail.com.
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted

Victor S.

unread,
Jul 21, 2024, 2:39:41 PM7/21/24
to Automate for Android
What I am doing, until the ability to add comments/remarks is implemented, is adding a `Set variable` block next to the block I want to "remark" on, naming the variable "Comment", and entering my remarks in the `Value` field. Usually, I won't even link my makeshift "Comment" block unless it will not be obvious to which block it refers to.

Ahmet K

unread,
Jul 22, 2024, 1:56:23 AM7/22/24
to Automate
Yes, that's an option too. Thx.



21 Tem 2024 Pzr 21:39 tarihinde Victor S. <vshr...@gmail.com> şunu yazdı:
What I am doing, until the ability to add comments/remarks is implemented, is adding a `Set variable` block next to the block I want to "remark" on, naming the variable "Comment", and entering my remarks in the `Value` field. Usually, I won't even link my makeshift "Comment" block unless it will not be obvious to which block it refers to.
On Wednesday, March 1, 2023 at 10:42:59 AM UTC-5 Ahmet K wrote:
Actually I think for each block there should be a "note field" which functions as a "remark" as in programming languages.

--
You received this message because you are subscribed to the Google Groups "Automate for Android" group.

To unsubscribe from this group and stop receiving emails from it, send an email to automate-use...@googlegroups.com.

Ian Hinton

unread,
Jan 29, 2026, 2:08:43 PM (12 days ago) Jan 29
to Automate for Android
I sorely miss a comment block. It makes future maintenance work much easier, as well as keeping a clear picture while in the creation phase. Making modifications in a flow I created some time ago can be challenging at times: trying to understand how things were done, what algorithms were used, meaning and usage of certain variables, etc... I've been programming for over 50 years (70 y.o. now), and the most valuable thing I learned at an early stage was documenting my work - for myself and for others. Trying to modify somebody else's undocumented program is often nearly impossible, resulting on many ocasions in rewriting it from scratch.
Same as Victor S., I created my own workaround by adopting another block, in my case the "Append log" block. For this to work without interfering in the real logging of the flow, do the following:
  1. First disactivate the "Logging" box in the main page of the flow (where all the privileges are listed)
  2. Insert your "Append log" block wherever you want to document something and activate its "Logging" field, setting it to "Only when logging enabled". This will avoid messing up the flow's log.
  3. When inserting an "Append log" block that you want to pass log messages to your log, make sure that its "Logging" field is disactivated.
The result is each Log block will display upto 28 characters without needing to open it (of course, you can write more as usual). This makes it easy to skim through your flows.
I prefer using the "Append log" block instead of the "Variable set" block because the icon displays more of my text, and looks cleaner. In any case, thanks to Victor S. for his workardound, as this is what got me on the right path some months ago.

For the developer: PLEASE include  comment block.
Reply all
Reply to author
Forward
0 new messages