Re: Footon's indi corner

File name: Custom Moving Averages Crossover.cs
ERROR: Indicator compilation failed in file [Custom Moving Averages Crossover.cs]
     Line 173 Column 17: The name 'slotType' does not exist in the current context.
     Line 180 Column 22: The name 'slotType' does not exist in the current context.



File name: Round Number II.cs
ERROR: Indicator compilation failed in file [Round Number II.cs]
     Line 160 Column 17: The name 'slotType' does not exist in the current context.
     Line 167 Column 22: The name 'slotType' does not exist in the current context.

Re: Footon's indi corner

Rename "slotType" to "SlotType".

Re: Footon's indi corner

after modification


File name: Round Number II.cs
ERROR: Cannot find an appropriate constructor for Round Number II

Re: Footon's indi corner

here is the fixed indicator file.

Post's attachments

Custom Moving Averages Crossover.cs 13.1 kb, 72 downloads since 2013-06-26 

You don't have the permssions to download the attachments of this post.

Re: Footon's indi corner

ahmedalhoseny wrote:

after modification


File name: Round Number II.cs
ERROR: Cannot find an appropriate constructor for Round Number II

Also not working? hmmm

Edit:
Ok, found the bug,

Thanks, Sq, for mending my errors.

P.S. I blame the heatwave for errors wink

Post's attachments

Round Number II.cs 9.92 kb, 52 downloads since 2013-06-28 

You don't have the permssions to download the attachments of this post.

Re: Footon's indi corner

hello and thanks for the work but

File name: Round Number II.cs
ERROR: Cannot find an appropriate constructor for Round Number II.



Still appear !!!!

Re: Footon's indi corner

ahmedalhoseny wrote:

File name: Round Number II.cs
ERROR: Cannot find an appropriate constructor for Round Number II.

On line 25

public RoundNumberII(SlotTypes slotType)

must be:

public RoundNumberII()

Re: Footon's indi corner

Thanks Pop it works fine now

Re: Footon's indi corner

Hello Footon , this week i just noticed candle code indicator since you have created  , but your indicator is quite different from the original mq4 indicator !!  your version lakes the 4 levels ( two OB levels ) & (two OS levels) , Kindly may you alter your code to show these levels


Thanks again for the nice work

Re: Footon's indi corner

ahmedalhoseny wrote:

Hello Footon , this week i just noticed candle code indicator since you have created  , but your indicator is quite different from the original mq4 indicator !!  your version lakes the 4 levels ( two OB levels ) & (two OS levels) , Kindly may you alter your code to show these levels


Thanks again for the nice work

No, it is not different. There must be different versions, mine is 100% as "my" mq source. In regard to those levels, I'm not following you I'm afraid.

Re: Footon's indi corner

here is the indi

Post's attachments

CandleCode.mq4 4.22 kb, 27 downloads since 2013-10-31 

You don't have the permssions to download the attachments of this post.

Re: Footon's indi corner

it looks like this

Post's attachments

CC.jpg 79.97 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

63 (edited by footon 2013-11-01 16:28:47)

Re: Footon's indi corner

Now it shows the levels.


edit

Error corrected.

Post's attachments

AaHspecCandleCode.cs 18.98 kb, 48 downloads since 2013-11-01 

You don't have the permssions to download the attachments of this post.

Re: Footon's indi corner

many thanks for the levels now drawn on chart

there is still another thing for the indicator to make its proper job which is replacing the fixed level with the four drawn levels

what i mean the four level you just added to indicator to be active :

Top levels:
Stddev2
Stddev1

CC above Stddev2 extreme high readings
cc crosses stddev2 up
cc between stddev2 & Stddev1
cc crosses stddev2 Dn
cc crosses stddev1 Dn
cc crosses stddev1 up

Bottom levels:
Stddev3
Stddev4

CC below Stddev4 extreme low readings
cc crosses stddev4 dn
cc between stddev4 & Stddev3
cc crosses stddev4 up
cc crosses stddev3 Dn
cc crosses stddev3 up


Regards

Re: Footon's indi corner

A lot of coding, don't have the time for it now. Will keep this tabbed but cannot promise anything.

Re: Footon's indi corner

thanks in advance

67 (edited by jsogaard 2013-11-11 15:02:06)

Re: Footon's indi corner

Hi
I did try to add this indicator but get this error. See the pic,,

Post's attachments

error.png
error.png 30.02 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

Re: Footon's indi corner

Download it from Indicator Repository!

Re: Footon's indi corner

Hey.......

Would you consider writing an altered Bollinger and Envelopes which would allow the 'Multiplier' to have values of 0.01.

At present they are restricted from going below 1.00.

I feel that they would have some  better purpose with that change.

Thanks for your consideration.


daveM

{If you do this, could the new indicators be used in both FSB and FSB Pro)

Re: Footon's indi corner

Trailing stop, Take Profit, Break Even, Stop Loss...

Is it possible to write User indicators for those or are they set up to be in the program only.....?

Is there some way that we can have a custom approach to those....?

A custom approach may be quite useful, I am unsure if it is possible.

Thanks


daveM

Re: Footon's indi corner

Blaiserboy wrote:

Trailing stop, Take Profit, Break Even, Stop Loss...

Is it possible to write User indicators for those or are they set up to be in the program only.....?

Is there some way that we can have a custom approach to those....?

A custom approach may be quite useful, I am unsure if it is possible.

Thanks


daveM

Last time I checked it needed changes in the FSB source code, it's still a little bit over my head.

Re: Footon's indi corner

Blaiserboy wrote:

Hey.......

Would you consider writing an altered Bollinger and Envelopes which would allow the 'Multiplier' to have values of 0.01.

At present they are restricted from going below 1.00.

I feel that they would have some  better purpose with that change.

Thanks for your consideration.


daveM

{If you do this, could the new indicators be used in both FSB and FSB Pro)

0.01 in BB you say, hmm. Let me see now, we calculate standard deviation and then plot it. Multiplier 1 means 1 standard deviation, 2 means 2 standard deviations and so on. 0.5 would mean half of 1 standard deviation, hmm, makes sense in a way.

After some time later... Changed the minimum to your liking in BB. Little hint: you should check the Envelopes again!

Off to World Cup now, I hope Argentina shows beautiful play.

Post's attachments

BollingerBandsDaveM.cs 25.87 kb, 38 downloads since 2014-06-15 

You don't have the permssions to download the attachments of this post.

Re: Footon's indi corner

Thanks for that......

Re: Footon's indi corner

Hello Footon,

I found an error in the Repuls indicator, which leads to a crash of FSB Pro. It happens mostly on using W1 time frame.

MovingAverage cannot be calculated on line 197 and returns Null because RepulsePeriod3*5 becomes greater than the length of PosBuffer3.

double[] forceHaussiere3=MovingAverage(RepulsePeriod3*5, 0, MAMethod.Exponential, PosBuffer3);

The same happens on line 198.

MovingAverage parameters must be validated before the call.

I'll try to make FSB Pro rising a proper error message in such a case.

Re: Footon's indi corner

Popov wrote:

Hello Footon,

I found an error in the Repuls indicator, which leads to a crash of FSB Pro. It happens mostly on using W1 time frame.

MovingAverage cannot be calculated on line 197 and returns Null because RepulsePeriod3*5 becomes greater than the length of PosBuffer3.

double[] forceHaussiere3=MovingAverage(RepulsePeriod3*5, 0, MAMethod.Exponential, PosBuffer3);

The same happens on line 198.

MovingAverage parameters must be validated before the call.

I'll try to make FSB Pro rising a proper error message in such a case.

Message received. I wonder why this hasn't come up before, this issue should come up in all 3 MA calcs, I've been trying to crash both FSB and Pro, but with no success, therefore I cannot estimate my fix. It's rather crude but I hope it won't crash at least.