Re: CALL FORM

Jeremy, Sorry - I find it so annoying when people recommend things I can't get at too. Here's a short primer from my own, limited, work with using DIALOG(*). First, why? I think the idea is to reduce the number of processes some of us create simply to display data. It's not uncommon for a user on

Re: CALL FORM

Kirk, As neither an attender nor a partner, I can’t see that presentation (yet; I assume it will become more generally available one day). I need to look more closely at DIALOG(*), but it does seem to me that CALL FORM can be pretty useful as a means of interprocess communication as well as int

Re: CALL FORM

Jeremy, On Wed, Sep 11, 2019 at 1:13 PM Jeremy Roussak via 4D_Tech < 4d_tech@lists.4d.com> wrote: > ... CALL FORM as a method of interprocess communication. ... You might want to take a look at John Baughman's preso from the last Summit: https://kb.4d.com/assetid=78028 Long story short, CALL FO

RE: CALL FORM

>It seems to be working, in that the listbox is updated, but I’m finding that >the first window > (in whose context the method invoked by CALL FORM is run) jumps to the front. > I don’t see anything in the >documentation that suggests it will do that. > It’s probably easy> enough to work around,

Re: Call form vs form page

Never mind I think I am in the wrong form when I stored the window if for the callback. John Baughman Kailua, Hawaii john...@hawaii.rr.com > On Aug 11, 2018, at 3:02 PM, John Baughman wrote: > > I’m not sure if it’s something I am doing wrong, but regardless what page is > actually being dis

Re: Call Form to the rescue

A welcome addition, the inverse of EXECUTE METHOD IN SUBFORM Finished crazy On Timer hacks, Call Subform with negative events... On Sat, Dec 9, 2017 at 8:55 PM, John Baughman via 4D_Tech < 4d_tech@lists.4d.com> wrote: > I was trying to update a footer cell of a list box in a parent form, from >

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: 4

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

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

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

Re: CALL FORM: Some notes on a command that's easy to misunderstand

> > > Is there some sort of “quick open” functionality for project methods > that I > > haven’t found yet? > > Yes! Great feature: > > METHOD OPEN PATH > http://doc.4d.com/4Dv16/4D/16/METHOD-OPEN-PATH.301-3037152.en.html > P.S. I think that API Pack's version of this feature allows you to open at

Re: CALL FORM: Some notes on a command that's easy to misunderstand

> On Mar 20, 2017, at 12:45 PM, James Crate via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > It would be nice if the tokenized method name could be used; We need this in a lot of places. I think it could be as simple as a "Method name" command that takes the tokenized name and returns the stri

Re: CALL FORM: Some notes on a command that's easy to misunderstand

On Tue, Mar 21, 2017 at 4:45 AM, James Crate via 4D_Tech < 4d_tech@lists.4d.com> wrote: Hey Jim, it's good to have you chiming in. > I was looking forward to finally having something better than CALL PROCESS > available, but it is disappointing to see the level of coupling required to > utilize t

Re: CALL FORM: Some notes on a command that's easy to misunderstand

On Mar 16, 2017, at 10:28 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> wrote: > > That's not what 4D's "messages" are, they're commands. In fact, the > best names for the new commands are probably these: > > EXECUTE METHOD IN WINDOW > EXECUTE METHOD IN WORKER I was looking forward to fin

Re: CALL FORM: Some notes on a command that's easy to misunderstand

On Sat, Mar 18, 2017 at 12:01 PM, Douglas von Roeder via 4D_Tech < 4d_tech@lists.4d.com> wrote: > David: > > Just read the feature request thread for WebSockets and I'm pretty certain > I voted for it (clicked 4 stars on the first message in the thread). > Thanks! Not my feature request, but, dan

Re: CALL FORM: Some notes on a command that's easy to misunderstand

David: Just read the feature request thread for WebSockets and I'm pretty certain I voted for it (clicked 4 stars on the first message in the thread). WebSocket fits well into the concepts of Call worker/form in that it's providing developers with more granular connections and, hence more granula

Re: CALL FORM: Some notes on a command that's easy to misunderstand

David: I'll read up on the web sockets - when I first saw that I misread it for "WebObjects". A cold chill ensued. C_Object is a great addition to the language. Agree that it doesn't do everything that OT does but that why we have wrapper routines. I've extended Cannon's OBJ_Module with OBJ_SetAr

Re: CALL FORM: Some notes on a command that's easy to misunderstand

> Interesting approach - thank you for posting that. DvR: You, of all people, will *love* this approach. > Lacking "callers" and C_Object, I've been using On outside call + > ObjectTools + IP messaging based on the ITK message queuing system. Once you have access to V16, you may find: * You lik

Re: CALL FORM: Some notes on a command that's easy to misunderstand

> On Fri, Mar 17, 2017 at 6:22 PM, Justin Carr via 4D_Tech wrote: > OK, so it's Friday afternoon and I've got a few moments while I sup on a cold > bevvy. Hey J, thanks for chiming in! > David & I kind of got the fervour about CALL FORM/WORKER at the same > time and this is one of the things abo

Re: CALL FORM: Some notes on a command that's easy to misunderstand

Justin: Interesting approach - thank you for posting that. Lacking "callers" and C_Object, I've been using On outside call + ObjectTools + IP messaging based on the ITK message queuing system. I'm not sure if this is germane to Call form/worker but I include a "reply to ID" in the message that's

Re: CALL FORM: Some notes on a command that's easy to misunderstand

Hi David, Yes, you need to log in. Notes are only available at livedoc.4d.com . (There is NO note feature at doc.4d.com .) The login link is at the top right of the web page. https://s8.postimg.org/oylrfbtsl/p01_comment_log_in.png Scroll down to th

Re: CALL FORM: Some notes on a command that's easy to misunderstand

OK, so it's Friday afternoon and I've got a few moments while I sup on a cold bevvy. David & I kind of got the fervour about CALL FORM/WORKER at the same time and this is one of the things about them that really captured our imagination. We are using CALL FORM and CALL WORKER to automate unit t

Re: CALL FORM: Some notes on a command that's easy to misunderstand

Forgot to mention, it might be worth renaming the commands for clarity so I put in a feature request the other day and then revised it before the post above. Here's the link if anyone agrees and feels like voting for it: http://forums.4d.fr/Post//19157490/1/ ***