Braza wrote:Good hint, Braza!
I recall dealing with this a long time ago...
If I remember well, I managed to do this with requesting folder names in the loaded library and file I/O operations.
Hope this helps.
EXTERNAL FILE DEPENDENCECheers,
FILE_DEPENDENCE "name1" [, "name2", ...]
You can give a list of external files on which your GDL script depends on. File names should be constant strings.
All files specified here will be included in the archive project (like constant macro names used in CALL statements and constant picture names
used in various GDL commands). The command works on this level only: if the specified files are library parts, their called macro files will
not be included.
The command can be useful in cases when external files are referenced at custom places in the GDL script, for example: ADDITIONAL_DATA
file parameters, data files in file operations.
Braza wrote:This, .. uhm... doesn't help me at all.
Its a new command called FILE_DEPENDENCE.
Braza wrote:Well, that is my intention.
Ok. I got your point.
Then: Why not letting the end user define the name of the macro as a string parameter?
GDL wrote:Try exchanging "IES_FILES" for "GSM_FILES" and storing it in "gsm_files_list"?
n = APPLICATION_QUERY ("LIBRARY_MANAGER", "IES_FILES", ies_files_list)
This command returns the list of file names with .ies extensions loaded with the active libraries.
Braza wrote:Yeah but that is the feature I want. Right now that doesn't work 😉
Try exchanging "IES_FILES" for "GSM_FILES" and storing it in "gsm_files_list"? :idea:
GDL wrote:Hope this helps.
GDL FILE MANAGER I/O ADD-ON
The GDL File Manager In-Out Add-On allows you to scan a folder for the contained files/subfolders from a GDL script.
Specify the folder you would like to scan by using the OPEN command.
Get the first/next file/folder name in the specified folder by using the INPUT command.
Finish folder scanning by using the CLOSE command.