Invoking System Editor in code - URGENT (OpenInsight 32-Bit)
At 07 AUG 2009 05:43:28AM Simon G Wilmot wrote:
Hi all,
I know that this has been covered on here before, but I am having some problems with this. I have tried with both Utility RunWin and setting the Idleproc params, but the system just isn't doing anything.
I am wondering if it is because I am having to do it either direct from a window event, or a procedure call from that event, with the parent window already having been called from another window.
Any thoughts ??
Thanks,
Simon
At 07 AUG 2009 02:12PM Jared Bratu wrote:
What version of OI are you working with?
Which system editor are you trying to start, DWB.exe? I believe it runs as an out of engine process so the user/pass/engine name have to be passed to it.
Can you start other windows and applications from the event where your code is executing? What about notepad?
At 12 AUG 2009 04:14AM Simon G Wilmot wrote:
Hi Jared,
I have actually changed companies in the meantime, but I am after the same thing where I am at the moment.
There are two different versions of OI I am looking at, 7.2.1 and 8.0.4, and quite possibly 9 in the near future.
The requirement is to have the editor facility together with the exec/tcl line in the same facility. I know that the System Editor+ and TCL line are available as OI windows and so are easily accessible, but it is much more convenient to have them together.
By passing the OEngine name, can you give me an example of the parameters I need to use for the DWB.exe.
Many thanks,
Simon
At 12 AUG 2009 05:17PM Jared Bratu wrote:
Starting the dwb.exe program from OI as it had been discussed on the forums isn't a documented feature. With the change in engine architecture from 8.x (and maybe even 7.x) the editor requires another command line argument to launch and connect to the oengine process. I believe the argument is a handle for the engine but it isn't a documented process and won't be supported.
At 13 AUG 2009 03:41AM Simon G Wilmot wrote:
Hi Jared,
Thanks for that - I appreciate that this isn't documented as as such isn't supported, but apart from the engine handle what do I need to include on the command line, eg /ap=APP, maybe /oe=enginehandle ??
Thanks,
Simon
At 13 AUG 2009 05:58AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
There's a specific technique just for this docced by Pat McNertheny here
World leaders in all things RevSoft
At 13 AUG 2009 01:46PM Jared Bratu wrote:
When I look at the DWB.exe process from sysinternals process explorer I can see the /AS= flag which I think is a unique engine handle that changes each time the system runs. Its undocumented so I can't say for certain or where the value comes from without looking at the code. The /AS flag is in addition to the standard arguments for oinsight.exe
At 14 AUG 2009 12:59AM dbakke@srpcs.com's Don Bakke wrote:
I know that the System Editor+ and TCL line are available as OI windows and so are easily accessible, but it is much more convenient to have them together.
Which is why we included both in our tool.
dbakke@srpcs.com
At 27 AUG 2009 02:10PM Jared Bratu wrote:
Martyn posted a blog entry that may help you with this issue if it is still a problem. It describes a method to launch tools using the Send_Message function with SYSTEM and RUNTOOL parameters. You can read his posting here http://revsoftuk.blogspot.com/2009/08/launching-oi-tools-from-code.html