|
|
|
#1
|
|||
|
|||
|
If my EL strategy is using statement
if time < 1600 then ...; compilation is fine. If I set the breakpoint and run strategy in PTL Builder, I'm getting an error: "Input string was not in correct format". Removing word 'time' from strategy makes everything running ok (but with missed functionality I need by using word 'time'). Please let me know your thoughts. Last edited by marekj : 02-08-2010 at 01:54 PM. |
|
#2
|
|||
|
|||
|
if time < 1300 then
Print(time);, I got result: 308 309 310 311 312 313 314 315 Last edited by strel : 02-08-2010 at 12:01 PM. |
|
#3
|
|||
|
|||
|
I'm using 1 tick chart. in my case, it doesn't work.
|
|
#4
|
|||
|
|||
|
Quote:
Are you using only Zen Fire connection? Could you decribe us details? It would be great if you contact us through the Skype (support.pfsoft), online support is Available from 8:00 AM till 4:00 PM GMT. Last edited by Support : 02-09-2010 at 11:52 AM. |
|
#5
|
|||
|
|||
|
My strategy:
[IntrabarOrderGeneration = false] Variable: todayLow(0); Variable: todayHigh(0); if todayHigh = 0 or Close > todayHigh then begin todayHigh = Close; end; if todayLow = 0 or Close < todayLow then begin todayLow = Close; end; { if todayLow > 0 then Buy next bar todayLow - 30.00 limit; if todayHigh > 0 then SellShort next bar todayHigh + 30.00 limit; } Print(time); I'm using only Zen-Fire connection, 1 tick resolution, ESH0:CME, PTL Bulider v2.0.50727. I do run strategy from PTL Builder ('Run' button in toolbar). After I compile and click o 'Run' button, I'm getting (last line) following output: ------ Compiling started: Module: Quant_Test, Time: 6:05:44 PM ------ Compiling Quant_Test... ====== Compiling completed Module: Quant_Test, Time: 6:05:44 PM ====== Input string was not in a correct format.; If I comment out Print(time); from my strategy, everything works fine. |
|
#6
|
|||
|
|||
|
Can someone answer if issue was duplicated, or only strel will create revenue for PFSoft by buying licenses (everything works for him - developer and nothing works for me - customer)?
|
|
#7
|
|||
|
|||
|
We have discovered the problem it is caused by regional settings format in Windows.
Fix will be included in the next release. Thanks! |