Re: Making LOG EVENT thread-safe

2017-10-08 Thread John Baughman via 4D_Tech
> Once it happens, you get all kinds of weird stuff - > duplicate workers with "unique" names, the runtime monitor gets super buggy > and starts throwing range errors...until you're dead. If you *don't* find > this result on your gear, please post what version of 4D you're testing > with. Yes I

San Fransisco Font

2017-10-08 Thread Sujit Shah via 4D_Tech
Does the SF font replace Lucida Grand on macOS Sierra? If so I don't seem to find it on my Mac? Has SF become the standard default font for macOS Sierra? -- xxx "There must be ingenuity as well as intention, strategy as well as strength. "

Re: Making LOG EVENT thread-safe

2017-10-08 Thread David Adams via 4D_Tech
Add, On the entirely likely chance that my first answer sounded insufferably arrogant - just wanted to addWell, I'm sleep deprived like I can't remember, and massively jet lagged. I was trying to say that this whole area is one of my *few* areas of genuine expertise. I don't have many. Just

Re: Making LOG EVENT thread-safe

2017-10-08 Thread David Adams via 4D_Tech
> I understand your thinking that 4D may not the way to go for event logging, > but your concern about CLOSE DOCUMENT is where we do not agree. I'am sure you > have seen CLOSE DOCUMENT fail, but I suspect that what you are seeing is not > an issue with CLOSE DOCUMENT, but something else not

Re: Making LOG EVENT thread-safe

2017-10-08 Thread David Adams via 4D_Tech
Hey John, thanks for the great post and all the work. There's no reason for other people to know this, but John and I have *totally* different coding styles. So I was really pleased he went through my example and reworked it in his own way. That he turned up some problems is instructive because

Re: Making LOG EVENT thread-safe

2017-10-08 Thread David Adams via 4D_Tech
Add, Thanks a lot for chiming in! It's always good to hear from you guys in the US office. I'm not sure what problem your solution is solving. I'm not trying to be flip, I just want to make sure to focus on the meat of the issue. A really common approach to log writing is as follows: Have one

voip api asterix

2017-10-08 Thread Andreas Overmeyer via 4D_Tech
von unterwegs gesendet > Am 08.10.2017 um 21:00 schrieb 4d_tech-requ...@lists.4d.com: > > Joe > > I have been writing an interface to the Asterisk VOIP software(Using PHP). At > this point I am waiting for the client to decide how they want the interface > to work-if you are using Asterisk

Re: VOIP caller ID interface

2017-10-08 Thread Joe Dombroski via 4D_Tech
Hi Peter, I figured that someone in the group has already started cracking this egg. Hardware/software on this site looks like a possibility. http://www.callerid.com/ *Joe* -- Joe Dombroski, CTS-D, CTS-I Brandywine Electronics, LTD BEL.comĀ® 611 Carson Drive

Re: VOIP caller ID interface

2017-10-08 Thread Peter Bozek via 4D_Tech
On Sun, Oct 8, 2017 at 8:10 PM, Nigel Greenlee via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > I have been writing an interface to the Asterisk VOIP software(Using PHP). > At this point I am waiting for the client to decide how they want the > interface to work-if you are using Asterisk I can

Re: VOIP caller ID interface

2017-10-08 Thread Nigel Greenlee via 4D_Tech
Joe I have been writing an interface to the Asterisk VOIP software(Using PHP). At this point I am waiting for the client to decide how they want the interface to work-if you are using Asterisk I can offer some assistance (I found there documentation somewhat obtuse and the sample 4D Code that

Re: Making LOG EVENT thread-safe

2017-10-08 Thread David Adams via 4D_Tech
I was never focused on LOG EVENT (?) I've never used the command and would prefer not to in this case. I only brought it up because it would potentially well with Loggly. (I'm not committed to Loggy and may not stick with that platform, for what that's worth. But it's worth trying for now.) I

Re: Making LOG EVENT thread-safe

2017-10-08 Thread Keisuke Miyako via 4D_Tech
LAUNCH EXTERNAL PROCESS becomes thread safe in 16R5 http://forums.4d.com/Post/FR/21049933/1/21050200#21050200 which opens many possibilities, the logger command on Mac, for example. perhaps we need not focus on LOG EVENT anymore...

Re: Making LOG EVENT thread-safe

2017-10-08 Thread David Adams via 4D_Tech
I've posted about my various worker log problems here and on some other threads and even posted my sample database for review. Lately, John Baughman has really been sinking his teeth into this issue and has spent a *ton* of time working on it. Thank you John! The news is bad, but I figured I'd

Post Key command not working in converted 4Dv16 database

2017-10-08 Thread Ken Daniel via 4D_Tech
All, I'm having a problem with the Post Key command not working in a database converted from 4Dv14 to v16. Post Key works fine in 4Dv14, and works in 4Dv15 and even in a newly created database in v16, but not in my converted database. I've tried resetting the Preferences and Database Settings to

Re: VOIP caller ID interface

2017-10-08 Thread Peter Bozek via 4D_Tech
On Sun, Oct 8, 2017 at 2:11 AM, Joe Dombroski via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Has anyone extracted caller ID from a VOIP phone and used it to open a > client record in 4D? > > > I am now solving same problem so would be interested in answer as well. I am able to communicate with

Query By Attribute vs Map NULL values to blank values

2017-10-08 Thread John Baughman via 4D_Tech
The documentation for Query by Attribute discusses at length how a # query performs with or without the Map NULL values to blank values checked. I do not see this checkbox in the field Explorer window for an Object field. Am I missing something here? It is there for other types of fields but