7.91 custom spread decimals

[checkraise]

My user defined spread, $UVOL / $DVOL , now has no decimal places since I upgraded to 7.91. When I go into Tools/Spread Symbol Settings, the only decimal formatting choice for this and all my other spreads is "default".

How can I get my decimal places back for this spread so I see 2 decimal places in my quote window, cursor window, and chart axis?

[ACM]

checkraise
Click on the arrow in the Decimal formatting box and then click the Up/Down selector in the dropdown window (see image) or scroll the mouse wheel.
Alex

[checkraise]

Many thanks Alex, I did not see the Up'Down selectors in the dropdown and thought default was the only choice. Thanks for including the image, makes it so easy.

[ACM]

checkraise
You are most welcome
Alex

[larrybird]

Spread decimals

There is an issue with the way the y-axis
display is done for spreads using futures.
Most stocks and cash indices will display with
an appropriate # of decimals on the y-axis
if one simply enters IBM / GE in the chart
window. However, if you do something like
CL #F / NG #F it fails miserably, omitting
all decimals. The only way around seems to
be predefining a custom contract which in
general is inconvenient for one time or
infreqent use.

Is this a) a known bug with futures contracts
and b) is there a way to change the 'default'
number of decimals on a 'default' spread?

Thank you

[checkraise]

larrybird, when I type your spread formula directly into a daily advanced chart, the price axis lables are 0-1 decimals while the price labels are 4-5 decimals. The same thing happens when I create the spread in Tools>Spread Symbol Settings and keep the decimals at default. But if I change default decimals to 3, the axis labels and price labels both show 3 decimals. So i don't get the "omitting all decimals" like you do.

7.91 build 738 here on W2kpro.

[larrybird]

here is an example

I have build 732, but this has been around
for some time.

[JayF]

Larry,

This is a known bug (EDL#11261), and it has been assigned to a developer. I'm unsure if a fix will make it into the next release or not, but it is being tracked by our internal systems.