Re: 4D Write to 4D Write pro Commands
Thank you Steve and Tom. I will move to the discussion forum and start from there. Thanks & Regards, Nisha -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com 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: 4D Write to 4D Write pro Commands
Nisha writes: > I have tried Invoke action but could not get it to work in 4D Write Pro. I think you’re on the right track with INVOKE ACTION. INVOKE ACTION is a tricky concept, but once mastered it should serve you well. >I would recommend moving over to the forums, this list is in its last days. >https://discuss.4d.com I agree with Steve. In the forums, you’ll have almost direct access to the 4D France Write Pro experts like Roland Lannuzel. See you there. Tom Benedict > On Jun 16, 2020, at 00:28, UKVetDerm via 4D_Tech <4d_tech@lists.4d.com> wrote: > > I would recommend moving over to the forums, this list is in its last days. > > https://discuss.4d.com > > Steve > > On 16/06/2020, 08:17, "4D_Tech on behalf of nisshaa2004 via 4D_Tech" > <4d_tech-boun...@lists.4d.com on behalf of 4d_tech@lists.4d.com> wrote: > >Hi All, > >I am in the process of converting 32-bit code to 64 bit and using 4D Write >pro in the process. > >I would like to know if there is a replacement for commands for > >WR ON COMMAND >WR EXECUTE COMMAND >WR ON EVENT > >I have tried Invoke action but could not get it to work in 4D Write Pro. > > >Thanks & Regards, >Nisha Fernando ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com 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: 4D Write to 4D Write pro Commands
I would recommend moving over to the forums, this list is in its last days. https://discuss.4d.com Steve On 16/06/2020, 08:17, "4D_Tech on behalf of nisshaa2004 via 4D_Tech" <4d_tech-boun...@lists.4d.com on behalf of 4d_tech@lists.4d.com> wrote: Hi All, I am in the process of converting 32-bit code to 64 bit and using 4D Write pro in the process. I would like to know if there is a replacement for commands for WR ON COMMAND WR EXECUTE COMMAND WR ON EVENT I have tried Invoke action but could not get it to work in 4D Write Pro. Thanks & Regards, Nisha Fernando -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com ** ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
4D Write to 4D Write pro Commands
Hi All, I am in the process of converting 32-bit code to 64 bit and using 4D Write pro in the process. I would like to know if there is a replacement for commands for WR ON COMMAND WR EXECUTE COMMAND WR ON EVENT I have tried Invoke action but could not get it to work in 4D Write Pro. Thanks & Regards, Nisha Fernando -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com 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: One to One mapping of 4D Write to 4D Write pro
Thanks Tom. Thanks & Regards, Nisha -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com 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: One to One mapping of 4D Write to 4D Write pro
Hi Nisha, I wish there was such a thing, but unfortunately the changes from 4D Write Classic to 4D Write Pro are fundamental and cannot be easily mapped. No longer are there discrete commands which only apply to 4D Write. Instead you will use commands from a range of 4D themes. Also, building a Write Pro UI is an additive process where you add features and tools to Write Pro area rather than subtracting features from Write Classic area. I recommend reviewing all the 4D Write documentation and all the 4D Blog articles. There is lots of help on the 4D Forums from the 4D Engineering Team, such as Roland Lannuzel. HTH, Tom Benedict > On Jun 8, 2020, at 19:15, nisshaa2004 via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi All, > > I am in the process of converting 4D Write to 4D write pro for a 64-bit > application. Is there any resource or tool that could help me with one to > one mapping of 4D Write and 4D Write pro commands and document properties > like wr view style palette, wr view borders palette and so on. > > > Thanks & Regards, > Nisha Fernando ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
One to One mapping of 4D Write to 4D Write pro
Hi All, I am in the process of converting 4D Write to 4D write pro for a 64-bit application. Is there any resource or tool that could help me with one to one mapping of 4D Write and 4D Write pro commands and document properties like wr view style palette, wr view borders palette and so on. Thanks & Regards, Nisha Fernando -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com 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: 4D Write to 4D Write Pro
Tim Nevels: > The only legacy support they promised to provide is to convert legacy 4D > Write documents. And even that does have it´s problems: Line spacing is not preserved. So if you have e.g. a 6 page 4DWrite document it is 8 pages after the conversion :-/ > But I have a crazy idea… > > What if someone created a 4D component that had the major 4D Write Plugin > commands with all the same parameters but as 4D component methods. And each > method accomplished the same results as the plugin command. Would be an instant buy over here. Greetings from Germany, Bernd Fröhlich ** 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: 4D Write to 4D Write Pro
That’s a great idea, Tim (and I remember you showing me that code). It might not be that much work for us to do for the subset of 4D Write commands that we use. Or maybe just create wrapper functions directly in the application that contain a switch telling whether to use 4D Write Pro or 4D Write Amateur. That could be done upfront and then use Global Find and Replace to swap the wrappers for the plugin calls. Still have to figure out the command cross-reference, however, which is the real kicker. I’d love to stay in 32 bit mode that’s soon not going to be possible on the Mac side of things. Richard Wright DataDomain rwri...@datadomainsoftware.com > Date: Wed, 29 Aug 2018 14:38:46 -0500 > From: Tim Nevels > > On Aug 29, 2018, at 2:00 PM,Richard Wright wrote: > >> Is there a cross reference of language commands between 4D Write and 4D >> Write Pro or do we have to all figure it out for ourselves? >> >> I’m mystified as to why wrappers for the old commands could not have been >> created so as to make the move to 4D Write Pro relatively painless. E-node >> did this very nicely when they created the new API for AreaList. All the old >> commands still work because they are internally mapped to the new ones. Why >> can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D >> Write but create a shell plugin that maps all the old commands to the new. >> With Mac Mojave being the last OS to support 32 applications it’s going to >> get serious pretty soon. > > > But I have a crazy idea… > > What if someone created a 4D component that had the major 4D Write Plugin > commands with all the same parameters but as 4D component methods. And each > method accomplished the same results as the plugin command. Then you could > remove the 4D Write Plugin, install the component and run a syntax check to > expose every method and line using the plugin commands. Then you open each > method and force a retokenization to magically change each line to use the > component method instead of the plugin command. That gets you 90% of the way > there without a major code rewrite. > > I did exactly this for 2 clients — different than these 2 clients — when I > upgraded them from v2004 to v11 and 4D dropped the 4D Open for 4D plugin. I > created a “4D Open for 4D SOAP” component that allowed me to not rewrite all > the 4D Open code. It was a lot of work, but in the end it was less than > rewriting all the existing code. And I could use it for 2 clients. The 2 > shared the upgrade cost. > > When I get ready to do the SDI work for 1 client and need to rewrite all the > 4D Write code, I’m going to look into doing the same thing. Might be > possible. Might not be possible. But at least I’ve done it before so probably > a day or two of analysis and prototyping work will tell me if it can be done. > > Tim > > * > Tim Nevels > Innovative Solutions > 785-749-3444 > timnev...@mac.com > * ** 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: 4D Write to 4D Write Pro
One solution for this is to just create a "stub" plugin that does nothing except load properly on 64 bit. Then copy all of the 4D Write resources to it. That way you can keep the old code around as long as you need it for reference. I think I did it by finding a small 64 bit plugin and then replacing the resources with the files from 4D Write. John DeSoi, Ph.D. > On Aug 29, 2018, at 2:38 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Once you have all the code rewritten and tested and working, you can dump the > old code, and you’ll have to when you remove the plugin because all the > plugin command will no longer tokenize. So get ready to delete a bunch of > methods. ** 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: 4D Write to 4D Write Pro
In our case, users have created about 1,500 template documents in 7 languages. I’d be lynched if I didn’t provide a path to convert them. Paul > On 29 Aug 2018, at 21:56, Richard Wright via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > That’s what I was afraid of. Does it not occur to anyone at 4D that people > have existing code to manipulate 4D Write documents and that that code has to > be rewritten to work with 4D Write Pro? The lack of a command cross reference > makes the process unnecessarily difficult and maybe you end up 90% through > the process only to find out that a certain functionality has not been > retained in “Pro". How hard could it be to write such a thing? After all, > when 4D Write Pro was being written, surely the starting point would have > been to retain all existing features and then give us all the great new > things. So you create a list of existing commands and then you check them off > as those functions are rewritten in “Pro”. How else could you know that you > haven’t missed something? Reading a bunch of blogs is not all the same thing > as an accurate cross reference. > > > Richard Wright > DataDomain > rwri...@datadomainsoftware.com > > > >> Date: Wed, 29 Aug 2018 18:57:19 + >> From: Vance Villanueva >> >> Hi Richard, >> >> 4D Write Pro is a newly developed architecture. There are no cross >> references of 4D Write Pro commands from 4D Write. We have resources to >> convert 4D Write docs to 4D Write Pro. Also, we have resources of 4D Write >> Pro in doc.4d.com, blog.4d.com, and kb.4d.com for the transition from 4D >> Write. >> >> Regards, >> >> Vance Villanueva >> >> >> >> >> -Original Message- >> From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Richard >> Wright via 4D_Tech >> Sent: Wednesday, August 29, 2018 9:45 AM >> To: 4d_tech@lists.4d.com >> Cc: Richard Wright >> Subject: 4D Write to 4D Write Pro >> >> Is there a cross reference of language commands between 4D Write and 4D >> Write Pro or do we have to all figure it out for ourselves? >> >> I’m mystified as to why wrappers for the old commands could not have been >> created so as to make the move to 4D Write Pro relatively painless. E-node >> did this very nicely when they created the new API for AreaList. All the old >> commands still work because they are internally mapped to the new ones. Why >> can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D >> Write but create a shell plugin that maps all the old commands to the new. >> With Mac Mojave being the last OS to support 32 applications it’s going to >> get serious pretty soon. >> >> >> Richard Wright >> DataDomain >> rwri...@datadomainsoftware.com > > > > > ** > 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 > ** ** 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: 4D Write to 4D Write Pro
That’s what I was afraid of. Does it not occur to anyone at 4D that people have existing code to manipulate 4D Write documents and that that code has to be rewritten to work with 4D Write Pro? The lack of a command cross reference makes the process unnecessarily difficult and maybe you end up 90% through the process only to find out that a certain functionality has not been retained in “Pro". How hard could it be to write such a thing? After all, when 4D Write Pro was being written, surely the starting point would have been to retain all existing features and then give us all the great new things. So you create a list of existing commands and then you check them off as those functions are rewritten in “Pro”. How else could you know that you haven’t missed something? Reading a bunch of blogs is not all the same thing as an accurate cross reference. Richard Wright DataDomain rwri...@datadomainsoftware.com > Date: Wed, 29 Aug 2018 18:57:19 + > From: Vance Villanueva > > Hi Richard, > > 4D Write Pro is a newly developed architecture. There are no cross > references of 4D Write Pro commands from 4D Write. We have resources to > convert 4D Write docs to 4D Write Pro. Also, we have resources of 4D Write > Pro in doc.4d.com, blog.4d.com, and kb.4d.com for the transition from 4D > Write. > > Regards, > > Vance Villanueva > > > > > -Original Message- > From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Richard > Wright via 4D_Tech > Sent: Wednesday, August 29, 2018 9:45 AM > To: 4d_tech@lists.4d.com > Cc: Richard Wright > Subject: 4D Write to 4D Write Pro > > Is there a cross reference of language commands between 4D Write and 4D Write > Pro or do we have to all figure it out for ourselves? > > I’m mystified as to why wrappers for the old commands could not have been > created so as to make the move to 4D Write Pro relatively painless. E-node > did this very nicely when they created the new API for AreaList. All the old > commands still work because they are internally mapped to the new ones. Why > can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D > Write but create a shell plugin that maps all the old commands to the new. > With Mac Mojave being the last OS to support 32 applications it’s going to > get serious pretty soon. > > > Richard Wright > DataDomain > rwri...@datadomainsoftware.com ** 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: 4D Write to 4D Write Pro
On Aug 29, 2018, at 2:00 PM,Richard Wright wrote: > Is there a cross reference of language commands between 4D Write and 4D Write > Pro or do we have to all figure it out for ourselves? > > I’m mystified as to why wrappers for the old commands could not have been > created so as to make the move to 4D Write Pro relatively painless. E-node > did this very nicely when they created the new API for AreaList. All the old > commands still work because they are internally mapped to the new ones. Why > can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D > Write but create a shell plugin that maps all the old commands to the new. > With Mac Mojave being the last OS to support 32 applications it’s going to > get serious pretty soon. Hi Rich, You have to figure it out for yourself. And you have to rewrite — from scratch — all existing 4D Write Plugin code. No direct one-to-one- command replacement. Some commands not available now. Some commands now require multiple 4D commands to accomplish the same thing. They said that this was a project where they decided from the very beginning to not provide any programming language legacy support. None. Zero. The only legacy support they promised to provide is to convert legacy 4D Write documents. You are on your own dealing with any programming code. This is the general takeaway I get with this issue. The 4D Write Plugin still works and can coexist with 4D Write Pro. So you can start migrating — which in this case is rewrite it from scratch — and continue to use your old code. Once you have all the code rewritten and tested and working, you can dump the old code, and you’ll have to when you remove the plugin because all the plugin command will no longer tokenize. So get ready to delete a bunch of methods. The only reason to stop using 4D Write Plugin is if you want 64bit compatibility. That’s basically it. If you can live with 32bit 4D Client you are fine. But if you want to run 64bit 4D Client and use 4D Write, you must switch to 4D Write Pro. For one of my clients they are excited about getting SDI mode on Windows. Everyone has multiple monitors and they have wanted this for a long time. Now they can have it. But they are the 90 user 4D Write Plugin client. So to get SDI you MUST go to 64bit compiled version. So they are going to have to pay for the 4D Write code rewrite just so they can get SDI. So they are swallowing it, but not super happy about it. Crazy thing is that to get SDI all you really need to do is check a checkbox and recompile. But if you use 4D Write, then it requires a lot more work. As they say… it is what it is. But I have a crazy idea… What if someone created a 4D component that had the major 4D Write Plugin commands with all the same parameters but as 4D component methods. And each method accomplished the same results as the plugin command. Then you could remove the 4D Write Plugin, install the component and run a syntax check to expose every method and line using the plugin commands. Then you open each method and force a retokenization to magically change each line to use the component method instead of the plugin command. That gets you 90% of the way there without a major code rewrite. I did exactly this for 2 clients — different than these 2 clients — when I upgraded them from v2004 to v11 and 4D dropped the 4D Open for 4D plugin. I created a “4D Open for 4D SOAP” component that allowed me to not rewrite all the 4D Open code. It was a lot of work, but in the end it was less than rewriting all the existing code. And I could use it for 2 clients. The 2 shared the upgrade cost. When I get ready to do the SDI work for 1 client and need to rewrite all the 4D Write code, I’m going to look into doing the same thing. Might be possible. Might not be possible. But at least I’ve done it before so probably a day or two of analysis and prototyping work will tell me if it can be done. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.com * ** 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: 4D Write to 4D Write Pro
Hi Richard, 4D Write Pro is a newly developed architecture. There are no cross references of 4D Write Pro commands from 4D Write. We have resources to convert 4D Write docs to 4D Write Pro. Also, we have resources of 4D Write Pro in doc.4d.com, blog.4d.com, and kb.4d.com for the transition from 4D Write. Regards, Vance Villanueva -Original Message- From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Richard Wright via 4D_Tech Sent: Wednesday, August 29, 2018 9:45 AM To: 4d_tech@lists.4d.com Cc: Richard Wright Subject: 4D Write to 4D Write Pro Is there a cross reference of language commands between 4D Write and 4D Write Pro or do we have to all figure it out for ourselves? I’m mystified as to why wrappers for the old commands could not have been created so as to make the move to 4D Write Pro relatively painless. E-node did this very nicely when they created the new API for AreaList. All the old commands still work because they are internally mapped to the new ones. Why can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D Write but create a shell plugin that maps all the old commands to the new. With Mac Mojave being the last OS to support 32 applications it’s going to get serious pretty soon. Richard Wright DataDomain rwri...@datadomainsoftware.com ** 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 ** ** 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 **
4D Write to 4D Write Pro
Is there a cross reference of language commands between 4D Write and 4D Write Pro or do we have to all figure it out for ourselves? I’m mystified as to why wrappers for the old commands could not have been created so as to make the move to 4D Write Pro relatively painless. E-node did this very nicely when they created the new API for AreaList. All the old commands still work because they are internally mapped to the new ones. Why can’t this be done for 4D Write Pro? If it’s truly ready to go, scrap 4D Write but create a shell plugin that maps all the old commands to the new. With Mac Mojave being the last OS to support 32 applications it’s going to get serious pretty soon. Richard Wright DataDomain rwri...@datadomainsoftware.com ** 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: 4D Write to 4D Write Pro, Moving and using templates (Was: WR Count equivalent in 4D Write Pro)
Step 1 should have read "Using WR Count and WR GET PICTURE IN PAGE INFO" > On Jun 12, 2018, at 11:41 AM, JOHN BAUGHMAN wrote: > > 1. In 4D Write store the position and dimensions of each anchored picture > place holder into a c_object. > Using WR Count and WR SELECT PICTURE IN PAGE > John Baughman 1331 Auwaiku Street Kailua, Hawaii 96734 (808) 262-0328 john...@hawaii.rr.com ** 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 **
4D Write to 4D Write Pro, Moving and using templates (Was: WR Count equivalent in 4D Write Pro)
If anyone was following the original thread, the underlying problem was how to address Anchored Picture place holders when converting a 4D Write template to 4D Write Pro. Beyond that, how to populate the place holder pictures when the 4D Write Pro template is used. My last post left this problem as undoable in anything prior to v17. I have since figured out a way to do it in v16 and thought I would post my solution if anyone is in fact interested. Moving the Template from 4D Write to 4D Write Pro… 1. In 4D Write store the position and dimensions of each anchored picture place holder into a c_object. Using WR Count and WR SELECT PICTURE IN PAGE 2. Copy the 4D Write area to an off screen area and delete all the anchored picture placeholders. 3. Convert the off screen area to 4D Write Pro. 4. Using the c_object created in step 1 recreate in the new 4D Write Pro are all the anchored picture place holders with WP Add Picture. Store the picture reference returned by WP Add Picture in the c_object created in step 1. Saving the 4D Write Pro template 1. Store the c_object in the template record. 2. Using the picture references stored in the c_object, delete all the anchored picture place holders 3. Save the record Opening the template in the Template table. 1, Using the saved c_object, recreate all the anchored picture place holders with WP Add Picture. Update the picture references in the c_object with the newly created anchored pictures references as returned by WP Add Picture Adding a 4D Write Pro template in a 4D Write Pro document for a patient in the patient table. 1. Using the saved c_object recreate all the anchored picture place holders with WP Add Picture. Update the picture references in the c_object with the newly created anchored pictures references as returned by WP Add Picture 2, Using the picture references in the c_object, populate the place holder pictures with the photos from the patient record. Hope this helps anyone struggling with a similar situation. John John Baughman 1331 Auwaiku Street Kailua, Hawaii 96734 (808) 262-0328 john...@hawaii.rr.com > On Jun 10, 2018, at 9:06 PM, JOHN BAUGHMAN wrote: > > > >> On Jun 10, 2018, at 8:37 PM, Keisuke Miyako via 4D_Tech >> <4d_tech@lists.4d.com <mailto:4d_tech@lists.4d.com>> wrote: >> >> I must say it would be difficult to manipulate an existing anchored image >> without Get elements or Get element by id (v17). > > > You assumed correctly in that these are anchored pictures. I have discovered > as you have pointed out that the reference returned by Add picture is > destroyed when the record is unloaded. I think you have confirmed for me that > there is no way currently to use picture place holders in a 4D Write Pro > template as I did in 4D Write. > > I will give this a bit more thought, but I am about to give up on this part > of my attempt to upgrade my client to v16. Since it is way to early to deploy > v17, I will have to tell them they will have to wait until we upgrade to v17 > to move any of their photo templates to Pro or create any new ones. Of course > this prevents me from moving them to 64 bit until then as well. > > BTW, another thing I cannot find is any way to provide a means for end users > to insert 4D expressions as they can in 4D Write. I could write a dialog for > this, but it already exists in 4D so why not provide the same functionality > out of the box? > > John > > > > John Baughman > 1331 Auwaiku Street > Kailua, Hawaii 96734 > (808) 262-0328 > john...@hawaii.rr.com <mailto:john...@hawaii.rr.com> ** 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 **