Quote: Originally Posted by
veetid 
We are working with Destinator to improve the SDK regularly... I am adding support for TMC as one of the next improvements, among other things...
I am also working with the HQCT developer to get the TMC data to pass directly into Destinator...
david
Nono don't get me wrong

The DestinatorSDK is okay (and leading the market) and Flux should continue with Destinator IMHO - the Problem is Navteq they need a very hard kick in their butt - and an OpenSource Navigation using different MapFormats or their SDAL Format is a kick for them (and they can't stop that ... in Germany for sure).
If CF was in the beginning I would say contact the NavIT project and go this route as a big sponsor.
Destinator's SDK is... yeah okay... but not "WOW" !
Example:
To get the Data into Destinator there should be a seperate Object "TMC" this seperate Object should (mainly) have an Event
Code:
NewTMCmessage(ByVal _LocID As Short, ByVal _EventID As Short, ByVal _Extent As Byte, ByVal _Dir As Boolean, ByVal _Diversion As TriState, ByVal _Duration As Byte)
This event is fired by the object if a new TMC message arrived - now this object should be placed in a seperate Assembly - Inside this object is per default the handling with gpstmc.dll (for the GPS/TMC mice).
For the Centrafuse-usage this object inside its assembly needs to be replaced by you...
(the (PDA) community could rewrite this object for Royalteks GPS/TMC mice)