Re: Constants vs IP vars

Every thing is so much easier using 4D methods rather than an editor! I can install my methods (tested and working for over 20 years) for the price of 1 days' work:) On Fri, Sep 16, 2016 at 5:37 PM, Jim Dorrance wrote: > Here is 1 of the methods that handles a theme: >

Re: Constants vs IP vars

Here is 1 of the methods that handles a theme: //JD20141120 //Method: Ks_PaperSizes ($patResourcePaths;$pnResID;$pnIndex;$pnFamily;$pnValue;$patConstants) //Description: C_TEXT($1;$tDomRoot) //DOCUMENT ROOT C_POINTER($2;$pnResID) //THE RES ID POINTER C_POINTER($3;$pnIndex) //THE ITEM

Re: Constants vs IP vars

Here is my Ks method: //Method: Ks ($bConfirm) //Description: C_BOOLEAN($1;$bConfirm) If (Count parameters>0) $bConfirm:=$1 Else $bConfirm:=True End if //XLIFF DOCUMENT NAME AND ROOT NAME C_TEXT($tXLIFF_FileName;$tXLIFF_DomRoot) $tXLIFF_FileName:="ksLabels"

Re: Constants vs IP vars

And constants should be part of the language, not some weird resourcy-thing that you have to maintain in a special editor. > On Sep 16, 2016, at 4:39 AM, David Adams wrote: > > The real problem is that 4D hasn't made constants first-class citizens. > Given that the feature

Re: Constants vs IP vars

> Le 16 sept. 2016 à 02:38, David Adams a écrit : > > 4D should have a constants editor, just like it has the list editor. Hi David, I do agree… Using constants is really uneasy when working in C/S. Since a long time I took a bad habit, I use functions:

Re: Constants vs IP vars

David, All good points. > 4D should have a constants editor, just like it has the list editor… Agreed. > … > I now use 4DPop for this feature (and nothing else… I tried using 4DPop way back (4D 2003, 2004, v11, pre-2003 ?) - can’t remember but it was not long after 4DPop became