Also, an NT8 strategy to trade precisely at the moment of pivot? Even an outline of how to trade off of this indicator would be very helpful.
Anyone, come one, come all.
Also, I was reading posts about repainting, I'm sure sure what this is. All I know is repaints during choppiness, but I don't have a clear definition of "repaint". Does the Pro version help this? If so, how? Please enlighten me.
Does it revert back and stake a new entry point?
From a scalper's perspective, 100 tick candles, 7 period look back, how would it hurt to trade on every pivot?
The goal of the scalper would be not to trade during choppy periods to the best of his or her ability, but hypothetically isn't the scalper trading off relatively small losses in the anticipation of big gains by trading every pivot (Long-short, short-long)?
I am trying to use PAS inside a custom indicator to change backcolor of chart based on whether the instrument is in an uptrend in higher time frames. Is it possible to pass on a user defined DataSeries object to PAS? Can someone please share a code snippet for the same?
folks I have the divergence indicator on false with the pas swing pro. Besides the retrace percentage, and entry percent allowance, what other criteria does the indicator use to determine the entry as obviously not all retrace legs show an entry on the specified retrace criteria.
I went through the the whole thread and want to try the indicator in one of my strategies. I think I followed all the required steps the get it to work but I get an error when I try to compile. The error is not new, I have seen different persons having the same issue. So far I could not find the solution, probably a simple thing.....
This is what I've done:
1. Download and imported the latest indicator package (no issue)
2. Using the indicators in charts (no issue)
3. Creating a simple strategy using declarations and variables from the given sample code
#region Using declarations
... using PriceActionSwingOscillator.Utility;
I have no experience with this indicator but my first question would be - NT7 or NT8 version?
Then the most likely place the error like this would arise is in the generated wrapper and these are generated from the accessors so that's where I would look for fix. As a first try I would try to instead of using "using" try putting direct full path to every use of the enum, especially around get/set at the bottom (eg. "PriceActionSwingOscillator.Utility.SwingTypes swingType") This should help the wrapper to avoid confusion.
There are users of the indicator where the 'standard' way of coding works fine so it must have to do with the way my NT is organized on my computer or how the indicator has been imported? I did everything following the described examples but I can't get it to compile. I even tried to do it on a fresh istall of NT on another computer with the same result.
I had to delete and/or rename the PriceActionSwingOscillator file I had because it didn't have the .Utility file with it... I found an older one with the .Utility in it - not sure where it came from ... I think the Download version didn't have the Utility.
Anyway, after deleting the old one, downloading and trying it again, it compiles and loads onto the chart.
Thanks for your reply. The thing is that I have no older version of the indicator and imported the latest available package directly into NT. I have indeed the feeling that I miss a file but I'm not into C++ enough to understand what I miss.
Actually using the indicator directly in the chart is no problem, that works okay. It's only when I make a Strategy with this indicator that results in the compile error.
Can you look what files you have belonging to the PriceActionSwing indicator?
Broker/Data: Data = Rithmic -- Gives 70 Level II Data
Favorite Futures: 6C (Low Margin,) 6E, CL, GC, ES and Maybe DX for smaller tick value
Posts: 767 since May 2011
Thanks: 1,262 given,
@Ducman, are you writing the strategy or trying to use Strategy Wizard? If using SWizard, click on the view code button. It will open the code for editing. Then compile it and the error should show up.
Careful since editing the SW code will stop SW from editing it. But at least you can find out what is causing the error.