Hello Ernie, Thank you for the reply. I did not quite understand the purpose of the asterisk at first. Then I watched a bit of the presentation by Thomas Maul that you referenced. It seems that this asterisk parameter is an early stage to the upcoming messaging commands.
Due to the manner in which my code was written, with an inherent expectation that once the dialog is closed and not before, execution will return to the line of code directly after the DIALOG command, I was getting -9909 errors when using it. I was getting the error since I did not realize that the first call that I made with the DIALOG command was returning control immediately (as if the user hit the cancel button), and then the code was ready to load the next dialog form which isn't permitted without a new window, apparently. Assuming that I am correct in my analysis, once the dialog window is canceled or accepted, where does control return in the process? Furthermore, if no code is written after the DIALOG command, the process would likely end leaving only the open dialog. It is still somewhat confusing. I suppose that is the intent so that once that dialog is closed, the process goes away. Is this a correct assumption? Thank you, Eric On Sep 5, 2016, at 12:15 AM, ernie hilgers wrote: > Hi Eric Asadoorian, > > >> I have just moved from v12 to v13, OS 10.6.5. I don't believe the following >> issue is OS related. > I still work v13.6 on mac osX 10.6.8. and still admire this product. (also > still work on v2004 on the pc because of the small pgm footprint) > and I am testing "the water" with v15.2 (many times very frustrating) lots of > changes..... (anyway, what can I do but adapt coming year). > >> In the past, upon calling the DIALOG Command, if the process in which the >> command was executed was in the background, that process stayed in the >> background. This behavior was good through v12 for me. >> After converting the database from v12 to v13, a background process >> (visible), upon receiving an outside call to cancel current DIALOG and then >> execute a new DIALOG Command, somehow becomes the frontmost window. >> I am not sure if this is the new expected behavior or a known bug. I am >> using 13.6. >> Has anyone else experienced this when moving from v12 or earlier versions to >> v13? >> >> Thanks, >> Eric Asadoorian > check out the asterix "*" in the dialog command > (Documentation/4D/13.6/DIALOG.301-1457244.en.html) > and also check out the demo by Thomas Maul on www.4Dmethod.com last week > where he explains the importance of the asterix when explaining amoung other > things interesting new commands of v15.4 and up. > > Greetings > > Ernie Hilgers (Aruba) ********************************************************************** 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] **********************************************************************
