trancexx Posted April 17, 2013 Posted April 17, 2013 Aha yes, I see you already posted that link, sorry. I'll see if there is anything I can read out from there. ♡♡♡ . eMyvnE
trancexx Posted April 17, 2013 Posted April 17, 2013 Well, the issue can be classified as bug. The problem is caused by conversion logic from internal Variant type to COM VARIANT type for references. Currently, referenced Variant is dereferenced and turned into a VARIANT of the basic type without creating reference on COM execution level. That means Invoke method of the interface receives VARIANT parameter without VT_BYREF type flag. Use VBS. ♡♡♡ . eMyvnE
tlman12 Posted April 18, 2013 Author Posted April 18, 2013 On 4/17/2013 at 9:43 PM, 'trancexx said: Well, the issue can be classified as bug.The problem is caused by conversion logic from internal Variant type to COM VARIANT type for references. Currently, referenced Variant is dereferenced and turned into a VARIANT of the basic type without creating reference on COM execution level. That means Invoke method of the interface receives VARIANT parameter without VT_BYREF type flag.Use VBS.slightly over my head hahaso is this a bug that is going to be fixed or is it just not worth it?i went ahead and wrote it in vb.net. accomplished the same goals but i just won't be able to integrate it into a program I've already got written in autoit as well lol. oh well works just fine compiling it and calling it with with a run from my other program :-Pif it is something that is going to be fixed i will be happy to help by testing these particular functions. thank you though for all of your help.
trancexx Posted April 19, 2013 Posted April 19, 2013 Fixing the issue is simple task. The only real question is by whom it can be done. I'm not developer any more so I can't give you the answers to your questions. ♡♡♡ . eMyvnE
tlman12 Posted April 19, 2013 Author Posted April 19, 2013 On 4/19/2013 at 7:50 AM, 'trancexx said: Fixing the issue is simple task. The only real question is by whom it can be done.I'm not developer any more so I can't give you the answers to your questions.alright, like i said its not a big deal to me i'm just happy to know it wasn't something i was doing wrong. i consider myself to be "fairly" programming savvy and i just couldn't figure out why it would work in on language and not another considering the similarities between vb and auotit. i would post this in the bug tracker but i don't enough about the problem you described to answer any questions they may have. if you want to post it that would be great and i will, like i said, be available to test and confirm a resolution. if not, that's fine too.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now