Keisuke, I see what you are saying, however, how is this accomplished? Do you just generate a UUID, and manually assign it?
4DPop does not do this sort of assignment (UUIDs) for the IDs. Yesterday, while trying to diagnose and resolve the problems I was having, I did try to see if there were individual Konstant ID conflicts by manually numbering the Konstant IDs. However when next I used 4DPop to manipulate the Konstants file the IDs were all changed to be sequential values, (ID = k_1 , k_2, k_3 ...) ----- Using a UUID as a group name would have solved about 1/2 of my problems from yesterday; the group name (Menus) I choose would not have had some (underlying) conflict. BUT, when I look at the Konstants in the 4D explorer, my group names appear. (ex: group name = "Freds_Konstants", there is an entry in the Konstants area showing 'Freds_Konstants') This makes it (similar to 4D's native Konstants) easy to find and recognize the Konstants group for examination. Using a UUID for the group name does not seem 'intuitive' in this respect. Am I missing something? Thanks Chip On Tue, 26 Jun 2018 23:58:31 +0000, Keisuke Miyako via 4D_Tech wrote: > when defining constants.xlf it's really important to use UUID to > avoid conflicts, > since you have no idea of what other plugin, components (private and > public) have defined and will define after yours is loaded. > > something like: > >> <?xml version="1.0" encoding="UTF-8" standalone="no" ?> >> <xliff version="1.0" xmlns:d4="http://www.4d.com/d4-ns";> >> >> <header> >> <note>Common Crypto plugin</note> >> </header> >> >> <group resname="themes"> >> <trans-unit id="30075EDF927B4ADCA4FB6968D37ABE4C" >> resname="30075EDF927B4ADCA4FB6968D37ABE4C" translate="no"> >> <source>Crypto output format</source> >> </trans-unit> >> </group> >> >> <group d4:groupName="30075EDF927B4ADCA4FB6968D37ABE4C" restype="x-4DK#"> >> <trans-unit d4:value="0:L" id="30075EDF927B4ADCA4FB6968D37ABE4C.1"> >> <source>Crypto HEX</source> >> </trans-unit> >> </group> >> >> </xliff> > > notice how group@d4:groupName is a UUID and trans-unit@id and id is > its derivative. > notice also the use of a type specifier (:L for longint) in > trans-unit@d4:value > > > > > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
