multi entry signal

[kittyan]

Hi,

is it possible to check live position size, entry price, entry bar number of an entry with referring to its own entry signal ?

kittyan

[NinjaTrader_Ray]

Unfortunately this is not supported.

[kittyan]

Is it likely to make some confusion ( showing live positions while having none ) within NT if I Close a position with exitlong ( entry signal name ) , that was partially closed before ?

I mean for example :
enterlong with 5 stakes with signal name ( EnterLong ( 5, "xyentrysignal") ),
than closing 1 stake without referring to any signal name ( ExitLong (1) ), than closing with signal name without a given stake number ( Exitlong ( "xyentrysignal" ) ) ?

Is it better for Ninja to have always specific and correct stake numbers and signal names in exit orders while working with muliple entry signals ?

Kittyan

[NinjaTrader_JoshP]

Kittyan,

If you are trying to scale out you will want to scale in first and use separate signal names to keep signal tracking properly aligned.

[kittyan]

Well,

thanks for the help. I hoped that Nt 7 would handle this multi order entry/exit situation without building up an own coded database counting and falging the entries, exits, living stakes, etc.

I think this would make NT much more professional: if you make longs in a Swing situation that developes later into a trend situation and you want to give the trend a chance without closing all your opened positions at the extrem of the swing it is rather hard to do without the mentioned database in case you have multiple entries/exits with different stake numbers. But it is known that you must have.

Anyway no problem, almost done with the own database, seems to be working right. Telling the truth NT 7 made a great progress even without our wishes. Not found yet any better in retail business.

best regards
Kittyan

[NinjaTrader_JoshP]

kittyan,

To clarify, NT7 does have the ability to do that, but you would have to go and use Unmanaged code which would neglect any NT signal tracking and leave everything up to the user to maintain. This should generally only be used by advanced programmers that know exactly what they are getting into.