Story editor

Description

The Story editor is used to browse, edit and build Osiris scripts.

Building the story

There are multiple options to build the story under "File".

The most important one is Generate Definitions and Build. This will build all necessary files for your story to work.

Other options are:

• Build: Only build story. This suffices if you know there have been no function definition changes.
• Build and reload: To see your changes in the editor, you'll have to reload the level after building. This option does that auto-magically for you!
• Generate Definitions and Build: As mentioned, the most thorough option. Creates all necessary files.
• Generate Definitions, Build and Reload: Again, if you want to see the changes in editor, this prompts a level reload.
• Generate Definitions: Only generate function definitions. This is useful to get code completion functionality without rebuilding story.

Code editing helper functionality

• Code completion is available via ctrl-space. Note that in case of user-defined queries, code completion will add a (wrong) "__DEF" suffix that you will have to delete again.
• When you are in the parameter list of a function call, the editor shows the parameter definitions at the top of the code editing window.

Known limitations

• Every pane in the editor gets its own "Find" dialog box. However, if you press ctrl-f while a "Find" dialog box for this pane was already open, this "Find" dialog box will not regain focus. Either always close the Find dialog box after searching for something (e.g. by pressing Esc), or click on it for it to regain focus. The global search (ctrl-shift-f) dialog does not suffer from this issue.
• The the parameter list shown at the top of the window will always list the parameters of the last defined overload in Story. This means that other definitions of the same function with more parameters may exist.