onesmith

If you need uuu to be a string instead of boolean you could try something like this instead of the boxed code. var: uuu(" "); if up and up[1] and up[2] then uuu="uuu" else uuu=" "; var: up(false), dn(false), uuu(false), uud(false), str(" "); up=c>c[1]; dn=c<c[1]; uuu=up and up[1] and up[2]; uud=up and up[1] and dn[2]; if uuu then str="uuu" else if uud then str="uud" else str=" ";

I asked two questions with very specific constraints. You might try rereading them.

I find videos to be more informative than books. Here's an excellent one by Mary McHenry, Senior Manager of Compliance at the National Futures Association discussing CTA's. Mary McHenry of the National Futures Association Discusses the NFA

Are you suggesting anyone endorses you or any investment advice, trading advice or recommendations you've made or might make in the future? Or the existence of an endorsement of your past performance?

The indicator and function are locked. A black box waste of time.

Forum protocol. Go to your profile, click on the about me tab. Answer the first question truthfully. Are you saying you're not aware of this protocol for identifying yourself as a vendor?

Your post is a BLATANT breach of protocol. Please identify yourself as a VENDOR.

It's not worth anything. There's more value in my passionate obsession with spreading disinformation.

Of all the traders I've observed there's only a few I believe when they say they have a profitable strategy. Looking back and thinking about the time I spent mining their words ...I could of spent that time better by doing something else with it. It isn't an efficient method for learning how to trade.

The MC status line says you have an ATR Trailing Stop input set to black. Other than that .. there isn't much information in the pictures or description. Can you post the code? Does the MC chart list the indicators status as "on"? How many days or bars of data are loaded? When you hover the mouse cursor on a bar what does the data window report as the value for the plot you're expecting to see? What does the scaling tab of the indicator show?

Volume here too. And fib numbers.

1.07 is the latest version. The information about S and N standing for string and number is in the ELC help file, not the ADE file. The MapSS.New function is listed separately under M for Map. If you look there you will find it along with MapSS.Put. That solves the verify error. But it gives additional errors when inserted in a chart. I don't recall exactly but they point to another function. My initial thought was it might be necessary to write some custom functions to get everything sorted out but I have not read enough of the help file to know why the new errors occurred. If your text is standardized then a kludge to get you by until a real solution is found would be to assign each text item to numbers 1 through 10. Transfer the numbers via ADE. Then translate the numbers back to their corresponding text. I'm interested in understanding why you have text instead of numbers. Is the text proprietary or just a string of letters generated by volume profile? What are you doing? Is it profitable? Speak up, I want to know these things.

I tested this and it works. Thanks for the idea. if lastbaronchart then begin if c=insideask then condition1=playsound("c:\Program Files (x86)\TradeStation 9.1\Program\corkpop.wav") else if c=insidebid then condition1=playsound("c:\Program Files (x86)\TradeStation 9.1\Program\bonk.wav"); end;

No you do not need to include the .wav extension when specifying the file location. When I tried your code it would not verify because the compiler doesn't allow the word playsound in the location you have it. The code I wrote in my earlier can be used as a model. Just substitute your requirements for condition1. if c=insidebid then condition1=true else condition1=false; condition1=playsound("your file location"); After that's working you can repeat the process insideask using condition2 but I recomend you do not try to include it until you have the first half working.

You can only play .wav files. Until you get this debugged copy chime.wav to your c directory and use the format below. if c>c[1] then condition1=true else condition1=false; condition1=playsound("c:\chime.wav");

Most people are not aware of the need to enable look inside bar backtesting. That reduces but does not eliminate the problems. It is still possible to write strategies that take advantage of the defects inherent within the stop and target logic.

The scatter graph shows a 1k stop loss. I am not aware of the precise details of the problems with the built-in stop loss and target keywords because I stopped using them when I found out they had problems. There are people using those things correctly, but the risk of error is not worth the time saved verses the time it takes to write something specific that implements their logic without their inherent defects. Examining these stats further ... shows you've optimized the stop loss separately for longs at 980 and 755 for shorts. If you're doing this using the built-in keywords .. good luck transfering their logic into real life trading.

You made a typing error in the 5th line where you used "the" instead of "this". You could of debugged this by commenting out the entire first paragraph. The second paragraph verifies correctly so it gives you a model you can compare against the first paragraph. [-1] is the same as next bar.

You are only permitted to look at next bar open in a strategy. The buy and sell statements refer to this bars close and this bars range. The conditional requirements for both of the stop orders were the same so I condensed them. if open[-1]>H or open[-1]<L then begin buy next bar c+range stop; sell next bar c-range stop; end;

MapSN calls a function written for Numbers. MapSS calls a function for Strings. You need to use MapSS. I commented out the line with the error and inserted the correction below it input: class("5"); var: myTexte("hello"), InfoMap(MapSS.New); // Value1 = MapSN.Put(InfoMap, "my.Texte", myTexte ); Value1 = MapSS.Put(InfoMap, "my.Texte", myTexte ); Value1 = ADE.PutBarInfo(Class, GetSymbolName, ADE.BarInterval, ADE.BarID, InfoMap);

1) catalog every bit of code you can find 2) code your own ideas Keep writing code.

I learned by studing the built-in code and stuff I found on the net. Take it apart and put it back together. If you get stuck google for a solution or post questions.

There might be a vendor that's on to something viable but they won't be aware of it and won't have the skills to take it that last bit that's required to make it viable. It's unlikely any vendor will ever achieve success as a trader. Too many differences reduce the likelyhood of that ever happening. The odds of learning something viable increase if you limit your research to free sources. Eventually you have to uncover and teach yourself what works.

Accuracy is essential.

I answered your question correctly in my first post to this thread. My an silly ary posts convey that same message. What happens when you format an indicators scale to no axis or a different axis relative to the underlying symbol? If all the code that calculates the pivot is contained in a single chart then the result will be correct. Calculate it. You have the formula. Don't use anything other than the underlying symbol.