There must have been some change and I´d like to know what changed since I cannot see any change in New & Notworthy. My charts do not load.
Size:
Color:
Size:
Color:
When I load Equities that are set in teh SI via "Wildcards", as discussed here:
/Forum/Posts/Number-of-decimal-places-30405The chart does not load and it says:
QUOTE:
Runtime error: "***********"wird analysiert - Quantifizerer {x,y} nach nichts.
bei WealthLabPro.ChartForm.q()
bei WealthLab.BarsLoader.GetData(DataSource ds, String symbol)
...
Size:
Color:
It's advised to use wildcards very carefully in Symbol Info Manager due to a couple of open issues.
In 6.1, the Symbol Info Manager started generating runtime errors when series of wildcard characters are used e.g. 'D**'. Make sure that no Symbol Info Manager entry contains multiple asterisks e.g '**' in 6.1.
We apologize for the inconvenience.
Size:
Color:
Are you kidding?
How to handle a list of 1000 equities then?
Size:
Color:
We're trying to get a handle on this. From what I gather, a change was made to move to towards using RegEx in the SIM to solve undesired matches that were occurring with the * wildcard.
If you trade only futures, it doesn't seem like there's a problem to continue using a single wildcard symbol. Just be aware that if you also test stocks, there may be undesired matched. In this case, just disable futures mode when testing stocks.
Size:
Color:
I am not only testing, I am also trading realtime in futures andequities. I need equities to be 3 decimals. How do I achieve this? it worked fine in 6.0.
Size:
Color:
QUOTE:
I need equities to be 3 decimals. How do I achieve this?
Preferenes > Advanced Options > Decimal Places > Pricing Decimal Points: enter 3.
Size:
Color:
@Eugene
Why did you suggest in the above mentioned thread to use Wildcards, when it is working with Advanced Options settings? Was there a change? Will I achieve the same results in WLD6 without Wildcards?
Size:
Color:
Because you asked how to have equities display 3 decimal points, the suggested option should do the job.
To avoid the runtime error, multiple wildcards should currently be replaced with single asterisk symbol.
2 Robert: would you find downgrade to WLD 6.0 a temporary workaround?
Size:
Color:
So, if I select three decimals under advanced options, all symbols will have 3 decimals despite those I specify in the SI Manager?
Size:
Color:
No, the Advanced Option changes the default decimal setting. Futures Symbol decimals should be honored in Futures mode.
(Incidentally, the decimals option was added in 6.0.)
Size:
Color:
Yes, just like in WL 3/4, but note that matching Symbol Info Manager settings (if present) will override this preference.
Furthermore, due to a bug if there's a trailing asterisk symbol, wildcards may go berserk and match anything. For example, if you set the decimal options to 3 and enter e.g. "A*", ALL symbols not defined in Symbol Info Manager will be treated incorrectly as Futures symbols: decimal places = 3 is ignored, 2 decimal are displayed, and Bars.SymbolInfo == SecurityType.Future. On the other hand, 'A*L' is fine (and will catch AAPL but not AA or CSCO).
Therefore, two suggestions to 6.1 users:
1. No multiple wildcards e.g '**'
2. No trailing asterisks e.g. 'A*'
Size:
Color:
Okay, working on my side now.
I have set Advanced Options to 3 decimals, so that all my Equities are handled this way, and all Futures are set in SI Manager anyway with their respective number of decimal places.
Thanks for the quick help. However, I am really glad that I am running my realtime scripts on another machine that I did not upgrade.
Thats another point why I think that every change should be announced in the change logs.
Size:
Color: