I think that the title says it all.

I have a Visual Basic ActiveX dll and I want to call a function that is on my script. I would also need to pass some parameters.

I remember seeing a post on which said how to do that, but I can't find it... (I suck at searching anyway)



Thanks

quote:

---

Originally posted by Felu
See Matty's reply to [Resolved] Talking to VB. .

---

• Subclass a Plus! Window and let it listen to Windows messages send from the ActiveX DLL.
  This can be done in roughly two ways:
  
  
  1. Easy way out (not that elegant imho): make a hidden Plus! window with a textbox control. The function in the ActiveX DLL writes something to that textbox control. A Plus! event will trigger and you can read out the contents of the textbox. This isn't that reliable though. This is done in one of -dt-'s scripts I believe, but can't remember which one (don't shoot me if not ).
     
     
  2. More advanced way (more elegant and more reliable): Subclass a Plus! window and let it listen to your own custom made Windows messages you send from the ActiveX DLL. This is done in the SendTo script.
  Both ways don't actually require the ActiveX DLL to be a DLL. That is, it can also be done from any other external program, script, tool, etc.
  
  
• Invoke an event from the ActiveX DLL
  This requires the ActiveX DLL to be a real ActiveX DLL.
  From the ActiveX DLL you invoke an events which will trigger the associated event in the Plus! script. This is done in the Xniff Notifier script.

Thanks, but I see that the script calls a function and then the DLL returns a value.
I want my DLL to call a function that is on my script and not the script call a function that is on my DLL.

Edit: Just read Cookie's post. I think I'm going to use the 1.A option (for a begging at least)
Btw, what do you mean by "a real ActiveX dll" ?

Both ways of method 1 can be done with anything which supports Windows APIs. Your thing doesn't need to be an ActiveX DLL, or even not be a DLL at all. It can be an exe (eg: like with SendTo), or whatever you make it in (eg: if a DOS batch file would support Windows APIs it could be that too). There is no real bound between your thing and the Plus! script.


For the second method your thing _must_ be an ActiveX DLL as it is the ActiveX object which will be linked to the script. There is a bound between your thing and the Plus! script.


For whatever way you choose (but certainly with method 1), you must _always_ take into consideration that multiple Plus! windows can exist (eg: when the user uses polygamy) and that the Plus! windows don't always exist and/or the script isn't running. Also take into consideration that the user can be switched in Messenger. You do not want to send stuff from your thing to the Plus! script of another user who just logged in instead of the previous one.

quote:

---

Originally posted by CookieRevised
Both ways of method 1 can be done with anything which supports Windows APIs. Your thing doesn't need to be an ActiveX DLL, or even not be a DLL at all. It can be an exe (eg: like with SendTo), or whatever you make it in (eg: if a DOS batch file would support Windows APIs it could be that too). There is no real bound between your thing and the Plus! script.

---

quote:

---

Originally posted by CookieRevised
For the second method your thing _must_ be an ActiveX DLL as it is the ActiveX object which will be linked to the script. There is a bound between your thing and the Plus! script.

---

quote:

---

Originally posted by CookieRevised
For whatever way you choose (but certainly with method 1), you must _always_ take into consideration that multiple Plus! windows can exist (eg: when the user uses polygamy) and that the Plus! windows don't always exist and/or the script isn't running. Also take into consideration that the user can be switched in Messenger. You do not want to send stuff from your thing to the Plus! script of another user who just logged in instead of the previous one.

---

quote:

---

Originally posted by Mike

quote:

---

Originally posted by CookieRevised
For the second method your thing _must_ be an ActiveX DLL as it is the ActiveX object which will be linked to the script. There is a bound between your thing and the Plus! script.

---

Since I think that I will use an ActiveX dll to do that (just because I don't think I have a reason to use an exe), can you please explain that method?

---

quote:

---

Originally posted by Mike

quote:

---

Originally posted by CookieRevised
For whatever way you choose (but certainly with method 1), you must _always_ take into consideration that multiple Plus! windows can exist (eg: when the user uses polygamy) and that the Plus! windows don't always exist and/or the script isn't running. Also take into consideration that the user can be switched in Messenger. You do not want to send stuff from your thing to the Plus! script of another user who just logged in instead of the previous one.

---

Right, I forgot about that.
Well, I guess that I can solve this problem quite simply by setting the hidden window's title to the user's email (or a random string?) and then send that string to my DLL. My dll then, would use FindWindow and pass the string the script sent to the dll as the window's title to find the handle of the hidden window.
Or maybe, I could just send the hWnd of the hidden window to my DLL, since MsgPlus has a function of getting the hWnd of a script created window.

---