Hello, I recall there was a terrible bug in v13 where a constants xlf file inside component resources would seriously mess things up for the host.
I think it is fixed now. also, it might be worth checking the actual content of the file, that it is using UUID-based IDs, not integer enumerations for groups and trans-units, to avoid conflicts. also, only constants with an ID < 15000 are supported by clairvoyance type-ahead, but such IDs are reserved for 4D. On Mar 5, 2020, at 2:06, Doug Hall via 4D_Tech <[email protected]<mailto:[email protected]>> wrote: By the way, if I remove the "Foundation Constants.xlf" file from my parent DB's Resources folder, I can't access the Foundation Constants while developing code. I'm hoping it's simply a duplicate file, and DOESN'T cause problems. ********************************************************************** 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] **********************************************************************
