First of all, you can choose what lines you want displayed on the chart:
Second, if you write your own code, just get the symbol's “ASK” price or “BID” price depending on what you want to display.
eg: Symbol.Ask
As the topic says I need Bid and Ask Candles
Then as I said, you'll have to write your own code. There is no option to display both bid and ask candles next to each other, or anywhere together, on a chart.
This problem should have been resolved by now. Please restart your cTrader and in case you still experience problems, please send us some troubleshooting information quoting this thread.
Best regards,
Panagiotis
I know you've probably not had the best of weeks but I think Patty's eloquent, insightful and detailed feedback possibly deserved a bit more than your identikit "problem solved" response. Probably unfair of me considering, but at the very least I hope Spotware takes points on board points 1,2,4 and 5 relating more to development process than any particular bug.
In at least the last 7 years I've been on these forums and have seen Panagiotis' responses, I can't recall a time where I've ever seen him do a generic copy/paste of responses like this. Even though it says it's his account, I'm not convinced it's him who actually wrote it. If it is, it's definitely “desperate times, desperate measures” and I'd be a bit disappointed like everyone else.
That aside, you can tell Spotware must be receiving A LOT of bugs and issue complaints with their release that all they can do to keep up is respond with the generic cookie-cutter response as you indicated.
Surely they must realize by now they are screwing up big time and need to get their act sorted?
It's quite evident from the string of releases that they have no automated testing procedures in place, nor any dedicated team of testers to review/test releases.
Way too many of these bugs that have been found and affect the application would have been caught doing basic testing if users are experiencing issues within a day of using the software.
Just look at the recent bug I've reported back in May/June with cBots and it's still not resolved. How can anyone trust cTrader to run any bots when there's a huge known bug that's gone unfixed since at least June?!
If there's any leadership at Spotware, they need to dump their people who are responsible for quality control, and some of their developers who should be doing basic unit tests (and catching these issues) to get some people in there who believe they should actually test their software before releasing to the public.
firemyst
05 Nov 2024, 06:09
( Updated at: 05 Nov 2024, 08:02 )
Judging from your charts, are you located in the UK?
That “gap” appears to have happened when the markets start their “reset” window, which causes huge spreads.
Because of that, what you obviously need to do is check the spread on the symbol before doing anything.
//Check the spread
if (Symbol.Spread >= SomePredeterminedAmount)
Print ("Not doing anything! Spread greater than allowed!");
else
{
//Do what you normally would
}
The fact it's the spread can also be confirmed by looking at the “tick” chart for the same time - look how the spread suddenly at least quadrupples:
I don't think this was ever working. When the indicator is unloaded and destroyed, all references created by the indicator will do as well, same for the indicator's log. If you want to check this, write in an external file.
Best regards,
Panagiotis
Ok, now there is no way for the indicator to clear the interactive objects it created when it is deleted.
I am not sure what you mean, can you elaborate?
When my indicator is on the chart. Adds objects to the chart, such as rectangles and trend lines These objects are interactive. "IsInteractive = true;" When I remove the indicator from the chart, those objects remain in the chart! If their interactive feature is false, they will be deleted automatically, but as I said, I will turn on their interactive feature. I want to delete all the objects added to the chart when the indicator is deleted
Hi there,
Can you share the code you are using to delete the objects so that we can check?
As an added step, you should also obfuscate your code before compiling it. THis way, if someone does manage to decrypt your code, it'll still be hard to figure out.
Visual Studio comes with a free tool as it includes a copy of PreEmptive Protection - Dotfuscator Community, free for personal use. (This free version was previously known as Dotfuscator Community Edition or Dotfuscator CE.)
To begin using Dotfuscator Community from Visual Studio, type dotfuscator into the Search Box (Ctrl+Q).
The “takeprofit” parameter in the execute market order is in Pips; you're supplying an actual price.
Replace “takeProfit” in the ExecuteMarketOrder with your parameter “TakeProfitPips”.
OR what you need to do is convert “takeProfit” back to pips as a distance from the current candle close, which seems pointless in this scenario as you have it since TP is measured from the current “close” price when the order is placed.
Thanks @firemyst, changing to TakeProfitPips worked a treat. Your explanation makes perfect sense. Much appreciated.
I wonder if the ExecuteMarketOrder used to be coded to expect the price, rather than pips, since ChatGPT seems to think that's how it works.
Set the pips, and then immediately call:
ModifyTakeProfitPrice()
to set the price if you want to set it by exact price instead of pips.
Thanks, I think I tried googling a while back and didn't find much, but your link is the info I was looking for. It's clear now, I'm using the ctrader app version from a prop firm, it doesn't show the algo option like in the example above.
I think it might only be available in the “Spotware” version of the app.
Keep in mind that regardless of how Spotware/cTrader calculate the angle, the angle will vary depending on the chart's zoom level horizontally / vertically.
It will also change as more bars appear to the right or if you scroll the chart back to the left as cTrader automatically scales the chart.
firemyst
15 Nov 2024, 03:03
This has already been answered if you Google it:
@firemyst