You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to ask a feature to support changing dwClsContext. For instance I right now need to use CLSCTX_LOCAL_SERVER and this means I have to rewrite create_instance and create_raw_instance in order to change that.
Thanks for considering.
As a side note, it would be nice if the Rust efforts at Microsoft had some plan. For instance I'd like to know is there ideas for creating something like winapi crate by Microsoft? The current winapi crate is very hackish. For instance proxy definitions are difficult to work with it because the auto-completions stop working etc. because they use so many macro tricks. Some sort officially supported (and generated) winapi rust package would be nice.
The text was updated successfully, but these errors were encountered:
Yes, we plan to provide provide support for all Windows APIs for Rust developers. We've started with WinRT because such APIs already have metadata describing them and bindings can thus be generated automatically, but we plan to introduce metadata for Win32 and COM APIs as well. At that point, Rust developers will be able to easily consume any Windows API.
Hello,
I'd like to ask a feature to support changing
dwClsContext
. For instance I right now need to useCLSCTX_LOCAL_SERVER
and this means I have to rewritecreate_instance
andcreate_raw_instance
in order to change that.Thanks for considering.
As a side note, it would be nice if the Rust efforts at Microsoft had some plan. For instance I'd like to know is there ideas for creating something like
winapi
crate by Microsoft? The current winapi crate is very hackish. For instance proxy definitions are difficult to work with it because the auto-completions stop working etc. because they use so many macro tricks. Some sort officially supported (and generated) winapi rust package would be nice.The text was updated successfully, but these errors were encountered: