This page annotates some common FAQs for the Graphex Application.
The Graphex application is written in way to allow you to create 'child' graphs (or 'subgraphs'). These are effectively the same thing as creating your own node. You can execute these graphs by using the 'Execute Graph' node.
Graphex is also extendable by other developers. If you are familar with the python3 programming language, you can read this document about creating a plugin for Graphex. Please note that this particular document is not intended for the same audience as the rest of Graphex's documentation.
You probably need to refresh the node. The easiest way to do this is to right-click on it with your mouse and select 'Refresh' in the dropdown context-menu.
If the node itself is showing the color 'red' anywhere (input field, icon, sockets), then you have an error that you need to resolve.
The best way to keep a graph looking 'clean' and minimal is by using less nodes to accomplish the same logic. One of the easiest ways to achieve that goal is by making heavy use of 'variable' nodes and the 'Execute Graph' node. Also make use of lists when possible and iterate over them in a loop. If you haven't already, you can read about 'variable' nodes, 'list' nodes, and 'loop' nodes in the document about special nodes. By striving to make your graph 'cleaner', you are also making use of good programming practices.
The document on the 'Execute Graph' node gives an example graph that is a good starting point to understanding a graph that follows this 'clean' pattern. I have renamed the 'child' graph from that example to 'format_and_print'. I have added on to the example by:
Assume as we continue to create 'sentences' that we want to 'format and print': we notice that there is a common pattern amongst all the sentences. All of our sentences are adding our name somewhere to the sentence and printing it. We can condense a large number of sentences we want to 'format and print' into a list and then iterate over the list:
One thing to consider is that you don't always need to use a variable. The first example should absolutely use a variable because your name is mentioned in more than one place in the graph. In the second example, your name is only referenced from the loop body. If this is the only place we intend to use that variable, then you should write your name into an input field on the 'Execute Graph' node instead (or provide your name as a graph input on the CLI). This saves resources on the computer that is executing your graph/program. You should also create a variable for the list of 'sentences' if they are used in more than one place.
Whether or not you should use variables and subgraphs is going to change throughout the lifecycle of developing the graph. Sometimes you don't know if a value needs to be reused yet. Going back and 'cleaning' up a graph without changing its functionality is called refactoring (programming jargon).
The path to the current configuration file in use by the server can be found in the client UI's Menu Bar via 'Help' -> 'About Graphex'.
Your favorite nodes are stored in browser storage. They will only persist on the same server in the same browser. Clearing stored information in your browser cache may also delete all favorited nodes.
If you have plugins installed, they may provide their own documentation pages. If any of your installed plugins have developer provided documentation, links to their documentation pages will appear on the dedicated page for plugin documentation.
At the time of updating this document, there are well over 1000 different nodes in GraphEx. It is unreasonable to write documentation for every new node that is added. That being said, there are a couple of different places you can reference to learn about nodes:
