Hi Mark
I dont know the calldll module, neither, but one way to call the wtsapi32.dll is from Visual Basic.
There are a couple of articles on the MSDN library how to do that,e.g
Q292631 "HOWTO: Call WTSSetUserConfig() and WTSQueryUserConfig() from Visual Basic"
Q253140 "HOWTO: Use WTSEnumerateProcesses from Visual Basic"
So what is the reason to use SWIG?
Maybe it is also possible with Python COM, but when passing structs from a different language to a DLL you have to take care on memory layout and data type representations.
Maybe it is possible to strip down the Header you initially mentionned so it compiles with SWIG?
From the tests we did with SWIG one year ago I know there are a couple of things that SWIG does not support
but sometimes it is possible to throw out all unneeded stuff and get it compilable.
Peter
> -----Original Message-----
> From: Roach, Mark R. [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 27, 2002 5:38 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FW: swig help with wtsapi32
>
>
> That looks very cool. I actually tried using LoadLibrary and
> GetProcAddress manually with little success. If I can just figure out
> how to get constants and structs out of the dll this will work
> beautifully. (Anyone know how to do that? If not, I'll just
> have to keep
> poking at it) Thanks very much!
>
> -Mark
>
