COM API: 4.0d: Question about two of the object types

Based on the COM API as it is documented in the wiki at present, and from the object model exposed by the current 4.0d RC1 build:

There are data type of LogosBibleDataTypeDetails and LogosBibleReferenceDetails, but I don't see how to ever get one of these objects.

How do I get one of those returned objects please?

As I can't see the objects within the main Logos4 application, can I cast one of the other objects to these types?

Thanks.

Find more posts tagged with

Comments

JimTowler

OK, looking closer, maybe I get them from LogosDataType.Details and LogosDataTypeReference.Details, but both are documented and typed as Object at present.

???

JimTowler

https://community.logos.com/discussion/comment/142218#Comment_142218

OK - I got something almost working in C# with a dynamic data type, however, I prefer to work with VB.NET and using "Option Explicit On" and "Option Strict On".

In which case, the two types that return Object for the Details properties are a real problem.

Is it possible to provide more details on what kinds of objects might be returned in the two Details properties, and then details on those objects?

Thanks.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/142280#Comment_142280

In which case, the two types that return Object for the Details properties are a real problem.

Is it possible to provide more details on what kinds of objects might be returned in the two Details properties, and then details on those objects?

We anticipate having other "Details" classes available in the future for other data types, and Object is the only type they will have in common. If dataType.Alias = "Bible", then the object returned from the dataType.Details property can be successfully cast to LogosBibleDataTypeDetails. Similarly, if ref.DataType.Alias = "Bible", then the object returned from the ref.Details property can be successfully cast to LogosBibleReferenceDetails.

There are no other Details objects at the current time.

JimTowler

https://community.logos.com/discussion/comment/143077#Comment_143077

Thanks Bradley,

Based on the large number of hours I spent over the weekend, this is "hard" to work with.

I found that if I set a breakpoint in Visual Studio, I could get a "dynamic" view of the returned object, and see its fields, but could find no simple way to find what type it was. I could not work out any sure way to obtain its class name, and then know for sure what it was, or what it contained.

To help with languages that have typing issues, or less direct control of the low-level COM Interop stuff, can I make a suggestion that should not be too hard to add, yet will be helpfl to users of the Logos classes.

Please consider:

For any class that is returned by the COM API, add a new field/propertiy, e.g. "LogosType::String" that holds the name of that object.

Then it would be easy to have a nest if-else-if-else-if-else or switch-case block that could know from the contents of that field what its got one of.

So, for above, I could do something like (VB):

dim x as object

x = myLogosDataType.Details

if x.LogosType = "LogosBibleReferenceDetails" then
' do something with it here
end if

This would only be important for classes that are "multi-choice", such as those that might be in the Details result above.

Thanks.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/143090#Comment_143090

For any class that is returned by the COM API, add a new field/propertiy, e.g. "LogosType::String" that holds the name of that object.

We are planning to implement that (or something similar) in the next release. We're currently leaning towards a "DetailsKind" property so that you can write:

If myLogosDataType.DetailsKind = "Bible" Then
' use myLogosDataType.Details
End If

This would avoid the need to write:

x = myLogosDataType.Details
If x IsNot Nothing AndAlso x.Kind = "Bible" Then
' ...
End If

JimTowler

https://community.logos.com/discussion/comment/143146#Comment_143146

Yes Please.

[ Attempting to work with the objects returned in Details at present is tricky, but what you wrote just above is great. It will also make it easy to work with from scripting and other places where its hard to use strong typing.

Sorry if I keep making ideas and suggestions re COM API (but you did ask for feedback). I've been surprised that no-one else seems to have much to say on this matter, so in the silence, I've just asked for the things that stop me for trying the ideas I am wanting to make work. It seems to me, that others would want these too, but its been quiet. ]

Fred Chapman

https://community.logos.com/discussion/comment/143176#Comment_143176

It seems to me, that others would want these too, but its been quiet. ]

We took a vote and decided let you do all the work and then we'll benefit from the fruits of your labor when you give it all away[;)]

JimTowler

https://community.logos.com/discussion/comment/143195#Comment_143195

We took a vote and decided let you do all the work and then we'll benefit from the fruits of your labor when you give it all away

Oh - OK.

Well I have version 3 of my own PBB working, and a new cool thing that lets you run the "New Sermon Wizard", and you can stay in bed an extra hour, while it writes great stuff for the next 3 Sundays ...

OK - just kidding [:)]

As documented and said by Logos, the COM API is mostly limited to Navigation matters. Even then, there are in my view, a few critical bits still missing. However, it does allow a few neat things. The one I most like is linking my ESV Bible in Logos4 to my MP3 Audio Bible I purchased from [Crossways?] or whoever.