WLP 6.9: Orders window, Trade Ticket questions
Author: superticker
Creation Date: 12/7/2015 10:17 AM
profile picture

superticker

#1
The GUI configuration of the Orders window "trading ticket" for WLP 6.8 & 6.9 won't let me post fractional percent trailing-stop sell orders. For example, trailing stop sells for 1.0% and 2.0% are possible, but 0.5% and 1.5% are not. Please fix the UI configuration so fractional percent values are allowed.

The WLP startup message says the Orders window is updated every 30 seconds. That's not true with WL 6.9 and only sometimes true with WL 6.8. The Orders Window only updates when the update button is pushed. Is this behavior normal? (I'm wondering if this may be a problem at the server side, or a problem with the handshaking between client and server.)
profile picture

Eugene

#2
Re: Trade Ticket. There's nothing to fix, this is by design. When not sure please check out the User Guide. Quoting from Orders > Manual Trade Ticket:

QUOTE:
Only whole numbers can be entered for the Trailing Stop % Amount. e.g., 1, 2, 3 (%), etc.


Re: 30 seconds. Please don't split conversation, you already have an open ticket for this with reply from Cone.
profile picture

superticker

#3
Well, you're right. The Fidelity website only allows whole numbers for trailing-stop "percent" sells as well--interesting. I can't imagine why that would be? I guess I'll place trailing stops as dollar values instead, where I can get $0.01 resolution.

--------

Hmmm. Cone hasn't replied about the 30-second update problem as yet. I just assumed he forgot about it.
profile picture

Eugene

#4
QUOTE:
Hmmm. Cone hasn't replied about the 30-second update problem as yet. I just assumed he forgot about it.

I think that since this issue may be connected to the primary issue you've raised in the ticket, his answer applied to this as well.
profile picture

superticker

#5
Thanks for your clarification. I'll just wait until after the new release of WLP, which follows 6.9.12, to see if all the client/server issues are fixed.

I think the old client-server design "tightly couples" the two together so much that the slowness of one affects the performance of the other, which becomes a problem on heavy trading days. A looser coupled, best-effort design may be more effective. Yes, a best-effort design means you may miss some streaming ticks or Order window updates on heavy days, but I think that's acceptable over the alternative (livelocking the streaming Chart windows).

Thanks again for the help.