Have the recent updates changed the Logos API?
I have some Autohotkey scripts that rely on the Logos 4 API but they don't work anymore. I'm wondering if the recent change from "Logos Bible Software" to "Logos Bible Study" might have affected this?
For example, I don't think ComObjActive("LogosBibleSoftware.Application") is valid anymore as it's the only common denominator in all my non-functioning scripts.
Comments
-
I don't have Logos installed so I can't answer that for you, but you can find out yourself what objects are on your system, and then do some guesses (like search for 'Logos'), and fix your scripts!
Here is what to do -
1. Run command window (Cmd) as Administrator
2. Type 'powershell' without the quotes. This puts you in the powershell environment (looks like a command line though)
3. type this ( copy/paste it to be safer you get it right):
gwmi Win32_COMSetting | ? {$_.progid } | sort | ft ProgId,Caption,InprocServer32 > output.txt
(Note - you may have to give a folder name prior to output.text, to put the output in a folder you have access to - for example:
gwmi Win32_COMSetting | ? {$_.progid } | sort | ft ProgId,Caption,InprocServer32 > c:\temporary\output.txt
That's it. Then open output.txt with your favorite editor (for example Notepad), and you will see a list of all the COM objects registered on your computer. Then start doing some text searches for text like 'Logos' to figure out how your objects changed; they probably didn't change much, minor name changes, and you can then get your scripts working!
Good luck, let us know how it goes!
0 -
Hmm, there was nothing with Logos in the output.txt!
For what it's worth, I'm on Windows 11 and running the latest beta but it has always worked fine before.
0 -
Hmm. It's been awhile since I worked with COM, I guess you might have to wait to hear what FL folks reply with. If I think of something else I'll let you know. Sorry!
0 -
Bump in hopes of a response
0 -
Anybody have info?
0 -
I'll give this one last shot. Something in the recent updates have affected how different scripting languages (AutoHotkey in my case). Is there any known update or change in the API?
0 -
I'll give this one last shot. Something in the recent updates have affected how different scripting languages (AutoHotkey in my case). Is there any known update or change in the API?
There have been no intentional changes to the COM API. I have no experience with the COM API, but it sounds kind of like Windows has lost the COM registration.
Perhaps this thread might help: https://community.logos.com/forums/t/133700.aspxAndrew Batishko | Logos software developer
0 -
I had already found that thread and unfortunately it didn't work. I'll continue poking around and see if I find something. Thank you!
0
