Main
Threads
Jump To Forum
Category : OmniTrader Professional Forum
----------------------------
- What's New
- OmniTrader Pro General Discussion
- OmniLanguage Discussion
- Omni Pilot Discussion
- OmniScripts
- Trade Plans In Strategies
- OmniScan
- Feature Requests
- Integrated Brokerage
Category : OmniTrader Pro Resource Forum
----------------------------
- OmniTrader Pro Technical Support
- OmniTrader Pro Frequently Asked Questions
- OmniLanguage Frequently Asked Questions
- OmniPilot Frequently Asked Questions
- Tutorials & Additional Resources
- Technical Analysis Library
Account
You are currently browsing as a guest.
You should
logon
to access more features
A Self-Moderated Community
-
ALL MEMBERS, PLEASE READ!
Vote for Members who contribute the most to your trading, and help us moderate content within the Forums.
You are editing a message originally written by 210921 on 4/26/2019
Username :
Subject :
Message :
Ok. Next step is to check the Temp folder file (same name as the one in indicators folder). That’s the “true VB” code which the parser creates. If that file has an error, it means the parser translated the OL code improperly. If it has no error then the problem lies either in the data or in the library. Also, anyone who does a lot of OL coding can learn a lot about how OL works by reviewing that file. Pay special attention to the main bar-loop. Re if/then syntax - in the past, with more complex code than this, I’ve seen anomalies appear when the “then” is left off. Remember that even though something may work properly in true VB, it doesn’t always follow that the parser handles it the same way.
Registration req. : Off
HTML : On
Formatting Codes
: On
Anon. posting : Off
IP visible : Off
Attachments: Users, Admin
Notify you whenever this thread is updated?
Include signature in this post?