From: hat AT se-46 DOT wpa DOT wtb DOT tue DOT nl ()
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Interfacing to a MS-Windows application: How ?
Date: 24 Apr 1998 09:26:55 GMT
Organization: Eindhoven University of Technology, The Netherlands
Lines: 25
Message-ID: <6hplsv$prp@tuegate.tue.nl>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980423191147 DOT 11501C-100000 AT is>
Reply-To: a DOT hofkamp AT wtb DOT tue DOT nl
NNTP-Posting-Host: se-46.wpa.wtb.tue.nl
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <Pine DOT SUN DOT 3 DOT 91 DOT 980423191147 DOT 11501C-100000 AT is>,
	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> writes:
> 
> On Thu, 23 Apr 1998 G DOT DegliEsposti AT ads DOT it wrote:
> 
>> There are still problems in sinchronization... I don't know if Libwin
>> allows interception of windows messages, but it seems very difficult, so the
>> clipboard approach would not be available...
> 
> Synchronization can be also achieved with disk files.  Make 
> simulation.exe create a file with a distinct name (which is known to 
> Excel) when it finishes.  For example, you could have Excel pass the name 
> of that file as a command-line argument to simulation.exe.  You can then 
> periodically test for existence of that file.

I don't want to check periodically, because it slows down the compuation.
Already, the simulation takes always too long. Now if I start doing
nothing just to ensure synchronization, the computation will take much
much more time (the simulator will typically call Excel very often).


Albert
---
Sorry, no .sig
The sys admin wiped the previous sig, and I haven't invented a new one yet.