Chip, you’re right. For my purposes, that isn’t an issue, but your approach is perhaps neater.
Jeremy > On 11 Nov 2019, at 16:43, Chip Scheide <[email protected]> wrote: > > Jeremy, > Just to be clear > > your code will *only* work if both the component and host are > interpreted. > for me, one of the advantages of using a component is being able to > compile it. > > For that circumstance you will need to have some other means to inject > code. > as I said I use text files in the resources folder, this is an > abbreviated bit of code that runs ON EXIT of the component (when > closing development). > > then you can import/inject the code from the component even if the > component is compiled. :) > > ARRAY TEXT($Methods;0) > > If (Application type=4D Local mode) > //methods to be injected into host system > //done this way to allow easy updating of the list > APPEND TO ARRAY($Methods;<method_name_to Export>) > // repeated for each method to export > > //insure that the most up to date versions of > // the methods to be injected are saved to disk > shtdwn_Write_Code_to_Disk (->$Methods) > > > On Mon, 11 Nov 2019 16:16:46 +0000, Jeremy Roussak wrote: >> Exactly. FWIW, this is my code. > We have done so much, with so little, for so long; > We are now qualified to anything with nothing <sigh> > - unknown ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
