JerryTrader
17 Mar 2021, 13:44

RE:

Hi amusleh,
Thanks for your prompt answer !
And by the way, a big shout out to you for your work as well
I have to take the time to look at your extension methods, but I'm sure that it is awesome ;)

amusleh said:

Hi,

Unfortunately it's not possible now, the cloud color is set from output color, you can't change or even access it via code.

I was afraid but expecting this since Cloud are Attribute, so by definition ... static.

I will think of a workaround, and post it there if I find some.
In the meantime, if someone finds something, please share !

Cheers,
Jerry

JerryTrader
02 Mar 2021, 11:12

RE:

PanagiotisCharalampous said:

var tickValue = Symbol.PipValue * (Symbol.TickSize / Symbol.PipSize);

This does not take into account the lot size, but I guess that this is the tick value for one unit.
So multiplying this tickValue by the Position.VolumeInUnits should give me the tick value for this position.

Thanks Panagiotis for your prompt answer.
Cheers,
Jerry

JerryTrader
19 Feb 2021, 15:09

Good news if it is already in the database and that it makes sense. I'm gonna open a suggestion, then.

Thanks for your answer.

JerryTrader
19 Feb 2021, 12:43

RE:

PanagiotisCharalampous said:

Unfortunately there is no way to get this information from the API at the moment.

Alright, 
Thanks for the quick answer.

Does my question make sense, or am I missing something ?

Is it already in your backlog, or should I open a suggestion (if my question makes sense obviously) ?

JerryTrader
15 Feb 2021, 15:37

I don't know your level of programming skills, but a pretty basic way of doing it without knowing anything about the cBot API would be to:

1. Create a field or property in your class
2. When you execute the market order, store the bar index in the field/property
3. Add a condition to check if the current bar index is greater than your field/property + 3

I think the best way to perform what you are looking for is to override the OnTimer method to set a flag like CanExecuteMarketOrder and stop the timer.
As soon as you execute a market order, you reset the flag and start the timer with Timer.Start() with the timespan you wanna wait before setting the CanExecuteMarketOrder flag.

JerryTrader
06 Feb 2021, 16:23

RE:

Hence my last question: "does cTrader only look into Documents\cAlgo\Sources\, or, depending on the setup, it could look into other folders ?"
In the long term, I don't think it is over-engineering to rely on an API property rather than guessing the path will always be the "Documents" folder.

For example, on my laptop, the Robots folder is on the D drive, so hardcoding a "C:\Users\<user name>\Documents\cAlgo\Sources\Robots" would not work.

So I guess that it always look into the Windows "Documents" folder (I can deal with it if there is no exposed property), but it would be nice to have a confirmation because I can't find it anywhere on the documentation.

JerryTrader
06 Feb 2021, 14:33

Thanks firemyst !

1) Use the built in system sounds, and then configure what the sounds will be in the Windows Control panel:

Good to know, I wasn't aware of such solution. Nevertheless, this will change the whole system sounds, and is not specific to an indicator or a cBot.

2) Get the current executing directory and use that as appropriate:

I already tried all those ways, but nothing is pointing to where the *.algo file is stored, but rather to where cTrader is executed from, which is a bit random and unpredictable since cTrader uses ClickOnce.

3) If you did a simple Google search, you would have found that the sound files for Windows are kept in C:\Windows\Media folder. Put all sound files in there, and prepend the path to whatever file name the user selects.

I did, and I currently use this for now, but I would like to deliver something where the user just has to copy/paste the *.algo file + the sound folder and that's it.

Since cTrader knows where to look for *.algo files, maybe they expose this path somewhere in the API.

@cTrader :
If it is not exposed, would it be possible to add this to the API ? Just a property on cAlgo.API.Internals.Algo, like AlgoPath, or something like that ?

Meanwhile, does cTrader only look into Documents\cAlgo\Sources\, or, depending on the setup, it could look into other folders ?

JerryTrader
05 Feb 2021, 20:16

You can't.

Indicators are just made to draw things on charts, but don't have any access to your account, nor orders, positions, etc...

Your indicator could write its calculated stop loss / take profit to a file or in registry.
Then you create a cBot that listens to this file or registry change, reads the values, and create orders accordingly.

JerryTrader
25 Jan 2021, 21:17 ( Updated at: 25 Jan 2021, 21:21 )

RE:

Ok...

I am a bit disappointed by such a support and lack of consideration for traders' needs, maybe it is not as "Traders first" as I thought it would be.
Anyways... Thanks for the time you took for writing those answers.

I guess I will have to reverse engineer all by myself to answer my own questions, so, if this can help someone there, here are the answers

JerryTrader said:

Hi Panagiotis,

Thanks for your answer. I'm a bit worried that you're just "hoping" but I'll deal with it, as long as I find a hack to use 4.6.2 + C# 6.

Can you tell me :

1. How is cBot/Indicator project created to be detected by cTrader ? Because if I try to create a project myself (to have the Build Events tab) with same name, same assembly name, same namespace, same .Net version, Build / Edit in Visual Studio never shows up in cTrader...
2. Why does the "Build Events" is not showing on the cBot/Indicator project ?
3. How can I forward the build to cTrader from VS, using a command line or something

I am open to any solution that could help me workaround this, and patiently wait for the migration to be published.

 

Note: I'm using Visual Studio 2017 Enterprise

 

Many thanks,
Jerry

1. To be built/edited in Visual Studio, cBot/Indicators projects (csproj) must have the following ProjectTypeGuids : DD87C1B2-3799-4CA2-93B6-5288EE92882
   <ProjectTypeGuids>{DD87C1B2-3799-4CA2-93B6-5288EE928820};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
   Note that you must have the cBot and Custom Indicators VS extension installed and enabled to "Edit in Visual Studio" from cTrader.

2. ---

   ---

   You must have the extension installed and enabled to load a cAlgo project inside Visual Studio, otherwise, the project will fail loading.
   The extension is responsible for hiding the "Build Events", but I still ignore why cTrader don't want us to use any build event, preventing us from doing any automated integrations...

3. ---

   ---

   It is possible to trigger a build from cTrader by using the command line : cTrader.exe /compile="yourProject.csproj' /debug="true" (the debug flag is optional if you want to build to release)
   To find all the cTrader name, open your Registry Editor, and go to : HKEY_CURRENT_USER\Software\Classes\.algo\OpenWithProgids
   To find all the cTrader.exe paths, go to : HKEY_CURRENT_USER\Software\Classes\{cTrader installation name}\shell\open\command

Hope this helps,
Cheers,
Jerry

JerryTrader
23 Jan 2021, 12:41

If it was that simple...  I already tried that but cTrader won't be able to compile C#6 language features such as lambda or string interpolation.

There's few topics in this forum mentioning that it is not working, like the one I linked in my original post. 

That is why we are forced to reference another compiled 4.6.2 DLL in the 4.0 cBot/Indicator. But it needs a 2 step compilation process,  which is error prone and time wasting. 

In my original post,  I thought of few differents approaches to workaround this, but the way cTrader projects are created is not common, and the way it is forwarding the build to cTrader is totally opaque. This is the reason why I seek for your help.

Thanks for helping me find a way to use cTrader in a user friendly manner. 

JerryTrader
22 Jan 2021, 16:19

I don't look for real hacks... Just ways to work around the lack of upgrades of the language used...
.Net Framework 4.0 has been released in 2010 ... 11 years ago

I can understand that it can be hard to migrate to 4.6+, and that you can't commit on an ETA.

But please, can you at least explain (without having to support any workaround), how is cBot/Indicator project created to be detected by cTrader, or why does the "Build Events" is not showing on the cBot/Indicator project ?

I'm considering fully switching to cTrader, and migrate 15 years of MQL4 EAs and Indicators, but it makes no sense for me to go from MQL4 old-school language to C# old-school version...

JerryTrader
22 Jan 2021, 15:07

Hi Panagiotis,

Thanks for your answer. I'm a bit worried that you're just "hoping" but I'll deal with it, as long as I find a hack to use 4.6.2 + C# 6.

Can you tell me :

1. How is cBot/Indicator project created to be detected by cTrader ? Because if I try to create a project myself (to have the Build Events tab) with same name, same assembly name, same namespace, same .Net version, Build / Edit in Visual Studio never shows up in cTrader...
2. Why does the "Build Events" is not showing on the cBot/Indicator project ?
3. How can I forward the build to cTrader from VS, using a command line or something

I am open to any solution that could help me workaround this, and patiently wait for the migration to be published.

Note: I'm using Visual Studio 2017 Enterprise

Many thanks,
Jerry

JerryTrader
20 Jan 2021, 21:22

RE: RE: RE:

afhacker said:

bishbashbosh said:

afhacker said:

Put your code on a separate class library project and compile it with Visual Studio, then reference the compiled library to your indicator/cBot.

That's how you can use any of the new C# features but if you put your code inside indicator/cBot project then for compiling cTrader compiler will be used which will fail as it doesn't support the new features.

I see. So the choice is either all-in-one solution or new C# - gotcha.

You can put all the projects on a single solution, you don't have to create separate solutions unless you have to.

Hi, 

Thanks for your tip, it works find, but do you have any solution to simply build everything just using Ctrl + Shift + B (Build Solution) ?

Currently, I need to individually build each DLL before building the solution (which will call the cTrader compiler).
This is a lot of intermediate steps which can lead to some errors (or just forgot to build the DLL since we are used to only "Build Solution").

Thanks !