The current ‘comment’ action is a little clunky imho - you have to actually open up the comment to see what it says. It’d be a bit nicer if the name of the action defaulted to the comment itself.
Also, would it be possible to make the tooltip for a normal action include the comment, if any? I guess I’d just like comments to be a bit more visible than they currently are - you don’t even know whether an action has a comment until you’ve opened it up and gone to the General tab.
It might be sexy to have an option whereby if an action has a comment, it appears in the action list before the action itself, greyed out or something, as if it were source code. Something like:
* //Load all files
* File Iterator
* * // Delete each one
* * Delete File(s)
Changing the name of the action itself has a similar effect, but then you can lose track of what action is actually being performed…
Steve (I’ll shut up soon)
The comment field is actually available on every action, not just the Comment. The Comment action is meant to be renamed so that its description reflects the comment you wish to insert in your build process. That way, you can use it to create the exact structure that you describe in your post.
Take a look at the Async Action Group example projects (included with FB) to see this in action.
You can also use Action Groups for the same thing (as they are also actions which do nothing, with the key difference that Action Groups can have child actions and scripts, and they aren’t a different color by default.)
Also, there is actually a way to see if an action has a comment without opening it up. Take a look at the rightmost column of the Action List frame (in FB 5) and you’ll see a little orange note next to any action which has a comment. Roll your mouse over the note to see a tooltip with the comment text.
Hth.
- Angus
Ah, interesting idea about using action groups as quasi comments. Nice!