comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » First catch of the day
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
First catch of the day [message #42161] Tue, 11 January 2005 23:50
Robert Barnett is currently offline  Robert Barnett
Messages: 70
Registered: May 2004
Member
Does anyone know how to get around this one?


I have had problems running IDL processes using both Watsyn and the IDL
Broker on Siemens E.Soft workstations. The E.Soft application runs in
full-screen mode obscuring the IDL windows. I've been trying to work out
a way to keep the IDL windows 'always on top'.

To solve this, I'm using CALL_EXTERNAL to access MS-Windows functions
from IDL. The particular library is C:\WINNT\system32\user32.dll which
is common over windows 98/NT/2000/XP.

I create a wrapper as recommended in the IDL documentation
result =
CALL_EXTERNAL('C:\WINNT\system32\user32.dll','GetForegroundW indow',WRITE_WRAPPER='user32GetForegroundWindow.c')

I successfully compiled using Microsoft Visual C++ Toolkit 2003.
cl -D_DLL -DWIN32 -D_MT /nologo /I"D:\RSI\IDL60\external\include" /c
"GetForegroundWindow.c" /Fo"GetForegroundWindow.obj"

However, I experience problems when attempting to link the compiled file
into a DLL. The contents of the generated C program
(GetForegroundWindow.c) indicate that I should use the following command:

link /out:"GetForegroundWindow.dll" /nologo /nodefaultlib /dll
"GetForegroundWindow.obj" /def:"GetForegroundWindow.def"
"D:\RSI\IDL60\bin\bin.x86\idl32.lib" msvcrt.lib kernel32.lib

It appears that only kernel32.lib is included with Microsoft Visual C++
yet msvcrt.lib is not. Is this library really required? Do you know
where I can obtain this library from?

The linking also fails because there is no GetForegroundWindow.def file.
This is explained in the documentation of the generatedGetForegroundWindow.c
* Note that these 2 commands are probably not quite enough: You
* will also need to supply a linker options file to control which
* symbols are exported. Under Unix, this file has various names
* (Solaris calls it a mapfile). Microsoft Windows calls it a def file.
* Read your systems linker documentation for further information.
Do you know where I can obtain documentation on how to generate this
.def file?

Any assistance would be appreciated and would assist me in making the
IDL product usable in the supplied environment.


--

nrb@
Robbie Barnett
imag
Research Assistant
wsahs
Nuclear Medicine & Ultrasound
nsw
Westmead Hospital
gov
Sydney Australia
au
+61 2 9845 7223
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Using CALL_EXTERNAL to manage Windows
Next Topic: where and NAN numbers

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:53:06 PDT 2025

Total time taken to generate the page: 0.00503 seconds