Google Maps über COM (Component Object Model)

[HJay]

Ich habe das Problem jetzt gelöst bekommen -- mit der live-Erzeugung des Reg-Key vom Programm aus. Keine Ahnung, warum das sonst nicht will. Immerhin geht es jetzt und das ist super: Rahmenlos und mit Scrollbars.

Danke für Deine Hilfe, der Reg-Key war der Kern der Lösung.

[Thom]

Super!
In der Version 3 wird diese Funktion auch mit integriert sein.

[DelphiFan2008]

Hallo Thom,

ich hatte vor ein paar Tagen Probleme mit Marker und dem OnClick Event. Dein Vorschlag war

Delphi-Quellcode:

procedure MarkerClick(Sender: TObject; Event: gmEvents.TEvent);
[...]

die Fehlermeldung kam immer noch, habe gesehen dass HJay ein ähnliches Problem hat und dazu deine Antwort

Delphi-Quellcode:

uses ..., HTMLObjekts, ...

procedure MarkerClick(Sender: TObject; Event: HTMLObjects.TEvent);
[...]

mit Hinweis auf noch ... Version 2.0 ...

Bei mir tuts nach dieser Änderung und einigem probieren und suchen auch

Gruss DelphiFan2008

[Thom]

Entschuldigung wegen der verursachten Verwirrung - das liegt daran, daß ich gedanklich voll in der neuen Version stecke und zum Testen immer die "alte" Version hervorkramen muß. :?
Wie schon öfters geschrieben: In der Version 3 wird vieles einfacher. :-D

[swaters]

Thom,
I was wondering how I would create a copy of the Response from a directions request.
I've tried a few methods but no success.

Thanks in advance.

swaters

[Thom]

Hi swaters,

Sorry - this is currently only available by using the internal function CreateObjectWrapper.

Delphi-Quellcode:

uses
  ..., JScriptObjects, //<- function CreateObjectWrapper 
  gmAPI, ...;

type
  TDirectionsResultAccess = class(TDirectionsResult); //for Script-property-access (currently protected)

procedure xxx.DirectionsCallback(Sender: TObject; Result: TDirectionsResult; Status: String);
var
  CopyFromResult: TDirectionsResult;
begin
  CopyFromResult:=TDirectionsResult(CreateObjectWrapper(TDirectionsResultAccess(Result).Script,TDirectionsResult,Result.Disp));
  [...]
end;

In the next version interfaces are used, so that the Result-object is not lost (destroyed).
The property Script will be public.

[swaters]

Thanks Thom.

Great project. Have watched keenly for awhile now. Still having trouble grasping some of the concepts.

Thanks again.

[Thom]

Thank you very much! :-D

I made some illustrations. Maybe they help to understand the concept of the framework a little bit better.
Image1
Image2

Do you have other ideas or questions for a better understanding?

[swaters]

Zitat:

Zitat von Thom (Beitrag 1194609)

Thank you very much! :-D

I made some illustrations. Maybe they help to understand the concept of the framework a little bit better.
Image1
Image2

Do you have other ideas or questions for a better understanding?

Thank-you Thom.

Funnily enough I do have another question. I bet you weren't expecting that eh?: Roll:

In your post #129 you attached a compiled program, DirectionsWithMultipleDestinations.zip. I was wondering if you could explain how to achieve that?

Your previous answer worked as I was hoping, thank-you again. This question is an extension of the other.
I now have my DirectionResults in a usable ObjectList and can render then through repitition. But each time I call DirectionsRenderer[0].SetDirections(FResultList.Items[i]) the previous render is erased. This is not what I am trying to achieve.

Your compiled example in post #129 seems to achieve what I am trying to do.

Thanks again, and Thanks in advance.

[Thom]

No problem. :lol:

Each DirectionRenderer can only display one (!) route. The renderer will pass a new route, the previous is removed.
If different routes are shown, several renderers are needed. In the example #129 are this three different routes and therefore three renderers.