Changes with the frontend...

**Ninja Monkey** · 01-22-2005, 09:10 PM

Following the recent events with destinator, there's going to be a few changes with the frontend...

1. the SDK will no longer be provided with the download. Until it is made clear whether or not I am allowed to distribute it freely then it must be obtained/purchased from PowerLoc. This means I am making no code other than my own available for download

2. the name of the frontend is going to change. I don't want the word "Destinator" or "Frontend" in there anywhere. I need you guys to come up with something because I'm not very creative

3. for now the website is back up, but the downloads aren't until I have removed the DLL's from them. The domain/logo will remain until we're clear on a new name

I'm going to hold off releasing 1.1.3 official until we've got a name, this is so I can make all the required changes to the code without having to release an update later on

**Pho** · 01-22-2005, 09:42 PM

Mmm.. a synonym of destination is 'target' how about 'TargetGPS' or something?

**rando** · 01-22-2005, 09:54 PM

You know I read that email you posted completely differently. Is it possible they were looking to license the maps to you so you could include them with your PC based mapping program (currently unnamed)? Perhaps I'm just being optimistic but generally when a company thinks you've infringed on them in some way you get a letter from a lawyer that is MUCH clearer about what they expect (cease and desist, pay damages, etc).

...just a thought.

**0l33l** · 01-22-2005, 09:55 PM

Navigator

BTW: The SDK is going great. I just wish I could send multiple commands at one time because Delphi likes to combine outgoing messages unless I put in a sleep function

It would also be cool if I could send text right to the textbox through code

Oh yeh, fill in some of those "not implemented" commands

**Ninja Monkey** · 01-22-2005, 10:03 PM

Originally Posted by 0l33l

Navigator

BTW: The SDK is going great. I just wish I could send multiple commands at one time because Delphi likes to combine outgoing messages unless I put in a sleep function

It would also be cool if I could send text right to the textbox through code

Oh yeh, fill in some of those "not implemented" commands

You can send text to the input boxes using winsock

You will only recieve "Not Implemented" if advanced mode isn't on and it needs to be

**Ninja Monkey** · 01-22-2005, 10:04 PM

Originally Posted by rando

You know I ready that email you posted completely differently. Is it possible they were looking to license the maps to you so you could include them with your PC based mapping program (currently unnamed)? Perhaps I'm just being optimistic but generally when a company thinks you've infringed on them in some way you get a letter from a lawyer that is MUCH clearer about what they expect (cease and desist, pay damages, etc).

...just a thought.

I didn't post the entire email, just one of the quotes. They go on about my "activities" and such

**rando** · 01-22-2005, 10:08 PM

Ah ok, I figured there was probably more to it. I hope it works out OK for you!

**0l33l** · 01-22-2005, 10:08 PM

Originally Posted by Ninja Monkey

You can send text to the input boxes using winsock

You will only recieve "Not Implemented" if advanced mode isn't on and it needs to be

Ah! That should do it

Too bad I still need sleep events which slows down the whole favorites thing

I'll try to think of something for that.

[Edit]: Oh yeh, a full screen function would be nice

**Ninja Monkey** · 01-22-2005, 10:12 PM

Originally Posted by 0l33l

Ah! That should do it

Too bad I still need sleep events which slows down the whole favorites thing

I'll try to think of something for that.

I don't understand, why do you need sleep events?

Can't you create a loop that will wait for a response before sending the next command (while doing a Application.ProcessMessages so the code won't pause)

**0l33l** · 01-22-2005, 10:14 PM

Originally Posted by Ninja Monkey

I don't understand, why do you need sleep events?

Can't you create a loop that will wait for a response before sending the next command (while doing a Application.ProcessMessages so the code won't pause)

The problem is that I can't get the response with the component I'm using at the right time. I'll figure something out.