Skip to content

Bottom level of Actions assumed by editing tool to be Success/Fail #93

@bluestar514

Description

@bluestar514

Imagine you had an action hierarchy that looked something like this:

- ABSTRACT_ACTION (ex: BE_A_GOSSIP)
-- MID_LEVEL_ABSTRACT_ACTION (ex: ASK_ABOUT)
--- concrete_action (ex: ask_about_day)
--- concrete_action (ex: ask_about_family)

With this structure the editor will show only one of the two concrete actions, I believe because it assumes it is a success/fail structure (this is true even if there are more than two concrete actions).

On the other hand, if it is structured like this:

- ABSTRACT_ACTION (ex: BE_A_GOSSIP)
-- MID_LEVEL_ABSTRACT_ACTION (ex: ASK_ABOUT_DAY)
--- concrete_action (ex: ask_about_day)
-- MID_LEVEL_ABSTRACT_ACTION (ex: ASK_ABOUT_FAMILY)
--- concrete_action (ex: ask_about_family)

both lowest level actions will appear in the editor.

domainMultipleLowest.zip - shows an example of the first structure (consider the actions under the abstract action BEAGOSSIP)
domainMultipleMidlevel.zip - shows an example of the second structure (again, look for BEAGOSSIP)

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions