OmniTrader Professional Forum OmniTrader Professional Forum
forums calendars search
today this week
 
register logon control panel Forum Rules
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.


  Current location        Thread information  
OmniTrader Pro Resource Forum
OmniTrader Pro Technical Support
Trapping Errors in Olang Routines
Last Activity 6/18/2018 10:21 AM
5 replies, 389 viewings

Jump to page : 1
Now viewing page 1 [25 messages per page]
 
back reply
Printer friendly version

^ Top
John J

Regular
252525
Posts: 84

Joined: 12/20/2011
Location: Leduc

User Profile
 
Subject : Trapping Errors in Olang Routines
Posted : 6/28/2017 2:05 PM
Post #29599

Hi,

This morning I wasted 3 hours on figuring out why OT was crashing or being non responsive in certain profiles. The culprit turned out to be an Olang indicator (text file was copied and pasted from the forum), which didn't compile properly.

We shouldn't have to go looking for errors like this. As we all know, one faulty Olang routine is enough to "corrupt" all routines regardless of whether they are in use or not (one rotten apple spoils the bunch so to speak).

I therefore propose that any compile error messages stemming from Olang are pushed to the forefront of OT/VT so that it can be dealt with, with minimal interruption.
^ Top
Jim Dean

Sage
2000100010025
Posts: 3128

Joined: 3/13/2006
Location: L'ville, GA

User Profile
 
Subject : RE: Trapping Errors in Olang Routines
Posted : 6/28/2017 6:22 PM
Post #29600 - In reply to #29599

The are visible on the bottom left during initialization. Check after that is very simple:

Open olang editor
Press Ctrl+b to compile everything
Watch results pane - it says what routine is in error.
Fix the routine.
^ Top
John J

Regular
252525
Posts: 84

Joined: 12/20/2011
Location: Leduc

User Profile
 
Subject : RE: Trapping Errors in Olang Routines
Posted : 6/29/2017 12:37 PM
Post #29601 - In reply to #29599

Hi Jim,

I think you misunderstood. In this particular case I never opened the Olang editor. I just copied the Indicator from the forum and pasted it directly into the VBA/Indicators folder. It turned out that this Indicator contained an error unbeknown to me at the time.

When you then go to restart OT/VT, there are no messages popping up saying that the system has been corrupted due to a faulty Olang routine. As both of us know, OT/VT tries to compile everything found in the VBA folders during startup. Compile error messages are not pushed to the forefront, and can only be seen after opening the Olang editor.

[Edited by John J on 6/29/2017 1:17 PM]

^ Top
THOMAS HELGET

Legend
500
Posts: 510

Joined: 3/22/2006
Location: BALDWINSVILLE, NEW YORK

User Profile
 
Subject : RE: Trapping Errors in Olang Routines
Posted : 6/29/2017 3:27 PM
Post #29602 - In reply to #29601

John J:

You are correct about pushing the compile problem to the forefront if difficulties occur on startup so that you might better know the cause of the difficulty.

However it has been my experience that problems like that can easily be solved by opening the OmniLanguage interface and compiling everything to see if the error is possibly there. That is what I think Jim was suggesting.

One source of difficulty sometimes stems from downloaded OmniScripts that contain a Return statement at the end of the file. To do that easily just go to the very last letter in the OmniScript and hold down the delete key until the line you are on is the very last line in the OmniScript. Then compile once again.

Another common problem is that a variable in the OmniScript has now been designated an OmniLanguage keyword and you will have to scour the OmniScript and replace all instances of it with a more satisfactory substitute.

I hope that helps!

Tom Helget

[Edited by THOMAS HELGET on 6/29/2017 3:29 PM]

^ Top
John J

Regular
252525
Posts: 84

Joined: 12/20/2011
Location: Leduc

User Profile
 
Subject : RE: Trapping Errors in Olang Routines
Posted : 6/29/2017 4:01 PM
Post #29603 - In reply to #29599

Hi Tom,

Yes, it's easy to solve once you know where to look. In this particular case I never though of any problems stemming from Olang, due to the fact that I had not coded anything in there for at least a couple of weeks prior.

In general it's one of those frustrating things that keeps happening. To be honest with you, not a day goes by that OT/VT doesn't crash at least once with some obscure error code. As a part time software developer I know very well that error trapping is of paramount importance....
^ Top
Buffalo

Legend
50025
Posts: 538

Joined: 7/11/2007
Location: stafford, va

User Profile
 
Subject : RE: Trapping Errors in Olang Routines
Posted : 7/4/2017 9:50 AM
Post #29605 - In reply to #29599

This

and the fact error messages don't tell you where to begin to look, much less give you any clue what could be the culprit
Jump to page : 1
Now viewing page 1 [25 messages per page]
back reply

Legend    Action      Notification  
Administrator
Forum Moderator
Registered User
Unregistered User
E-Mail this thread to a friend
Toggle e-mail notification


Nirvana Systems
For any problems or issues please contact our Webmaster at webmaster@nirvsys.com.