Np2112
-
Posts
9 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Blogs
Gallery
Downloads
Events
Posts posted by Np2112
-
-
Thanks Mike, is there is a workaround for what i am trying to do then inside of 1 hotkey?
worst case, i can just not use a conditional order and use 2 keystokes to execute, 1st to trim and 2nd to move pos to b/e.
-
Hi - I am currently using hotkeys to trim position/take profits along the way, the logic is as soon as 1st trim is executed, remaining position qnty should move to breakeven. Getting an error with quantity i.e only the qnty of position that was executed on trim moves up to breakeven,
Below is current formula, What should be changed to move the entire remaining qnty to B/E?
-
-
Hi - I often use indicators in combination with liquidity on order book to confirm my trade thesis, is it possible to highlight indicator value on the X axis of a depth chart, this would be really cool and I've never seen this on other platform, Bookmap maybe comes the closest
For eg: lets say I use pivot points and want to confirm if there is liquidity near the pivot points, this is how a depth chart would look.
- 1
-
-
sure, FYI It did not happen for the last 2 trades, don't exactly know what changed as I was playing with settings
(some screen shots below).
Quote source: I have the default set to Quote stream connect, with smart source turned on to toggle between QS, TDA and yahoo
Broker: Fido(screenshots below were all executed in Fid) and TDA
-
Hi - any time i enter/exit a trade using chart trading the candle wicks spike and be like that for the entire session, is there a way to correct that?
QQQ chart as shown in Medved with my trades,
Actual QQQ during that time
I have odd lots turned off in settings and below are my spike filtering settings, can you help! Thx!
-
Hi - I see a similar issue, can you email me the update as well?
Thx!
Hotkey help to move stop to break even
in Support
Posted
Yes, I had tried doing that with Fidelity earlier, but sometimes the stop order would get executed before, while the trim order was still waiting to be filled, this creates error stop qnty would be more than position held. Hence was looking at OTA orders.