Pedigree wrote:

pips400 wrote:I could be wrong, but I think once price has crossed under WP for a long, or crossed above WP for a short, then that's the decent retrace we're looking for, so if it goes to S1 for a long or R1 for a short, it doesn't really matter because we already had a decent retrace at WP. Exception to this is a bounce off the WP which happens a lot, which would also be a valid setup.

Right. So there's really no need to mention the weekly resistances or supports, let alone the monthly. Just wondered if I was missing something.

Thank you.

Jemook wrote:

Pedigree wrote:

pips400 wrote:I could be wrong, but I think once price has crossed under WP for a long, or crossed above WP for a short, then that's the decent retrace we're looking for, so if it goes to S1 for a long or R1 for a short, it doesn't really matter because we already had a decent retrace at WP. Exception to this is a bounce off the WP which happens a lot, which would also be a valid setup.

Right. So there's really no need to mention the weekly resistances or supports, let alone the monthly. Just wondered if I was missing something.

Thank you.

Hey Pedigree,

Yes there is a need to mention the resistances and supports. In point 1 I mention the Weekly Pivot, Weekly Resistance/Support 1,2,3 and Monthly Resistance/Support 1,2,3. What I'm trying to say is the pivots are a good place to look for a BOUNCE to get back into the trend, so keep a lookout for them.

You can enter wherever you like but I find the best setups are after a bounce off WP or WS1 or WR1.

Hope this helps!
J

Pedigree wrote:Very useful stuff. Can I ask what decides the frequency of ticks?

garyfritz wrote:

Pedigree wrote:Very useful stuff. Can I ask what decides the frequency of ticks?

However often your broker sends 'em. Hopefully your broker sends every tick they receive from their market portal (liquidity providers), but every broker has a different set of LPs that could result in different numbers of ticks. And some brokers may filter them so you don't receive every tick. And different pairs have different activity levels, and activity is different at different times of the day.

So "you get as many as you get."

With the standard setup, you'll get more ticks & thus more CPU load when you're displaying a lot of active pairs. With the 10-second patch I posted (assuming it works right...) Empty4 still calls the start() function on every tick, but that's fairly minor overhead. It won't actually do any work (checking price, calculating values, updating plots, etc) between the 10-second updates. If your chart is a really active symbol, like EURUSD during Euro hours, it might get 5-10 ticks per second or more. So a 10-second update can significantly reduce the work it has to do.

garyfritz wrote:

spotdespot wrote:
But it's easy to fix. Just add this at the beginning of start():

Code: Select all

datetime LastUpdate = 0;
if (TimeCurrent() - LastUpdate < 10) return(0);
LastUpdate = TimeCurrent();

(Not tested since the markets are closed, but it's pretty trivial.)

That will update every 10 seconds. Change the 10 to 60 if you want it to update every minute.

garyfritz wrote:Yes. You just wouldn't see any updates to the indicator for an hour. (And those updates probably wouldn't be in sync with the candle close.) If it was me I'd update it every 5 or 10 minutes so I could glance in on it between candles.

garyfritz wrote: But it's easy to fix. Just add this at the beginning of start():

Code: Select all

datetime LastUpdate = 0;
if (TimeCurrent() - LastUpdate < 10) return(0);
LastUpdate = TimeCurrent();

(Not tested since the markets are closed, but it's pretty trivial.)

That will update every 10 seconds. Change the 10 to 60 if you want it to update every minute.

//+------------------------------------------------------------------+
//| Custom indicator iteration function                              |
//+------------------------------------------------------------------+
int start()
{
  datetime LastUpdate = 0;
   if (TimeCurrent() - LastUpdate < 10) return(0);
   LastUpdate = TimeCurrent();
   int limit;
   int counted_bars = IndicatorCounted();

   if (counted_bars < 0)  return(-1);
   if (counted_bars > 0)  counted_bars -= 10;

   limit = Bars - counted_bars;

   if ( maxBars > 0 )
   {
      limit = MathMin (maxBars, limit);   
   }   

   int i;
   
   for ( i = 0; i < CURRENCYCOUNT; i++ )
   {
      SetIndexStyle( i, DRAW_LINE, STYLE_SOLID, 2, currencyColors[i] );
   }   

   RefreshRates();
   
   for ( i = limit; i >= 0; i-- )
   {
      int index;
      double diff = 0.0;
      
      ArrayInitialize(currencyValues, 0.0);