Re: Command(s) with column and C-number

Hi Arnaud, > On 21 Nov 2019, at 22:08 AEDT, Arnaud init5 imap via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > beside code sharing, it's important to tokenise your own formulas if they > embed commands or constants "as text". Thanks for the additional information. Cheers

Re: Command(s) with column and C-number

Hi Arnaud, You're absolutely right. Thanks to remind me it and figure out this! - Patrick EMANUEL Administrator www.association-qualisoft.eu (Soft1002, Simply Asso & QS_Toolbox) -- Sent from:

Re: Command(s) with column and C-number

> Le 21 nov. 2019 à 07:56, Jörg Knebel via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Thanks Patrick. Hi Jörg, beside code sharing, it's important to tokenise your own formulas if they embed commands or constants "as text". For example, a calculated column in a listbox using hardcoded

Re: Command(s) with column and C-number

Thanks Patrick. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com

Re: Command(s) with column and C-number

Hi, I would say that it helps you if you share code with someone which is not working with the same 'language', or between different version of 4D. Sometimes, commands are renamed and using the token (:C) force to update the syntax. It is also the same for constants ;-) Patrick -

Command(s) with column and C-number

Hi All, What is the benefit/advantage of using commands followed by a column and a (unique) number? Examples: OB Get:C1224(…) C_LONGINT:C283 Open window:C153(…) Thanks Cheers Jörg ** 4D Internet Users