Miyako, In all honesty, I don’t really care about the splash screen; it belongs to 4D and 4D can make it behave as it wishes; if I don’t like it, I needn’t use the splash screen mechanism at all and, as Keith observes, it’s not a tragedy if it closes. I mentioned it only for completeness.
What does bother me is the closing of input windows with no chance for the user to intervene and say “hang on - I made those changes and I don’t want you to throw them away without asking me”. That doesn’t seem right. Jeremy > On 10 Oct 2019, at 22:44, Keisuke Miyako via 4D_Tech <[email protected]> > wrote: > > thank you for sharing, > > so if that is the case, I suppose we can say that... > > the splash screen is not a dialog; On Close Box is not applicable by default. > to prevent it from closing, you could use DIALOG in the application process. > that said, starting a DIALOG (event loop) in On Startup is a very bad idea. > you are never finished booting the app. > >> 2019/10/09 7:51、kculotta via 4D_Tech <[email protected]>のメール: >> >> All true what you said, with some observations (17.3): >> >> If On Close Box is checked, an input window gets the event, but does not >> close. An output window did close. >> If not checked an input window will close, revealing the output window it >> was opened from (when DIALOG was called without OPEN WINDOW being called >> first). >> The windows were created with "DIALOG(outputForm)". >> >> I saw the application window close, but was able to option-command-E to get >> the Explorer. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
