Yeah, that's a pretty significant bug. Hopefully they fix it! I tried it on a Windows Server 2012R2 machine running 4D Remote, and did a ctrl-S over the DELAY PROCESS line and then minimized -- same thing. RESUME PROCESS did nothing.
> On Jan 5, 2018, at 1:40 PM, Drew Waddell <[email protected]> wrote: > > Hey Jeff, > > After I typed it up I realized I probably should have said we are working on > Windows but also thought the F4 might have been a giveaway. I was curious > about whether it would be different on a Mac. I tried from another process > RESUME PROCESS, BRING TO FRONT, and DELAY PROCESS with passing 0 which seems > like it's the equivalent to RESUME PROCESS based on the documentation notes. > No luck. > > Ah, here we go, calling SHOW PROCESS brought it back to life. What's > interesting here is that when calling PROCESS PROPERTIES it said the process > was visible. > > That's not really a solution though, we'd have to write like a process > watching that would have to make a call that process needed to be revived. ********************************************************************** 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] **********************************************************************
