I have mentioned this technique in a few articles and I felt it deserved an article of its own. I call it “Overloading FGLLDPATH” but the name is a bit of misnomer as it does not involve changing FGLLDPATH.
Environment variables such as FGLLDPATH, FGLRESOURCEPATH define a search path to use for finding certain files.
The last place the Genero runtime searches for program modules (.42m files) is $FGLDIR/lib. This is where standard Genero functionality resides. If in the search path defined by $FGLLDPATH there is a .42m file with the same file name as one that is in $FGLDIR/lib, it will be found and used instead of the one in $FGLDIR/lib. Similar logic applies for files found by searching the path defined by $FGLRESOURCEPATH.
You can potentially utilise these look up rules to override some of the standard files shipped in $FGLDIR/lib. Reasons you might do this include to give your application a consistent User Interface where our standard dialogs look different from the rest of your dialogs.
Read more at
https://4js.com/ask-reuben/ig-205/
Sign in for full access
Help
