Posted: Mar 31, 2011 @ 10:17 PM             Msg. 1 of 6

I'm trying to get a simple console app working. I'm looking at your example code, and it seems very simple, but I can't figure out where I'm going wrong.


OEC.API.OECClient _oec = new OEC.API.OECClient();

_oec.OnLoginComplete += new
OEC.API.OnLoginCompleteEvent(this.cb_OnLoginComplete);

Console.WriteLine("Attempting to connect...");
_oec.Connect("api.openecry.com", 9200, "<username>", "<password>", false);
Console.WriteLine("Server found. Waiting for connection complete.");
Thread.Sleep(100*1000);


During that sleep, I expect OnLoginComplete to fire, and it never happens.

I also have handlers on OnDisconnected, OnLoginFailed, OnError, and
OnUserEvent. None of these events fire.

I can run "OEC API Example" with the same login, and the procedure finishes correctly. I've stepped through the code, but for the life of
me, I can't figure out what the example is doing that I am not.

Thanks for any help.
Edited by THarnett81 on Mar 31, 2011 at 22:18:56

Posted: Apr 01, 2011 @ 07:10 AM             Msg. 2 of 6

Hello,

OECAPI fires event via Windows messages behind scene. You need to start some message pump in the thread that created the instance of OECAPI.

---

Victor Vins
Software Developer

Posted: Apr 01, 2011 @ 09:26 AM             Msg. 3 of 6

I've been doing some Googling, and this seems non-trivial. Or, at least, I've not been able to find a simple example of this.

Does anyone have an example of how to do this?

Surely I'm not the first person to attempt to use OEC in a console application or a WPF application.

Edited by THarnett81 on Apr 1, 2011 at 09:52:36

Posted: Apr 01, 2011 @ 02:06 PM             Msg. 4 of 6

Ah, I got it now.

My trouble wasn't WPF vs WinForms, it was UI vs Console.

If you use the OEC lib in a console app, the OEC events don't trigger. I don't know where the events go, but they sure don't go to your app.

As VictorV said, for a console app you'll need to start a message pump or something. I don't know much Windows programming outside of WPF/C#, so I wasn't able to figure that out.

Luckily, I don't really need a console app. I whipped up a demo WPF app, and WPF magically does the behind-the-scenes message pump bullcrap.

Ironically, I started with the console app because I thought it would be the easiest way to demo basic functionality of the OEC library. How backwards is it when a UI app is easier than a console app?
Edited by THarnett81 on Apr 1, 2011 at 14:07:37

Posted: Apr 16, 2011 @ 12:06 PM             Msg. 5 of 6

My long-term goal is to run the strategy on a servers somewhere (as opposed to my PC at home). Does this console event issue mean that the OEC API is not a good platform for me?

---

Zachary Kurmas

Posted: Apr 18, 2011 @ 08:15 AM             Msg. 6 of 6

Hello,

Windows message pump can be started virtually in any kind of .NET application. Please check System.Windows.Forms
.Application.DoEvents() method.

---

Victor Vins
Software Developer