uvwxyz
24 Apr 2023, 12:34

RE:

firemyst said:

The error message is what's wrong.

You need to add a reference to System.Management.dll to your Indicator project.

https://ctrader.com/api/guides/referencing_dll#:~:text=In%20order%20to%20add%20a,your%20cBot%20or%20Custom%20Indicator.

Thanks heaps firemyst. Amazing expanation. I'll give it a go. 

Cheers.

 

 

 

 

uvwxyz
04 Jun 2022, 07:35

Hi @amusleh,

Amusleh, my sincere big apologies for the post. Please ignore the post. The problem was a security one at my end. I think my indicators are working as they were before the last night's upgrade; at least the ones I checked are. Sorry for the post.

Thanking for all your hard work. 

Cheers.

uvwxyz
02 May 2022, 11:39

RE: RE: RE: RE: RE:

galafrin said:

uvwxyz said:

galafrin said:

 

The 4.1 csproj file under path folder is backed up by Beta under csproj.backup  in sane directory. A quickfix replaces last csproj by  backedup csproj an rename to csproj and you are done.

Hi galafrin ,

Thanks very much for your time. That's a good solution to know, thanks.  What I ended up doing was I reloaded my periodically backed up indicators (4.1) from anoher drive and opened them in the brokers 4.1 version.

Cheers.

Of course but you might end up loosing your eventual updates  in between if the wholde folder is replaced instead of only the csproj !

Ok, I didn't realise that. But fotunately, I did re-load only all the backed up csprojs; as I found by comparisions between 4.1 csprojs and 4.2 csprojs that's where the differences were. And csprojs were much smaller in size so faster to reload back. So it was lucky for me!!! (I perridically backup the entire cTrader and CAlgo folders with all the bots and indicators and other related folders that are in them.)

Thanking you.

uvwxyz
01 May 2022, 02:56

RE: RE: RE:

galafrin said:

 

The 4.1 csproj file under path folder is backed up by Beta under csproj.backup  in sane directory. A quickfix replaces last csproj by  backedup csproj an rename to csproj and you are done.

Hi galafrin ,

Thanks very much for your time. That's a good solution to know, thanks.  What I ended up doing was I reloaded my periodically backed up indicators (4.1) from anoher drive and opened them in the brokers 4.1 version.

Cheers.

uvwxyz
18 Apr 2022, 11:20

RE:

amusleh said:

Hi,

If you changed the target of your indicator and then recompiled/rebuild an indicator inside cTrader 4.2 then it's project structure changed, if you compile it again on cTrader 4.1 you will get that Guid error.

To solve this issue you can recreate those indicators inside cTrader 4.1 and just copy the code from old ones to new ones.

cTrader 4.2 is backward compatible, but cTrader 4.1 can't use cTrader 4.2 indicators/cBots. 

Thanks amusleh for your reply. Yes, what you say had worked, but I had hoped there was a better (ie faster) solution. ( Inserting the called indicators is time consuming and duplicate doesn't work).  Also I thought I had changed only a handful of indicators to 4.2, but I am getting many many more indicators in 4.1 with that Guid error. Perhaps these many many indicators are calling those few changed to 4.2 ones. (Maybe next time I would be cautious and won't be so eager to jump and experiment with a newer version. I will say some of the features of the 4.2 looked and are wonderful such as the editor's colours coding, syntax errors made visual,  new format of comments, etc. That's why I was very hopeful, in experimenting!!)

Thanks again.

uvwxyz
15 Apr 2022, 14:15

RE:

amusleh said:

Hi,

Version 4.2 is in beta test, we don't have any exact release date for it yet.

We are testing and collecting bug reports from users right now for 4.2.

If your indicator code is visible in 4.1 and not visible on 4.2 code editor, then please send us via email the indicator ",algo" file with it's solution directory which is inside cAlgo/sources/Indicators folder.

Our email: connect@spotware.com

Thanking you for your reply. I have emailed as you mentioned in the your reply. Cheers.

uvwxyz
11 Apr 2022, 12:14

RE:

amusleh said:

Hi,

Are you using the Spotware cTrader Beta 4.2? or your broker cTrader? Which version of cTrader you are using?

The new cTrader 4.2 is backward compatible.

Hi amusleh,

Thanks for the reply. I am using Spotware cTrader Beta 4.2.  Can you please tell us when you think the next upgrade of version 4.2 will be? My indicators codes don't open in the editor. When I open the cTrader 4.2 it comes up with message:

"Exception # D38CF699 in Spoware cTrader 4.2.0.4105:  * An error has occured. The Problem has been submitted to the cTrader team. We apolisse for the inconviencience. Please restart cTrader."

After restarting cTrader same error appears but someimes witth different Exception #. I do not want to download manually beacause I can't afford to lose my many many combinations of indicators in already opened charts. These took me very very long time to make. There are too many templates to remember - which ones I had opened last. ( When Spotware does 'Required Upgrade' these combinations of indicators on opened charts are preserved; when we manually download Automate they are not.) So knowing when the next upgrade will be can help me plan my time accordingly. Thanking you in advance for your usual quick replys

uvwxyz
01 Apr 2022, 12:39

RE:

amusleh said:

Hi,

Try to change the compiler from your cTrader settings to SDK compiler, the default one is embeded compiler which has limited functionality.

cTrader 4.2 is not released for any broker yet, it's only available as beta on Spotware cTrader beta.

Hi  amusleh,

I tried doing this, but I can't find how to do this  in a Demo Account.

I tried looking for cTrader Settings in he Credentials Details. But didn't find the Settings.

Thanks for any help. 

uvwxyz
15 Mar 2022, 09:24

RE:

amusleh said:

Hi,

Installing a new broker cTrader will not delete or replace your current indicators/cBots/templates.

All installed cTrader instances will use the same automate folder data.

Thanking you so much Amusleh, for a quick answer. Thats great. Cheers.

uvwxyz
10 Apr 2020, 09:07

RE:

PanagiotisCharalampous said:

Hi uvwxyz,

Can you please provide us with exact steps to reproduce this behavior? If you could record a short video demonstrating this, it would be very helpful.

Best Regards,

Panagiotis 

Join us on Telegram

Thanks Panagiotis  for the early response, as usual. It happens ones or twice a month  and is impossible to predict so may not be easy to record. Next time it happens i will write down behaviour just before it. I wondered if anyone else ever had such behaviour while coding indicators.

Thanking you again. Keep safe.

uvwxyz
09 Dec 2019, 11:30

RE:

PanagiotisCharalampous said:

Hi abc,

No it is not. You can use any broker's cTrader instead.

Best Regards,

Panagiotis 

Join us on Telegram

Thanks Panagiotis, 

Keep up the great work. CTrader is great. Cheers.

uvwxyz
09 Dec 2019, 11:23

RE:

PanagiotisCharalampous said:

Hi abc,

The current brokers version is 3.6 and you should not have this problem. The problem was reported on 3.7 which is currently only on Beta.

Best Regards,

Panagiotis 

Join us on Telegram

 

Thanks for such quick response. Is it possible to download Beta Version 3.6?

uvwxyz
09 Dec 2019, 11:01

RE:

PanagiotisCharalampous said:

Hi Patrick,

Indeed, templates are not backwards compatible. You should be overriding your templates if you plan to use them on an older version.

Best Regards,

Panagiotis 

Join us on Telegram

 

Hi Panagiotis ,

How can i use previous version of CTrader, eg version 3.6, as the new version crashes my Indicaors, with a runtime error message of :

"09/12/2019 21:58:15.088 Crashed in Initialize with OverflowException: Too many nested indicators created."

Thanking you.
 

uvwxyz
05 Dec 2019, 13:26

RE: 3.7 Too many nested indicators created.

Shares4UsDevelopment said:

version 3.7 Great!
playing around with it pops up the following question.
What is the max of sub-indicators you can have in a indicator after 17 is says there are too many.

private Class RSIs
{
  public RelativeStrengthIndex dataSeries;
  public PairInfo(Indicator thisRobot, Symbols)
  {
    foreach(string SymbolName in Symbols)
    {
      try
       {
         Bars bars = thisRobot.MarketData.GetBars(TimeFrame.Minute, SymbolName);
         if (bars == null)
           dataSeries = null;
         else
           dataSeries = thisRobot.Indicators.RelativeStrengthIndex(bars.ClosePrices, Periods);
       }
       catch (Exception ex)
       {
         dataSeries = null;
       }
    }
  }
}

and how to overcome this Maximum?

 

 

Hi Panagiotis,

I have many Custom Indicators that use a large number of Nested Indicators. Yesterday they were all displaying outputs in CTrader Automate , but today with the new version 3.7, they are not.

Is the number of Nested Custom Indicators that is allowed to be used in a Custom Indicator, a restriction with cTrader and cAutomate? If it is then all my work of previous years (when there was no such restriction) is a waste. Hoping that there is no such restriction for Custom Indicators. (I understand that this may be a problem in automated optimazatioin. However, it should not stop Custom Indicators from using as many Nested Indicators as needed as long as they don't use automated optimization or backtesting.) Thanking you.

uvwxyz
06 Aug 2019, 14:21

RE:

Panagiotis Charalampous said:

Hi abc,

To investigate futher we will need you to send us some troubleshooting information when this happens as well as the settings file of your cTrader. To send troubleshooting information, press Ctrl+Alt+Shift+T, paste a link to this discussion into the text box and press submit. You can find your settings file in C:\Users\UserName\AppData\Roaming\Broker cTrader\Settings and send it to us at community@spotware.com.

Best Regards,

Panagiotis

 

Hi Panagiotis 

Thanks for the reply.

I attemptesd to do Ctrl+Alt+Shift+T during when the problem was happening but the computer wont let me; i noticed the CPU gets 100% occupied from the beginiinning of starting the cTrader.

I use a ESET SMART SECURITY PREMIUM protection. Recently this protection reported " DNS server is making melicious request". Since then then i changed DNS server from Google DNS server to automatic DNS server.

Thanks for any help. I have send the cTrader settings file as requested.

uvwxyz
25 Jul 2019, 14:52

workspaces and new versions

Hi

 When i was logged in before this new version, I had hundreds of instances and charts-combinations opened in my cusom indicators,. Today with the compulsory update to new version, I have none left. All I get is the bare custom indaicators. How can I get those instances with set charts and parameters  back. I tried the same workspace that i had before.  The same workspace opens but with no charts.

Does cAlgo delete the old workspaces it had saved in the cloud, when a new version comes out? If so why doesn't it allow us to save the workspaces somewhere else?  How can I get back my hard work ?

Thanking you.

uvwxyz
25 Jul 2019, 14:49

workspaces and new versions

Hi

 When i was logged in before this new version, I had hundreds of instances and charts-combinations opened in my cusom indicators,. Today with the compulsory update to new version, I have none left. All I get is the bare custom indaicators. How can I get those instances with set charts and parameters  back. I tried the same workspace that i had before.  The same workspace opens but with no charts.

Does cAlgo delete the old workspaces it had saved in the cloud, when a new version comes out? If so why doesn't it allow us to save the workspaces somewhere else?  How can I get back my hard work ?

Thanking you.

uvwxyz
08 Mar 2019, 06:50

RE: RE: IsOverlay not work as previous version did.

Panagiotis Charalampous said:

uvwxyz said:

Hi,

Previously one could use in the Indicators opened chart's tool : f / Custom and overlay a custom indicator B ( built with declaration: "IsOverlay = true;) over another custom indicator A (which is already displayed in a panel), by selecting (in the  f / Custom dialouge box)  B as the 'Indicator' and selecting an output series of indicator A as the input series (source) for indicator B.

Now doing so draws the Indicator B on the main chart which is useless, and also takes away a lot of power of cTrader custom indicators. Previously it drew on the panel of Indicator A.

Can you please, make this previously available funtionality available again.

Cheers.

Hi abs,

This is a bug and we will fix it.

Best Regards,

Panagiotis

Hi Panagiotis,

Thanks greatly for such a quick and a well-appreciated reply.

Cheers.

uvwxyz
07 Mar 2019, 13:10

IsOverlay not work as previous version did.

Hi,

Previously one could use in the Indicators opened chart's tool : f / Custom and overlay a custom indicator B ( built with declaration: "IsOverlay = true;) over another custom indicator A (which is already displayed in a panel), by selecting (in the  f / Custom dialouge box)  B as the 'Indicator' and selecting an output series of indicator A as the input series (source) for indicator B.

Now doing so draws the Indicator B on the main chart which is useless, and also takes away a lot of power of cTrader custom indicators. Previously it drew on the panel of Indicator A.

Can you please, make this previously available funtionality available again.

Cheers.

uvwxyz
01 Sep 2018, 03:43

RE:

Panagiotis Charalampous said:

Hi uvwxyz,

Thanks for the suggestion. You can consider posting it in UserVoice so that it can be considered by the product team. It makes it easier for us to manage suggestions in one place and provide proper feedback rather than being scattered in different forum topics.

Best Regards,

Panagiotis

Hi Panagiotis

Thanks for your reply. However, I thought CTrader's and formerly cAlgo's one of key principles was Custom Development, as your website says. Previously you provided a facility wherby I could develop some complex indicators over many years and this required using long indicator names. It was possible to view these names when opening many indicator windows on the same chart. Now with the last update you made it impossible to distinguish these indicators when opening on the same chart. I feel this is not part of requesting something new and is therefore not part of 'UserVoice' as a new suggestion, but it is an essential back-compatibity feature that should never have been taken away. 

If such drastic changes are made in your updates that back-compatibity is not respected, it is hard to know how reliabe cTrader would be in the future. Hoping that this feature will be soon put back.