Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Strange behavior

From: amicom:sonic at: 30-Sep-2008 21:00

Hi All! It's been a LONG time since I've written to the list, but I've been busy scripting in REBOL ever since I worked at REBOL ('98 through '01). I'm working on a (hopefully) commercial project, but I'm having a really tough time. I'm using SDK-276. Here's a rundown of the project: There is an "agent" component that is an encapped REBOL script, and its job is to start as a service when the computer starts. Its only job is to babysit another encapped REBOL script called the "client". If the client locks up or quits unexpectedly, the agent kills any locked processes and restarts the client. If the agent locks up or quits unexpectedly, the client kills any locked processes and restarts the agent. The client polls a file for any new instructions to perform, and if found, it performs them. This file could contain any REBOL commands, including 'call. The agent starts up fine, and it will restart the client when needed. The client restarts the agent when needed. This is OK. However, the problem comes when the client needs to open a window of any sort (could be another executable using 'call, it could be a REBOL window, etc.). The executable that the client calls will usually execute, but the window will not appear most of the time. Sometimes, there will be a minimized window in the tray, but it cannot be maximized. Sometimes, there will be no window at all, but the executable will appear in the task manager. Any ideas? Also, I've tried having both the agent and the client bring up a window the first thing, but only the agent or the client's window will appear, not both. Thanks for your suggestions! -Bo