|
kmcintyre
 Veteran
  Posts: 132
Joined: 9/12/2007
Location: Valley Center, CA
User Profile |
I updated OT2019 over the weekend to pre-release 2p.
Today I tried to compile an OL indicator. No luck.
Please see the attached png.
The error message appears to be saying there is an issue with the VB compiler?
How should I proceed?
Thanks
Keith
Attached file : OL compile error.png (89KB - 191 downloads)
|
|
Jim Dean
 Sage
       Posts: 3433
Joined: 3/13/2006
Location: L'ville, GA
User Profile |
It's a generic message. It means something bad happened during compile.
Standard procedure is to
1. close OT and delete all VBA/Temp files
2. restart OT and watch bottom left messages like a hawk to see if any compile errors occur
3. fix the things that didn't compile properly
... this could include MANY things ... OLang, CC, any OScripts anywhere, Strats, etc.
Most often, it's an inadvertent change to an OLang routine ...
|
|
kmcintyre
 Veteran
  Posts: 132
Joined: 9/12/2007
Location: Valley Center, CA
User Profile |
Thanks Jim
restarting OT is raising a dialog about compile errors. I see SAMA and DAMA lines called out. I will reload Trade Secrets 1 assets.
The vb temp files are in …/OT2019/vba/temp?
While I have you, do you know what BarMonth and BarDay (I think I have those names right) return? Are they integer functions?
Thanks again...
|
|
Jim Dean
 Sage
       Posts: 3433
Joined: 3/13/2006
Location: L'ville, GA
User Profile |
yes re the Temp folder
BarMonth() returns 1-2
BarYear() returns a four-digit year
BarDayOfMonth() returns 1-31
BarDayOfWeek() returns 1-7 (I don't recall offhand if Sun or Mon is 1)
BarHour() & BarMinute are similar.
You can simply plot any of these with a quick indicator, to illustrate
|
|
kmcintyre
 Veteran
  Posts: 132
Joined: 9/12/2007
Location: Valley Center, CA
User Profile |
all resolved...
thanks
|