RE: Re: .NET xPLLib "feature"

["Ian Lowe" <ianlowe@xxxxxxxxxxxxxxxxx>]

I'd have to check the source to be sure, but I'm guesisng they are parsing
it out from the xplmsg.content object (which is the entire message as
received).

This is what we did as a workaround for now, but given the richness of info
available about a message from the assembly, it seems more like an accident
than a design decision that there doesn't appear to be a reported value
with
the message type in it.

I'll add the code and pass the bundle back to John for checking :)

Ian.

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On Behalf
Of Mal Lansell
Sent: 12 December 2005 10:48
To: ukha_xpl@xxxxxxx
Subject: [ukha_xpl] Re: .NET xPLLib "feature"

How are the other apps managing it?

Mal

--- In ukha_xpl@xxxxxxx, "Ian Lowe" <ianlowe@x...> wrote:
>
>
> Or rather, the lack of one..
>
> Myself and Jen are building an app and it struck us that we can't
actually
> get the message type from the .net assembly - there doesn't seem
to be a way
> to find out whether this is a stat, trig or cmnd message.. Which
is a little
> odd!
>
> I have the source for 4.1 here, so I guess I could add the
required public
> sub in easily, I'm just a little curious..
>
> Ian.
>
> Ps> also rebuilt the assembly for VS 2005 - working nicely now :D
>