AutoHotkey Community

That should be very easy with COM_L, I'll probably make COM_Unicode4Ansi be an alias for COM_SysString. It may be also straightforward to do for COM.ahk for the official AHK, however, I deliberately stopped updating it to leave it inferior to COM_L/COM_U. But as the incorporation of AHK_L/AHK_U/Native COM support into the official build is indefinitely delayed without any mention from Chris about the future plan, I think I have to update it too.

A new function COM_SysString is added to COM_L/COM.ahk.

Just thought I'd report back on this one, Sean. There seemed to be multiple causes for the stall in COM_Invoke. Some of them were solved by adding Critical to the hotkeys, but I also found that IEReady() was colliding with a subsequent call to click a button once the page was loaded. I replaced the IEReady calls with one of the old readyState complete functions and now those hotkeys work fine.

I also found another bizarre instance, I've been using COM to generate an auto-populated Outlook email. The final line I used to display the email:



Had caused no problems up until recently when it began running into the stall. I toyed around and found that if I deleted the true parameter that it would work fine:



But before I found that out I toyed with some of the other lines in my code and found that if I condensed this code:



Down to this:



It would decrease the stall to a few seconds and finally complete, but it would not eliminate the stall entirely. I have no idea how one chunk of code decreases the stall and the other one eliminates it, but I thought I'd put it out there for you to peruse if you're interested.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

No, all are rooted from one: AHK, especially GUI stuffs, will be irresponsive until return a com call to out-of-process servers like IE, Excel, etc. So:
1) do the best so that a call will be completed as soon as possible.
2) don't call ones which will be waiting indefinitely unless being prepared to programatically handle those yourself, like creating modal dialogs etc.
3) never screw up the chronological order, i.e., don't allow the call interrupted while being executed, like you did in your last post. It's highly likely to create nicely a dead lock.

It'll create a modal window. See 2).

Both the previous and this calls are wrong.

likely AHK is releasing for other processes thus 'stall' you see. Try setting batch lines to -1, etc.

(not tested)

_________________
Joyce Jamce

I'm trying to call a function from a registered txtrocx.dll (activeX dll).

I'm getting
Any ideas of why this is?

The ultimate goal is to be able to wrap all of the functions from the activeX control.

Thanks for any help.

_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞

You must first create an object
perhaps something like this
not having or feeling like looking for any documentation on this DLL the above is a best guess and makes the assumption that Dest is avail directly to the base object

_________________
No matter what your oppinion Please join this discussion
Formal request to Polyethene

Sean - since the primary AHKL release is now Unicode, do you plan on changing the names of the COM_L & COM_U libraries to avoid confusion? ( Or merge the two? )

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

OK, I merged COM_L and COM_U into COM_L. There exist two subdirectories, ANSI and UNICODE.

I'm looking for a way to auto-detect if connection to a certain network is made, after some looking around I thought maybe I could use COM and iSensNetwork (found here: http://msdn.microsoft.com/en-us/magazine/cc301850.aspx) to do what I want, but it's a bit above my current level of coding.

Am I barking up the wrong tree?

I've been doing the auto-detect by just doing a run command for ipconfig and read the output, but that has problems of its own :S

Hope you can (and will) help me.

I realized just how right you were when I was trying to troubleshoot this again today. I read a bit deeper into the VB reference and found I was taking a bizarre route to create a mail item when this was all I needed:



I also resolved the problem with the errors associated with invoking the Display method; I needed to retrieve the Inspector object associated with the new mail item:



One thing I haven't figured out is why retrieving the Inspector object for the new mail item prevents you from invoking the Send method. If I bypass retrieval of the Inspector object I can send the mail straight away without any warnings.

Thanks again for your help, Sean.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

It's outside the scope of COM.ahk, although all needed ingredients for it are already in COM.ahk. You may try to adopt the functions in COM.ahk COM_CreateIDispatch/COM_DispInterface to your need.

Cool, thanks for the information.

Could you give me a working example? That would help me tremendously.
How would I find the pdisp required for those functions?

Encouraged by this post, I tried to incorporate COM into AHK myself. It was my first coding in C++, so there could be many I missed/got wrong. It's based on (UNICODE) AutoHotkey_L45 and I also included the altered/new files in the zip.

DOWNLOAD AutoHotkey_COM.

The new functions are:

Not all in COM.ahk were translated yet like COM_Parameter/missing params. And instead of producing MsgBox, Invoke will assign its HRESULT to A_LastError, so an user can handle the error himself.

The most notable syntax change was on Enumerate and Connect to event. Now I'd like to demonstrate only about Enumerate, and later for others.

Example: Enumerate

Thats great. I don't use COM much, but that will change if it gets into AHKL.

Thx for your work.

_________________