- Search Crypto Craft
- Orest replied Oct 9, 2008
Somebody actually pays attention to details! Sure, it's all makes sense.
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Robert, no - I meant actually profit curve like a line if you will. If you are comfortable doing this you could take LongShortTotal.mq4 and modify it to monitor all 14 buys and all 14 sells (same pairs) instead of 7 buys and 7 sells like it does ...
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Ok, thanks PriNova - this one would be easy to modify. I said modify because we also need another indicator which would mock 14 long and 14 short trades to see how it goes let's if we open 14 shorts(longs) an hour ago. Orest
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Ron, my personal opinion that only benefit of IA is it's not lagging (from 30sec to 1min) like inidcator waiting for a tick (I'm not sure if it's a real issue). But problem of IA is it's lagging datawise unless you open new one every hour, 4 h, etc.
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
That's what Ronald just finished! You could try and give us your feedback.
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Okay, good. I'll also do something like this... AUDUSD 636+50 1up USDJPY 100-34 1dn It will show pips delta from previous value. Would that be helpful? Also I'm stealing another Julius's idea.
What if we show totals for JPY pairs, USD pairs and ...Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Looks interesting, I was thinking about something like this, Bruce. I'll probably get my hands dirty in this.
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Here is another problem I found... if(StartingArray[j] == ReferenceArray[k]) RankArray[k] = j + 1; Both arrays hold profit/loss in pips, so as you could think it has nothing to do with pair itself, there is no guarantee you found exactly the pair ...
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Do you mean similar to Anchor indicator, but showing the trends on different time frames? BTW why would you want to stare at CPU?
You're supposed to stare at monitor. Probably what's why you couldn't notice the trend change. Sorry, couldn't ...Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
When pair doesn't jump "this time" it holds the last jump's value, so it could potentially show same slot number on different pairs. Regarding showing slots delta it's not very informative so far. Suprisingly
it's almost always shows "1" with ...Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
Ronald, this part doesn't look right. What you do is you overwrite same array element with different values. if(ShowRank1 && RankCount == 1) Rank[i] = RankArray[0]; if(ShowRank2 && RankCount == 1) Rank[i] = RankArray[1]; if(ShowRank3 && RankCount == ...
Indicators development for T101's not very simple method
- Orest replied Oct 9, 2008
This is not my EA, Robert I have no idea what's inside. Folks, at this point we work on indicators implrovements, please don't bring any EAs here. You can leave what's been already posted, but don't bring more.
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
Another good idea, comdoc! I wonder why do you guys need smaller timeframes though? It's dancing on 1h like crazy...
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
RR, you have infinitive loop there - replace "while(i>=0)" with "for (i = 0; i<(Bars-counted_bars); i ++)" Also, if(RankCount != 1) Alert("ERROR: Please select one rank to display only"); should be if(RankCount < 1) Alert("ERROR: Please select one ...
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
Robert, could you point me to the error you mentioned? Thanks
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
Humble request — Folks, I have very modest and humble request if you would... We all know that basket trading is all about pure Price Action, nothing else, right? No Fibo lines, no Bollinger bands and other nuclear weapons of mass destruction. ...
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
Robert, variable names mean nothing, just beleive me okay? The code iteself works as it should with pairs from your Properties.
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
Very valuable point, thatnks icicle. Again, this is the last call for those who can't get "Anchor" indicator working. You need to place attached file to experts/include folder. This is ongoing development, so issues are possible.
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
WinUser32.mqh should be in experts/include folder. As for Anchor perfomance you could try to reduce number of bars on your chart (Options->Chart-> maxbars). MAke sure both indicators have same pairs.
Indicators development for T101's not very simple method
- Orest replied Oct 8, 2008
This morning 4h and 1h columns changed from Long to SHort, on 4h sells trade began invasion to top part of the column, shortly touching the top anchor,Dayli trend was Short (strong) it was just before beginning of NY session.
Indicators development for T101's not very simple method