Printable View
so my friend now I translated the rest of the words German and of course I will translate in Turkish lang for the user.
My friend
This beautiful program is not doomed to die. if you use it. and i use i do not give up. I love iGO without iGO I do not feel well. iGO live ..
Thank you for everything...
Spoiler: screen
[Only registered and activated users can see links. Click Here To Register...]
Average Speed(Primo) by Frontzosd_v1.1
Update For Primo.. Android and WinCe!
A bug in Serbia Variant fixed!
Now we can manually zerod the counters!
If the window appeared we can simple press over it!
And of course , all the switcs works correctly now!
Spoiler: link
And we have all the words we must translate in our language
Spoiler: translation for Dictionary Lang
My friend Titanic , you must check again your translation
Because I made some changes!
Hello, My friend frontzosd
Can you please write what is the difference between two ux I use now Italy edition,
Average Speed / Android / Italy edition, Serbia edition,
Thank you for answer.
Greetings from Germany. Titanic
Dear friend.
The difference comes from:
Where (in which camera id) , each country put the Average
Speed camera!
For Serbia ...
Only in Camera 12(Toll post Station)
The time start, each time we pass a Toll station!
The counters zerod at the moment we pass near from the next Toll station, after we have first the Average statistic results announcement, with the optical window!
Also We have the choice to have info window, when we pass, in every speedcam which exist untill the next Toll Station..(the cheque part)
Or not!
For Italy:
The Time start in Every Average Speed Camera
Speedcam id = 4
And stops in each Town Entry Point camera (id 10)
Between we can set points (we agree to use camera 22 My Poi ) for to
Appeared the info window for to know in some moments
Our Average Speed Results!(the Cheque part)
For
Both of the two edition I create a timer button, for to set
for how often we want the info window wants to appeared
And to info us about the Average results , during navigation untill this moment!(the cheque part)
Average Speed Cams (ASC) have never worked on any application (iGO, TT, Sygic,...). Never! The application sees the cameras but there is no solution when the average speed is stopped.Quote:
Originally Posted by Titanic52 [Only registered and activated users can see links. Click Here To Register...]
No one cameras database is not complete. Neither of the users nor the ones that sell the agency. Because the bases have only one camera for the way. It is not known where the average speed measurement ends.
ASC is a specific camera. It's not point, like other cameras. ASC refers to the section of the road. It is logical that the ASC (section road) is marked with the TWO cameras.
The only way to work on iGO applications is through UX.
Well, that means that ASC for Serbia is not a specific but logical attempt to solve the problem.
It would be good if the principle (TWO points) for ASC is accepted.
@mens
In any case you have always from any point to point
Your average speed results.
Give me the point you want (coordinates)
And you have it..
The mechanism exist (my ux)
The other you describe , is very .. very easy now!
----
What I am wrote pro your work and your UX?
Nothing.
This is my opinion about this complex problem.
And in my post is ... The only way to work on iGO applications is through UX...
That means that I think that your UX is very useful.
I think you misunderstood my comment.
In my opinion there is another problem.....
Who lives in Serbia uses the Serbia edition, who lives in Italy uses the Italy edition, but who travels to Europe which one must use?
Dear Frontzosd you will have to invent the Average Changer.....:ahah:
I have to solve some problems because in Italy there are several very long stretches, for example from Turin to Bologna, and there are several cameras that work both as "beginning" and "end". In Spain, I think that it works well, they do not have these anomalies.
I think I understand what Nens was going to say.
The problem is that GPS can not know which is the end point (there may be dozen of them along the highway). And when you get to them it's already late.
Maybe the problem can be simplified.
Actually, there is no need for another camera, or cameras at all.
Simply, the user has to choose the starting point (first toll), and a ux start from then counting, and shows the distance traveled and average speed for that time constantly. On one every minute or two. Or kilometer. Including stop time during road.
When the driver sees that he is left a few kilometers to the goal toll ramp, (or 10km to the city, or...) he will know what to do. And he must stop ux of further counting manually.
It's not necessary to know where is the points , for start and stop!
We don't care if we use ux for Serbia or Italy!!
It's useful to know , every time during navigation ..
(For example we can use the timer setting button!)
Our Average Speed results!
We can also manually zero the counters when ever we
Want!
This is the point!!