Re Subject: question about PROCESS 4D TAGS 4d v13

ked this time. I tried to figure out where the problem might have slipped in but could find no code differences between the new Project2 and the 'old' Project2. It was strange, the loop count was correct and in debug mode I could see the values. But when Process 4D Tags would produ

Re: question about PROCESS 4D TAGS 4d v13

Hi Ernie, Is there a typo or are you using two arrays? aTxtHeaders1 and aTxtHeaders If so, you should use the array variable which you use as loop counter as index for your arrays too. HTH Koen > Op 22 mei 2020, om 00:47 heeft ernie hilgers via 4D_Tech >

Re: question about PROCESS 4D TAGS 4d v13

Is check array Sent from my iPhone > On May 21, 2020, at 6:47 PM, ernie hilgers via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi All, > Mac 10.13, 4D v13 > > Working with PROCESS 4D TAGS and testing it baffles me because, > I created a 'template' html do

question about PROCESS 4D TAGS 4d v13

Hi All, Mac 10.13, 4D v13 Working with PROCESS 4D TAGS and testing it baffles me because, I created a 'template' html document, that gets opened by 4D which contains this code: In a 4D method that runs this aTxtHeaders array is filled with 7 text strings

RE: What would cause PROCESS 4D TAGS to "not work" - SOLVED

Thanks to all who responded. Tim Penner and Charles Miller - It was the compatibility setting "Use 4DVAR Comments instead of Brackets" This explains why a new database worked correctly. You can not even access the option there. Since the structure has been through multiple versions of 4D

Re: What would cause PROCESS 4D TAGS to "not work"

Check you preference compatibility and make sure you have correct options checked. Also make sure method is available for 4d tags Regards Chuck Sent from my iPhone > On May 23, 2017, at 5:07 PM, Ed Hammond via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > PROCESS 4D TAGS

Re: What would cause PROCESS 4D TAGS to "not work"

Try your test using process variables, not local variables. PROCESS 4D TAGS was changed as of version 14 so that it had to use process variables (at least in Interpreted mode). > Compatibility note: In previous versions of 4D, local variables defined in > the calling context could be ac

What would cause PROCESS 4D TAGS to "not work"

PROCESS 4D TAGS experts! I was working on an image viewer involving a local html file and using PROCESS 4D TAGS to substitute a URL with the source image from a remote system. I was working on a local copy of our application (4D v15.4, Mac OS 10.11.6) to develop the viewer before moving

Re: PROCESS 4D TAGS [Solved]

Thanks Jim. So based on your post, I tried it with Select Document and as you note it works. Then I changed the path name to use the Folder Separator constant even though “:” (semi-colon) seemed to be working fine and voila, the code works. Don’t know why but it works. Mitch

Re: PROCESS 4D TAGS

if the document is not correctly loaded, as others have speculated: 1. given this is Mac, could there be a hidden file extension? 2. Given no encoding is not specified, could it be saved in UTF-16? Document to text doesn't update OK, the only way to know that it worked is to check that the

Re: PROCESS 4D TAGS

.1045681.n5.nabble.com/PROCESS-4D-TAGS-tp5751717p5751731.html Sent from the 4D Tech mailing list archive at Nabble.com. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com

Re: PROCESS 4D TAGS

How do you know PROCESS 4D TAGS is failing? Have you confirmed that the process variable "tTemplate" actually contains your template? In other words, does “Document to text” successfully retrieve the template? When the command “Document to text” encounters an error, the com

re: PROCESS 4D TAGS

BTW the template is: “ ” Randy, I tried the compatibility option but that didn’t do it. Mitch ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html

Re: PROCESS 4D TAGS

> > HTML Template: > > > > > > > > > > > > Method: > > C_TEXT(tHTML;tTemplate;$tPathname;tData) > $tPathname:=Get 4D folder(Current resources folder)+"Templates"+":"+"Test > Template.html" > tTemplate:=Document to text($tPathname) >

PROCESS 4D TAGS

v14 OSX HTML Template: Method: C_TEXT(tHTML;tTemplate;$tPathname;tData) $tPathname:=Get 4D folder(Current resources folder)+"Templates"+":"+"Test Template.html" tTemplate:=Document to text($tPathname) tData:="Hello There"

Re: PROCESS 4D Tags

the 12.1 addendum specifically mentions Char(1) in the context of 4DVAR vs 4DTEXT. http://docs2.4d.com/4Dv12/4D/12.1/Renaming-4D-HTML-tags.300-519792.en.html but there is no word on 4DSCRIPT. so to be specific, I guess I should have said, Char(1) in the context of 4DVAR is deprecated since

Re: PROCESS 4D Tags (Sujit Shah)

> Am 21.10.2016 um 01:58 schrieb 4d_tech-requ...@lists.4d.com: > > Thanks Ortwin. I am escaping each element of the array by using char(1) > > > I eventually ended up using > >

Re: PROCESS 4D Tags

> Le 21 oct. 2016 à 02:25, Keisuke Miyako a écrit : > > Char(1) was deprecated in v12.2 > http://docs2.4d.com/4Dv12/4D/12.4/4D-HTML-Tags.300-977162.en.html > > 4DHTML succeeded 4DHTMLVAR in order to invalidate the Char(1) trick without > breaking compatibility. > >

Re: PROCESS 4D Tags

Char(1) was deprecated in v12.2 http://docs2.4d.com/4Dv12/4D/12.4/4D-HTML-Tags.300-977162.en.html 4DHTML succeeded 4DHTMLVAR in order to invalidate the Char(1) trick without breaking compatibility. Char(1) was useful in contextual mode (also deprecated in v12), but could become a liability in

Re: PROCESS 4D Tags

On Thu, Oct 20, 2016 at 5:16 PM, Sujit Shah wrote: > Well: > > 1) I "read" it in the manual yesterday :-) > > And > > 2) It seems to work > Can't argue with that, eh? -- Douglas von Roeder 949-336-2902 **

Re: PROCESS 4D Tags

Well: 1) I "read" it in the manual yesterday :-) And 2) It seems to work On Fri, Oct 21, 2016 at 11:10 AM, Douglas von Roeder wrote: > On Thu, Oct 20, 2016 at 5:02 PM, David Adams wrote: > > > A bell is ringing in the back of my head...is the

Re: PROCESS 4D Tags

On Thu, Oct 20, 2016 at 5:02 PM, David Adams wrote: > A bell is ringing in the back of my head...is the Char(1) trick deprecated? > I had a quick look at the docs and couldn't figure it out...does anyone > else > remember? > David: Yeh, that caught my eye, too. I seem to

Re: PROCESS 4D Tags

Thanks Ortwin. I am escaping each element of the array by using char(1) I eventually ended up using href="" $tInput:=$tInput+"" $tInput:=$tInput+"" $tInput:=$tInput+"" ... PROCESS 4D TAGS($tInput;$tOutput;"StartDate=";$tStartDate;" Star