>>127
outputをローカル変数代わりに使える
キメの問題だけどそれでもABの隔離思想となじまないから(内部的には同じでもいいんだけど)少なくとも表示上設定フィールドを分けて、間違っても戻り値に含まないようにして欲しいと伝えてはある

As my conclusion at this moment, the editing feel of Action blocks is a little limited than normal macros'. That's my latest feedbacks. Please consider below improvements when you add other features in future update.

1. navigation link to the local test log view via the top right ... menu
It has no direct access to the system log. As a typical usecase, if an editing action block is nested deeply such as macro -> action block -> action block..., I have to be back 3 or more times to home screen once, then choose the system log tile.

2. "local variable"
I don't mean just same as the local variable of standard macros. It works as same as the current output parameter internally, but has only one limitation NOT to return the value to avoid unexpected mistakes. It shows in another field like normal local value of regular macros, but never keep the value, only for the current instance. It makes a dialog small and short on an action statement in a caller macro as well.

3. check a testing result easier
Currently, a testing result is not shows as the default value of the output parameter when testing entirely via the top right ... menu, only when testing the individual statement via context menu of each action. So the top right ... test menu is not helpful, while continuous step by step testing on each statement is useful.

4. pack one or more action block(s) in one file
I often make a bunch of "low level" functions. Therefore pack them as a chunk in a .ablock file. It might be better to have the extension such as .alib or .achunk to identity easily. I'm not sure but It might be realized just writing a simple, never called "catalog" wrapper to collect them and make a recursive chunk though.

5. filter feature on the list view
The numbers of Action blocks should be 100++ soon. So the list view would be nicer to have a filter feature, just same as the normal macro list has.
Some guys might prefer categorized one such as tab or tree view by name. I decide to name them as my rule like "myLib.myClass(.mySubclass...).myFunc()" for their visibility and quick access, but people might not. so it is better that each action block has an attribute to determine where they should be as users' definitions.

6. share as an image
Same as macros'. It is better to have a feature taking screenshot of an action block even longer to share on MD forum or so.