I thought of both of those too, and they also seem messy. Hmm... maybe a hid_windows.dll that's loaded by my hid.dll. That right now seems to be the best option. Do I have to explicitly load every function with GetProcAddress()?
.hc
On Dec 20, 2005, at 6:16 AM, Thomas Grill wrote:
Hi Hans-Christoph, if you really want to stick to your name, the only chance i see is to load all symbols from the Windows hid.dll dynamically (LoadLibrary and GetProcAdress). It depends on the number of functions you are using but should be doable in principle. Apart from that this _could_ work, it's a really dirty solution.
You could also name your object hidwin.dll and load it as a library ;-) Or use a hid abstraction, encapsulating a hidwin object.
best greetings, Thomas
Am 20.12.2005 um 06:54 schrieb Hans-Christoph Steiner:
So, I have a little problem with DLLs. I have a [hid] object. The filename is hid.pd_linux, hid.pd_darwin, and hid.dll. The Windows DDK HID library is called... hid.dll. Arg. It gets worse... my hid.dll is of course dependent on the Windows hid.dll. So when Pd opens up my hid.dll, it looks for the Windows symbols in my hid.dll, and they are, of course, not there.
So I did a little LoadLibrary(), but that does not help because it seems that Windows wants to follow all of the links immediately when it opens my hid.dll, before even the setup function is called, so I get the errors before any function is called.
Any suggestions as to how to deal with this?
.hc
"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
News is what people want to keep hidden and everything else is publicity.
- Bill Moyers