@nmnandakishore You are welcome.
By the way, you might be interested in viewing this post containing the materials used during my last meetup which was focus on QtLocation - you could find helpful tips for managing maps, point of interests and route.
QtLocation und QtPositioning sind erst ab Qt 5.5 als TechPreview verfügbar.
Willst du nur Kartenmaterial mit dem Plugin zur Verfügung stellen? Oder auch Routing, Places, etc?
Stimmt QtLocation Modul gibt es sehr viele Klassen die einem schnell den Überblick verlieren lassen, aber wenn man mal den Überblick hat ist es eigentlich recht einfach.
Am einfachsten nimmst du dir den source-code vom "Original" plugin her.
I understand your advice. 1 app access the file and the other app communicate directly to the first app. However, I aimed to use a memory-mapped-file just because I read some articles where it said this is one of the best practice to communicate two process without lossing information. Is this correct?
I am really interested in your advices, so I present my case:
GUI <-> MainAPP <-> SPortAPP
GUI can be anything made for anybody with the only requirement of implementing a protocol/API to communicate to MainAPP. (e.g. sockets)
MainAPP is my application who implement mathematics, logic, etc and defines the behaviour of my system. It cannot lose any information so I thought I might save it on a file.
SPortAPP is a propietary protocol implementation whereby external systems read/write information to the database of MainAPP . This app shouldn't interact directly to MainAPP
So, Such information must be available to read and write by both MainAPP and SPortAPP.
what is your opinion about it? Do you reccomend any other type of implementation?
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.