Jim: I may have missed is, but what make and model did you buy to integrate this way. It sounds like the manufactures were ensuring it would work on the MacOS from within other applications as well as on Windows. That is nice.
Thanks Jody Bevan > On Jun 19, 2019, at 10:10 AM, Jim Crate via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > It’s pretty simple, the signature pad had an app that could be launched to > collect a signture. > > The app supported a user-specific properties file, which I copied into the > correct place from the Resources folder. These properties also affected > launching the signature app from Scriptel’s Adobe Reader plugin for PDF > signatures. The app also supported being launched with command line options > that could override those properties, and one of the options forced it to > quit after collecting a signature or canceling. If you launch with the ‘open’ > command, LEP will return immediately, but I executed the binary buried in the > application package (Contents/MacOS/binaryname) so LEP waited until the > application quit. So in 4D the process is: > > — make sure the destination file does not exist > — launch the app with LEP > — check for the destination file; if it doesn’t exist user cancelled. > > The best way to see if this will work for you is to test by launching on the > command line (Terminal on macOS). If your shell does not give you a promp > until the app quits, then this might work for you. The option that forced the > Scriptel app to quit after accepting/canceling is for plugin mode (--plugin). > The Topaz may work similarly, especially if they have plugins that allow you > to collect signatures in Excel, Word, or Adobe Reader. > > Jim Crate ********************************************************************** 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 **********************************************************************
