CF1.6 MapPoint 2K4 Plugin Alpha Source Code Now Available - Page 2

midiwall · 09-04-2006, 12:37 AM

Quote: Originally Posted by josgab

Hi i'm installed cf plugin but not work with the last release of centrafuse i have mappoint 2006.
any solution pleaseee

"but not work" is pretty vague... What are the specific symptoms?

Are you having issues getting a button configured to launch it? Does the plugin load Mappoint but the GPS doesn't lock? Do you get a message saying that it can't find maps?

Which version of CF is this?

black06stang · 09-04-2006, 09:46 PM

Will CFmapoint2006 work with RC2?

midiwall · 09-04-2006, 10:17 PM

Quote: Originally Posted by black06stang

Will CFmapoint2006 work with RC2?

Yes, that's the setup that I'm running in my truck.

Did you try Paul's 0.82 that he released on 9/1?

midiwall · 09-04-2006, 10:23 PM

Quote: Originally Posted by josgab

Hi i'm installed cf plugin but not work with the last release of centrafuse i have mappoint 2006.
any solution pleaseee

Hi;

I just replied to your question on the CFMapPoint dev space. You gave more information over there, (that you only have NY and Berlin maps), so I'm thinking that you're actually running Destinator under CF and not Mappoint. the CFMappoint plugin doesn't _replace_ Destinator (the stock nav system in CF), it installs along side of it.

To use CFMapPoint, you have to create a button in CF to launch the plugin. Have you done that, or are you still clicking the "NAV" button and thinking that will launch MapPoint?

midiwall · 09-06-2006, 09:13 AM

{paraphrased from my post on Paul's dev site}

You need to create a button for CFMapPoint. To do this:

In CF, go to SETTINGS, page DOWN one and you should see BUTTON LAYOUT. Select it, then hit SETUP.
This is where you configure the buttons that appear all over CF. The first set are the buttons that appear in the MENU drop list, then come the first page, then the 2nd, then the 3rd. Pick an empty spot, then click SET.
Scroll through that list until you see "CFMAPPOINT". Select it, and click OK.
Click CLOSE, then CLOSE again.
Flip through the pages until you find the button labeled "CFMAPPOINT".
Click it.

paulpv · 09-12-2006, 11:04 AM

Good news: My condo has an offer and is going forward to close on 8/12. I will be putting an offer in on a house to close hopefully around the same time (it will be tight). After that I should be able to concentrate more on getting CFMapPoint stabilized and v1.0 out the door.

I still use CFMapPoint myself and am fully aware of many of its problems of needed improvements.
There is a reason why I shared out the code folks!

Is anyone having *any* problems w/ getting CFMapPoint to at least *run* with either MP2K4 or MP2K6?
I am aware of some GPS imprecision and resume problems, as well as some required manual setup issues.
I will fix the GPS issues next, as well as look in to automating some last setup steps.

Are there any other known *blocking* problems?
Please post your comments either here, or preferrably on the project's site:
http://workspaces.gotdotnet.com/CFMapPoint

Thanks for the understanding of the delays!

Pv

paulpv · 09-12-2006, 11:10 AM

Quote: Originally Posted by midiwall

Yes, that's the setup that I'm running in my truck.

Did you try Paul's 0.82 that he released on 9/1?

midi, have you noticed any GPS precision problems?

Pv

midiwall · 09-12-2006, 01:04 PM

Quote: Originally Posted by paulpv

midi, have you noticed any GPS precision problems?

Kinda', but neither instances were your issue.

I had a period of about a week where it looked like you were dropping the minus sign of the longitude, so West was becoming East (e.g., 46.80/-110.20 would become 46.80/110.20).

In digging through it I found that all of my GPS aware apps were doing this so it wasn't an issue with CFMapPoint. "Fix" wise - hard to say... It kinda' "just stopped" doing it. You know I'm a developer as well, and I HATE that crap, but I really didn't do anything 'cept a slew of reboots over a period of days.

The only thing that I actually touched was Xport3 where I shifted virtual COM ports. It may or may not have had something to do with it, but once the problem went away, I couldn't get it to come back. weird.

Past that... I've seen a couple of instances of the "20 miles off" thing, but it pops back into sync in a few minutes. I chalk that up to GPS interference (trees, mountains) and MapPoint is guessing wrong when trying to fill-in-the-blanks.

clarkie · 09-12-2006, 02:48 PM

The reason for this error is a rounding error in the routine ConvertDegreeMinuteSecondToDegrees in the origional int32 was used.

I am assuming that the same code was used.

In my case when in Southampton UK the GPS had me located in the middle of english channel. At home 8 miles away all was ok.

/// <summary>
/// Expects input in dddmm.mmmm or ddmm.mmmm format
/// </summary>
/// <param name="input"></param>
/// <returns></returns> private double
ConvertDegreeMinuteSecondToDegrees(string input)
{

if(input == null || input.Length <=0)
return 0;
double inputvalue = Convert.ToDouble(input);

int degrees = (int)(inputvalue/100);

return degrees + (inputvalue - (degrees * 100))/60;

}

paulpv · 09-12-2006, 04:11 PM

Quote: Originally Posted by clarkie

The reason for this error is a rounding error in the routine ConvertDegreeMinuteSecondToDegrees in the origional int32 was used.

Danka! I will try to add that fix soon!

Pv

paulpv · 09-19-2006, 03:51 PM

Quote: Originally Posted by paulpv

Danka! I will try to add that fix soon!

Pv

I have added the fix and will try to release a small patch today.

Pv