Search is based on keyword.
Ex: "Procedures"
Do not search with natural language
Ex: "How do I write a new procedure?"
Modo Markup
Modo Markup is a simplified text markup feature that exposes some Rich Text features for tooltips and message tables. It supports tooltips in command dialogs and forms, and any message table lookups.
Syntax
*text* | Bold |
_text_ | Italics |
`text` | Fixed-width font |
~text~ | Small font |
==text== | Heading (bold and centered) |
* text |
Bullet Note: There is a space after the asterisk. |
![icon][iconResource] | Icon Resource |
![inputevent][eventHash] | Key assigned to the an event hash. Hash format is the same as is stored in the config. |
![inputcommand][commandString] | Key assigned to the command string in the global input map |
\ | Escape character. Any character typed after this is not parsed, and inserted directly. |
{{{...}}} | Content inside the curly braces is not parsed. |
Restrictions
• Font styles cannot be nested. You can't do *_text_* to get a bold italics. This is a limitation of the underlying rich text system.
• ![][] inserts can be wrapped in the font styles for situations where you want to display input mappings or icons with bold or italic text, for example.
• Fixed-width fonts are slightly offset, due to the underlying implementation.
• inputcommand key assignments are always found in the global map, not in view-specific maps.
• Special hidden Rich Text codes are inserted into parsed strings, which means that they can be parsed a second time without issues. However, these hidden codes can result in unprintable characters being displayed for clients that don't support Rich Text, such as window titles, edit fields, or OpenGL. Most internal code detects and deletes these codes where necessary.
Sorry you didn't find this helpful
Why wasn't this helpful? (check all that apply)
Thanks for taking time to give us feedback.