Hello, im not getting alerts when i put in the 1.03 version of NT-TMA-CSS-SP
but alerts generate on 1.02. Am i missing something? i've checked the settings though.
NeoTraders NB Indicator Lab
-
VirtualFM
- Trader
- Posts: 84
- Joined: Sat Apr 28, 2012 3:45 am
Re: NeoTraders NB Indicator Lab
I have this problem as well: No alerts in v1.03, even if the Alerts flags are properly set. It works in v1.02 but not in v1.03.
I asked NeoTrader to take a look at it, but since neither he or anyone else commented on it, i figured it was something on my side and disregarded it.
I also can't get the corner info (D1/H4/H1) in SOME pairs. It's a mystery why it works on some pairs and not on others.
I asked NeoTrader to take a look at it, but since neither he or anyone else commented on it, i figured it was something on my side and disregarded it.
I also can't get the corner info (D1/H4/H1) in SOME pairs. It's a mystery why it works on some pairs and not on others.
- NeoTrader
- Trader
- Posts: 436
- Joined: Wed Apr 04, 2012 2:52 pm
- Location: small Village at Lake Chiemsee, Bavaria, Germany
Re: NeoTraders NB Indicator Lab
hi crazzzzzy and VirtualFM,
For the Info problem see a few posts back... this will also be fixed in the next release (hopefully
)
happy trading,
NeoTrader
-
I will look into the Alert thingy...don't know why it doesn't work any more and had also no time to look into. The Alert was also setup to only work with the Diff Slope if I'm correct...Didn't use the Indicator in a while.VirtualFM wrote:I have this problem as well: No alerts in v1.03, even if the Alerts flags are properly set. It works in v1.02 but not in v1.03.
I asked NeoTrader to take a look at it, but since neither he or anyone else commented on it, i figured it was something on my side and disregarded it.
I also can't get the corner info (D1/H4/H1) in SOME pairs. It's a mystery why it works on some pairs and not on others.
For the Info problem see a few posts back... this will also be fixed in the next release (hopefully
happy trading,
NeoTrader
-
-
VirtualFM
- Trader
- Posts: 84
- Joined: Sat Apr 28, 2012 3:45 am
Re: NeoTraders NB Indicator Lab
Oh! Great, thank you! The alert will be really handy, as I spend most time doing something on the computer and will certainly help to not miss opportunities (or at least grab some!)NeoTrader wrote:hi crazzzzzy and VirtualFM,
I will look into the Alert thingy...don't know why it doesn't work any more and had also no time to look into. The Alert was also setup to only work with the Diff Slope if I'm correct...Didn't use the Indicator in a while.
For the Info problem see a few posts back... this will also be fixed in the next release (hopefully)
-
As for the info stuff... heck, I even tried to change the font to see if it helped! Weird thing is that on some brokers I never had problems, then on another one (my main one, bad luck, huh?!) it either doesn't display anything or doesn't display the info or just puts everything on top of each other. It must be related with the Window number or maybe with the sufix of the broker or something.
-
gms
- Trader
- Posts: 83
- Joined: Fri Jan 13, 2012 12:58 pm
Re: NeoTraders NB Indicator Lab
NT TMATrue SlopeHisto MTF does not show the info.NeoTrader wrote: If you have any further Feature Requests or find any Bugs please inform me here on the thread.
showInfo = true
Error Message: unknown subwindow number -1 for ObjectCreate function
gary
- NeoTrader
- Trader
- Posts: 436
- Joined: Wed Apr 04, 2012 2:52 pm
- Location: small Village at Lake Chiemsee, Bavaria, Germany
Re: NeoTraders NB Indicator Lab
Hi Gary,
If this is not the case please report back.
happy trading,
NeoTrader
-
Please read here for why this Problem occurs.gms wrote:NT TMATrue SlopeHisto MTF does not show the info.
showInfo = true
Error Message: unknown subwindow number -1 for ObjectCreate function
If this is not the case please report back.
happy trading,
NeoTrader
-
- gaheitman
- Trader
- Posts: 655
- Joined: Tue Nov 15, 2011 10:55 pm
- Location: Richmond, VA, US
Re: NeoTraders NB Indicator Lab
I haven't used the indicator, but would it be worthwhile to add an extern to allow folks to manually set the window for those cases where WindowFind() returns -1?NeoTrader wrote:Ok... I will try to clarify why this error happens.
If you want to create any Object on the Chart you must assign a specific Window Number to this Object. A Window is the main chart and also any separate subwindow of any Indicator.
The only way to find the Window related to an Indicator is via the IndicatorShortName and the WindowFind() Function.
But since our beloved Empty4 Platform seems to change the the IndicatorShortName when you add a second Indicator on top of it (it concatenates the Names) the Indicator is not able to find the proper Window anymore and cannot create the Objects it wants and this Error occurs.
The only solution to this is to deactivate the objects if you want to use multiple instances of this indicator on top of each other.
Hmm, I wonder what it's name is in the Init()? Do you think it concatenates it after Init() is called or before when loading from a template?
George
- NeoTrader
- Trader
- Posts: 436
- Joined: Wed Apr 04, 2012 2:52 pm
- Location: small Village at Lake Chiemsee, Bavaria, Germany
Re: NeoTraders NB Indicator Lab
Hi George,
The Error seems only to occur when indicators are staked on to each other. And if I disable the object(s) the error is gone.
I have no option to check it...it could be possible that you can trick it with an external Parameter...but then the user needs to be accurate with the name...and if there are also some variable parameters in the indicator name like TF or a Window Number the user would have to change the name every time...and I use variable window(indicator) names to enable multiple instances of my indicator on one chart. Otherwise I would have always the same Error as soon as two instances of my Indicator are on one chart.
And this is also tricky as you can see on some of the latest reports where the InfoTable which is an Label Object still is not set correctly sometimes, especially when you have multiple instances of the Indicator.
I think that I have now a fix for this. The object names are now more specific as is the window name...
hope this helps,
happy trading,
NeoTrader
-
I don't know when and how it changes the name...it is only an assumption of mine that this is the cause of the problem since nothing else changes on the indicators beside this.gaheitman wrote:I haven't used the indicator, but would it be worthwhile to add an extern to allow folks to manually set the window for those cases where WindowFind() returns -1?
Hmm, I wonder what it's name is in the Init()? Do you think it concatenates it after Init() is called or before when loading from a template?
The Error seems only to occur when indicators are staked on to each other. And if I disable the object(s) the error is gone.
I have no option to check it...it could be possible that you can trick it with an external Parameter...but then the user needs to be accurate with the name...and if there are also some variable parameters in the indicator name like TF or a Window Number the user would have to change the name every time...and I use variable window(indicator) names to enable multiple instances of my indicator on one chart. Otherwise I would have always the same Error as soon as two instances of my Indicator are on one chart.
And this is also tricky as you can see on some of the latest reports where the InfoTable which is an Label Object still is not set correctly sometimes, especially when you have multiple instances of the Indicator.
I think that I have now a fix for this. The object names are now more specific as is the window name...
hope this helps,
happy trading,
NeoTrader
-
- gaheitman
- Trader
- Posts: 655
- Joined: Tue Nov 15, 2011 10:55 pm
- Location: Richmond, VA, US
Re: NeoTraders NB Indicator Lab
Actually, I meant for the code to check the return value from WindowFind() and if you get a -1, use the value in the extern parameter (extern int WindowNumber) instead. It would require the user to enter the correct number, but it is easy enough to change if they are wrong.NeoTrader wrote:I have no option to check it...it could be possible that you can trick it with an external Parameter...but then the user needs to be accurate with the name...and if there are also some variable parameters in the indicator name like TF or a Window Number the user would have to change the name every time...and I use variable window(indicator) names to enable multiple instances of my indicator on one chart. Otherwise I would have always the same Error as soon as two instances of my Indicator are on one chart.
And this is also tricky as you can see on some of the latest reports where the InfoTable which is an Label Object still is not set correctly sometimes, especially when you have multiple instances of the Indicator.
I think that I have now a fix for this. The object names are now more specific as is the window name...
Looking at the documentation for WindowFind(), it appears they anticipated my init() question:
GeorgeThe online help wrote:Note: WindowFind() returns -1 if custom indicator searches itself when init() function works.
- NeoTrader
- Trader
- Posts: 436
- Joined: Wed Apr 04, 2012 2:52 pm
- Location: small Village at Lake Chiemsee, Bavaria, Germany
Re: NeoTraders NB Indicator Lab
hi george,
...this could work.
Will try it out with one of the next versions.
Thanks for your inspirational and insightful inputs.
happy trading,
NeoTrader
-
hmmm...actually I never thought of it that way...but you are clearly right, as usualgaheitman wrote:Actually, I meant for the code to check the return value from WindowFind() and if you get a -1, use the value in the extern parameter (extern int WindowNumber) instead. It would require the user to enter the correct number, but it is easy enough to change if they are wrong.
Will try it out with one of the next versions.
Thanks for your inspirational and insightful inputs.
happy trading,
NeoTrader
-