On May 5, 2017, at 2:00 PM, David Adams wrote: > You seem excited about the event ;-) Keep in mind that not everyone can > attend because they either live to far away, have a scheduling conflict, or > are reading these posts in the future. Unless they invent a time travel > machine, it won't be possible to attend...Ultimately, if information isn't > in the docs (language ref, tech notes, tips, recorded sessions, etc.), it's > easily lost or ignored.
I was trying to be silly, not serious. I guess I should have put a :) next to my post. And I am excited about the 2018 4D Summit. JPR says it is going to be big. He provided no details except for one little hint. So as not to offend and keep anything secret here is his comment. If you are using periods in variable names, you might want to stop doing that. You take from that comment whatever you want. I think I know what it coming and it’s something we had a discussion about in the last month here on the iNUG. Something that will definitely be interested in. But that’s just my opinion and speculation. It will be April 2018 before we all know for sure what is coming. And they also mentioned that the 4D Summit in Paris next year will also be done in English and French with translators available in all sessions. So if you can’t make it to America… there’s always France. > As far as the sequence of events goes, it's basic information that should > be in the documentation. There's nothing advanced about it and it's nothing > that should be secret. It's a bit of the mechanics that it's important to > understand so that you don't tie yourself in knots. Here's how it works > (I've posted it here before): > > * When you call Open window (etc.) a 'queue' is created. This is *before* > any form is shown. So, the queue is a property of the window, not the form. > > * You can post code blocks to the queue via CALL FORM *as soon as the > window reference is returned.* > > * ...but then there's no form context to execute the command(s) you've > supplied. > > * Once you open the form, On Load runs. *Your queued commands are still in > the queue.* > > * After On Load, the queued commands are executed in order. The code you > pass in through CALL FORM is held in a First In First Out structure. That's > what a queue is. 4D's CALL WORKER and CALL FORM are 100% reliable about > executing code in the sequence it was received. That's a promise and it > makes things a lot simpler than they might otherwise be. Since this is > FIFO, not truly asynchronous or a stack (LIFO), the code is executed in the > order that you sent it. You are correct. This is exactly how JPR described it. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ******************************************** ********************************************************************** 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:[email protected] **********************************************************************
