RE: CALL FORM and CALL WORKER
In fact, the functionality explained below could be seen as setting an alarm The alarm fires after a second (period of time) In the meantime it can be reset to again wait for a period of time before it fires Gr, Piotr Van: Piotr Chabot Stadhouders Verzonden: vrijdag 1 december 2017 17:40 Aan: 4D iNug Technical <4d_tech@lists.4d.com> Onderwerp: CALL FORM and CALL WORKER Hi, This is the first time I am going to use CALL FORM and CALL WORKER I am going to convert a "Searchbox" mechanism where a user enters some characters and after 3 or more characters the search is started This was done by a custom Timer mechanism implemented via a separate process and inter process arrays I could call CALL FORM from within the "On After Keystroke" event of the search field, but there is a catch The search isn't started right away after typing 3 characters, but waits for 1 second to see if there are more characters typed So, in the old way there is a method that adds a search request to the interprocess arrays and a process that handles the requests However, after typing more characters within 1 second the request is reset and the 1 second waiting starts over again If the 1 second passes the process calls the form with CALL PROCESS It is this waiting part that is a problem for me to implement I don't know how to do this with CALL FORM / WORKER Does anybody know how to do this? Thomas Maul perhaps? Gr, Piotr ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
CALL FORM and CALL WORKER
Hi, This is the first time I am going to use CALL FORM and CALL WORKER I am going to convert a "Searchbox" mechanism where a user enters some characters and after 3 or more characters the search is started This was done by a custom Timer mechanism implemented via a separate process and inter process arrays I could call CALL FORM from within the "On After Keystroke" event of the search field, but there is a catch The search isn't started right away after typing 3 characters, but waits for 1 second to see if there are more characters typed So, in the old way there is a method that adds a search request to the interprocess arrays and a process that handles the requests However, after typing more characters within 1 second the request is reset and the 1 second waiting starts over again If the 1 second passes the process calls the form with CALL PROCESS It is this waiting part that is a problem for me to implement I don't know how to do this with CALL FORM / WORKER Does anybody know how to do this? Thomas Maul perhaps? Gr, Piotr ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: CALL FORM and CALL WORKER ideas (Was: 4D World Tour - Get off the fence)
Jeffrey, Thanks for the note on subforms, that's good to hear. The last time I looked at them I found little in the docs and thought that it might be an orphaned features. Now I see that there are several pages in the Design and Language manuals. Sounds like it's time for another look, I certainly like the concept. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
RE: CALL FORM and CALL WORKER ideas (Was: 4D World Tour - Get off the fence)
Dave, There are certainly a few conceptual things covered regarding call form and call worker that were discussed and helpful to understand. 1. The fact that you can have multiple forms within 1 context is a complete shift if thought processes. Consider that you can have 2 forms sharing the same selection, process variables etc. In one of JPR's demos, he has 1 form where you select the records, make setting changes etc. and it updates a second forms dashboard display without having to send a selection or really much of anything to the second window other than a call form telling the second window to "update" its display. The display updates using the variables and selection from the first form. Because both windows were started within the same process the share the context information. 2. Call worker in my case is also going to be very helpful. Right now I have some after-hours processes that take a long time to run and are fairly process intense. Being able to just pass these off to multiple cores on the server is going to be extremely helpful to shorten the time of processing as I can slice the tasks to multiple cores. I can't say that the World Tour event helped my understand this but it just showed more examples of performance differences using more cores. 3. One more point regarding call form and call worker. One of the tidbit pieces that I picked up at the conference was a tip for getting rid of IP variables. As you well know in 4D we love our IP vars for setting up runtime constants. JPR's recommendation for this is setup all your values in an object and just pass this object into each worker. Certainly this is not as nice as just having the values at my disposal all of the time but it certainly is a workable solution. Number 1 and 3 are really the concepts that were discussed that I had not yet considered and were very helpful tips on how I can take advantage of the new threading models 4D has provided. HTH Justin -Original Message- From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of David Adams via 4D_Tech Sent: Wednesday, April 5, 2017 4:49 PM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: David Adams Subject: CALL FORM and CALL WORKER ideas (Was: 4D World Tour - Get off the fence) Thanks for posting about the show, it sounds like a really solid couple of days. Likewise to all of the other, similar posts here today. I noticed as a theme a lot of excitement about CALL FORM and CALL WORKER. I'm pretty stoked about them and would really appreciate hearing from people how they are using these tools, or how they're planning to use them. I've been studying them closely for months and am pretty deep in the weeds on the detailsit's nice to be reminded about simple, effective uses. Any comments welcome. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com ** ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: CALL FORM and CALL WORKER ideas (Was: 4D World Tour - Get off the fence)
I also thought the discussion on subforms was excellent too. I have to admit that I've never even looked at them, but they are definitely a game-changer as well. So, not a new feature but definitely new to me. -- Jeffrey Kain jeffrey.k...@gmail.com > On Apr 5, 2017, at 5:49 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I noticed as a theme a lot of excitement about CALL FORM and CALL WORKER. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
CALL FORM and CALL WORKER ideas (Was: 4D World Tour - Get off the fence)
Thanks for posting about the show, it sounds like a really solid couple of days. Likewise to all of the other, similar posts here today. I noticed as a theme a lot of excitement about CALL FORM and CALL WORKER. I'm pretty stoked about them and would really appreciate hearing from people how they are using these tools, or how they're planning to use them. I've been studying them closely for months and am pretty deep in the weeds on the detailsit's nice to be reminded about simple, effective uses. Any comments welcome. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
