fullmonte
22 Apr 2013, 13:58

Could this be used to talk to other applications from cAlgo?

fullmonte
21 Apr 2013, 12:45

RE: Update

I have managed to stop this happeneing by always removing and readding the references to the DLLs after each DLL rebuild.

fullmonte
19 Apr 2013, 14:53

RE: RE:

same, it was the first I knew. I suggest you make the settings more obvious, this was a huge issue for me and it already had an elegant configuration which I had no idea was there.

fullmonte
19 Apr 2013, 14:52

RE:

Lack of Multi symbols is one of the CAlgos 2 greatest weaknesses, the other being the lack of debug which makes system testing quite a PITA. Rather than having a "flash" implementation why not provide the symbols as least allow 2 different robots to talk to each other as a work around through an interface. That would allow robots to trade baskets with knowledge of the other traders positions and events.

fullmonte
15 Apr 2013, 21:57

RE:

I did not know that you had different settings.Thanks for this.

fullmonte
30 Mar 2013, 21:56

RE:

I am embarrassed but I believe it will fix the problem. Bloody datetime strings drive me mad.

fullmonte
27 Mar 2013, 17:51

Turns out CAlgo is doing it to any exposed DateTime variable created by the server that is exported. Always the same pattern, month replaced with hour.

fullmonte
27 Mar 2013, 17:18

 protected override void OnPositionOpened(Position openedPosition)
 {

            Log(openedPosition.EntryTime.ToString("dd/mm/yyyy hh:mm:ss.fff"));

 }

gives you 06/00/2013 07:00:02.500, which is a big of a pain in the arse tbh since need to develop a work around

fullmonte
27 Mar 2013, 17:05

OK. I have traced the problem to the Position object in CAlgo only, it does not replicate with other Datetime variables which is wierd.

fullmonte
27 Mar 2013, 17:00

06/22/2013 08:22:15.000  the pattern is this, you are replacing the months with the minutes s0 3 is replaced with 22 here

06/20/2013 08:20:02.500  and 20 here

If this is intentional I will no longer be using cAlgo. Please confirm what is going on.

fullmonte
21 Mar 2013, 10:27

So we cannot get access to the cAlgo system dlls for extending to external dlls?

fullmonte
13 Mar 2013, 13:43

RE:

Thats the one. Its the only real concern I have (apart from the lack of debug)

fullmonte
01 Mar 2013, 16:45

Update

All within .NET.  Will post a full explanation soon

fullmonte
28 Feb 2013, 13:56

Addin

The issue can be replicated with any addin:

1. Rebuild add.

2. Build Calgo including the referenced DLL.

It appears that CAlgo must be restarted for each referenced DLL build otherwise it crashs when you try and rebuild CAlgo when you build. Tbh the system works very well with addins and I am not massively annoyed with the crashing since it is essentially an unmanaged feature of using CAlgo. It would be nice however to rebuild without having to reboot when using referenced code.

fullmonte
27 Feb 2013, 15:29

Everytime I build the platform crashes. For every code change the entire platform has to be rebooted. This is not the firs time it has experience such a unstable release. Please sort this out.

fullmonte
15 Feb 2013, 14:47

Version

Can you please explain how I mightr get access to the latest version of the CAlgo. The current version I have does not work and I understand is redundant

version 1.0.293

This is the only version available however from the installer.

F

fullmonte
12 Feb 2013, 16:12

RE:

My apologies. A symptom of not being able to debug is that unforced errors can be hard to track down.

fullmonte
11 Feb 2013, 15:35

RE:

I was thinking could you not make an indicator for each symbol and then just refer to each indicator for the currecy pair you need at a given moment as a work around.