A lib in that case would be a UserLib, which is a text file that specifies which DLL is called, and how the functions in that DLL are made available to Blitz.
It is perfectly possible to get force feedback support through purpose written wrapper DLLs, Pepsi had a DLL going once before Userlibs even came along (although there were some problems with it), but that's really a specialist thing. UserLibs cannot directly provide this functionality, at least as far as I know, because Blitz doesn't support callbacks.
I don't think it's reasonable to suggest to someone who bought Blitz thinking it's an easy way to bypass the hassles of C++ and DirectX for their games programming, to actually forget all that, and now do it themselves.
And yes, I think a lot of people here seriously underestimate the amount of people that own FF capable devices, or that will do by the time their software is released.
It is perfectly possible to get force feedback support through purpose written wrapper DLLs, Pepsi had a DLL going once before Userlibs even came along (although there were some problems with it), but that's really a specialist thing. UserLibs cannot directly provide this functionality, at least as far as I know, because Blitz doesn't support callbacks.
I don't think it's reasonable to suggest to someone who bought Blitz thinking it's an easy way to bypass the hassles of C++ and DirectX for their games programming, to actually forget all that, and now do it themselves.
And yes, I think a lot of people here seriously underestimate the amount of people that own FF capable devices, or that will do by the time their software is released.