You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes one only wants to only buy (or only sell) - hence it would be useful to have a flag in UI (in bot configuration) that disables 1 side. Should be simple change to add.
Update: to be fair, I figured out how to do it through "configuring placements manually (and specify only 1 side there)" - but intuitive/simpler way to do it would be to have a boolean "Disable Side" toggle on each of the side-cfg-cards (that when pressed would grey-out the whole card)
The text was updated successfully, but these errors were encountered:
but intuitive/simpler way to do it would be to have a boolean "Disable Side" toggle on each of the side-cfg-cards (that when pressed would grey-out the whole card)
Seems like there already is a button to "Allocate" if it hasn't been:
that button ^ would probably be an equivalent to / or inter-operate with a "Enable Side" toggle (which is what "Disable Side" toggle would turn into when side-card is disabled, and when pressed it would simply reverse that grey-out action applied previously) on a side-cfg-card - because we need to enable buy/sell side back on before we can allowing user to configure placements for it (it wouldn't be intuitive to allow user to configure placements for disable side, I think, so just enable it for him automatically if he wants to configure placements).
Sometimes one only wants to only buy (or only sell) - hence it would be useful to have a flag in UI (in bot configuration) that disables 1 side. Should be simple change to add.
Update: to be fair, I figured out how to do it through "configuring placements manually (and specify only 1 side there)" - but intuitive/simpler way to do it would be to have a boolean "Disable Side" toggle on each of the side-cfg-cards (that when pressed would grey-out the whole card)
The text was updated successfully, but these errors were encountered: