3 Symbol search and the search result box
4 Automatic code folding for search patterns
7 Working with the tree view folder structure / include structure
2 Moving sets in rows and columns
3 Selection of elements in the sets
5 Editing element names in rows and columns
7 Changing element names (Uels)
8 Adding a new symbol to the gdx file
12 Statistics and comparison of values
12.1 How to activate statistic functions
12.2 Adding percentiles to statistics
There are 2 ways to show the file structure - one is the "Folder Structure" and one the "Include Structure".
The folder structure shows the order of the folders and files on your hard disk, while the include structure shows the order of $include statements in the files.
In the folder structure, you can choose the file extensions to be shown. In this example, gms, gdx and lst files are selected.
Some of the files are marked blue, some orange. The reason will be explained in the next section, the Include Structure.
In the include structure we see that there are 2 base files: transport.gms (blue) and Untitled_4.gms (orange).
In transport.gms an $include statement calls Subfile1.gms.
From Subfile1.gms, 2 further files are called - SubSubFile1 and SubSubFile2.gms.
From SubSubFile2.gms the subfile Untitled_4.gms is called.
The reason of using base files is as follows:
Imagine we are working with SubFile1.gms. In SubFile1.gms we use a set i, which is declared in transport.gms. If we don't consider the information of transport.gms, this set i will be adressed without being declared. But because SubFile1.gms is the base file, the compiler always runs the base file and its include files to find errors and symbol declarations.
But we see, that Untitled_4 is used in 2 base files. So, how would GMS-Manager handle this? We will see in the description of the GMS-Manager.