The Origin Forum
File Exchange
Try Origin for Free
The Origin Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ | Send File to Tech support
Username:
Password:
Save Password
Forgot your Password? | Admin Options

 All Forums
 Origin Forum for Programming
 Forum for Origin C
 Problem with compilation of attached code
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic Lock Topic Edit Topic Delete Topic New Topic Reply to Topic

peter.cook

UK
356 Posts

Posted - 06/28/2006 :  4:49:47 PM  Show Profile  Edit Topic  Reply with Quote  View user's IP address  Delete Topic
Origin Version (Select Help-->About Origin): 7.5 SR6
Operating System: Win 2000

Hi,

The order of events on opening an Origin project with atached files should be :

OEvents Launch Sequence:
1.BeforeUserCNF
2.AfterUserCNF
3.BeforeCompileSystem
4.AfterCompileSystem
5.BeforeOpenDoc
6.BeforeCompileProject
7.AfterCompileProject
8.AfterOpenDoc

My problem is that all our opjs have attached files (.cnf, .ogs, .c, .op, .dll) and I am sure that the attached origin c code is not compiled before the section [afteropendoc] is run. The problem might be more significant with slower pcs, client server set up and when network is slow. This shouldn't be the case, and explains why users accessing customised menu functions have problems if they don't allow Origin time to compile (athough attached origin c files should have compiled by then). Some applications access databases on opening and display inconsistent results arising from this. I have to do a fix (now I've identified the problem) such as
 loop(num,1,10) {
if(exist(OCfunction)==20) {
OCfunction;
break;
};
sec -p 1;
}


messy and I don't want to do this.

How can I resolve this problem and as an additional question what steps can I take to ensure fast as possible compiling and loading of attached code?

Cheers,

pete

cpyang

USA
1406 Posts

Posted - 06/29/2006 :  09:14:14 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi Pete,

In terms of slow compiling, maybe the answer is not to recompile codes that have already been compiled. Maybe we can provide an option to make attached files to be extracted at specified locations so when the same OPJ is reopened, the same OC files extraction can detect no change from what has already been extracted and thus no need to trigger recompiling on same OC files.

CP


Go to Top of Page

peter.cook

UK
356 Posts

Posted - 07/06/2006 :  3:34:19 PM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi CP,

I replied to this offline with Easwar, but for the sake of the forum - this approach could work but I would ask why we can't just attach compiled files?

Cheers,

Pete

Go to Top of Page
  Previous Topic Topic Next Topic Lock Topic Edit Topic Delete Topic New Topic Reply to Topic
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
The Origin Forum © 2020 Originlab Corporation Go To Top Of Page
Snitz Forums 2000