Frontzosd Silver Skin for New NextGen 64 bit apps!

**Cheldron** · 18th September 2024, 02:13 PM

When click on the "Information" button, data is displayed that includes "Height". Part of this data is voiced by TTS. After the word "Height", its numerical value is said, and the word "meters" is not translated into russian. How is the word that voices the units of measurement of height written in the ux-plugin? The word "meters" is not suitable for translation in this place.

Spoiler: Screenshort

**AnthonyGreek** · 18th September 2024, 02:46 PM

Hi Cheldron,

It's one of these two:
m="метр"
meters="метр"

**Jozs** · 19th September 2024, 08:25 PM

@Alain57
Did you manage to find a solution to the French TMC problem? (post #293,#294,#297,#298,#300)

@everyone
How does the program know, or should it know, that the average speed measurement phase is over?

**Alain57** · 19th September 2024, 09:05 PM

@ Jozs

Unfortunately not !

**Papp G** · 19th September 2024, 09:38 PM

Originally Posted by Jozs

How does the program know, or should it know, that the average speed measurement phase is over?

There is a camera at the beginning and there is one at the end, between the two it calculates the average based on the elapsed time. It doesn't measure speed, just time. When you get to the second camera, the measurement should end!

**kwbs** · 19th September 2024, 11:22 PM

Originally Posted by Jozs

How does the program know, or should it know, that the average speed measurement phase is over?

The last camera will be set for speed of 5 km per hour.

34.000000,31.000000,4,5,1,154

You are welcome to look at a virtual exercise on ASC that I did on a road section, which has no such cameras but there is a speed arbiter with "laser guns":

[Only registered and activated users can see links. ]

**waldek** · 20th September 2024, 07:31 AM

Originally Posted by Papp G

There is a camera at the beginning and there is one at the end, between the two it calculates the average based on the elapsed time. It doesn't measure speed, just time. When you get to the second camera, the measurement should end!

This is how it works in older versions of iGO 9.18... In newer versions of iGO 9.35... unfortunately it doesn't work like that. You have to manually turn off the measurement at the end of the measurement section. Unless I missed something.

**frontzosd** · 20th September 2024, 08:58 AM

and who's going to stop me from making zeroing the counter work this way?
We don't care about edition?

"to reset the counter automatically, immediately After the camera?
and let it count again
until we meet next camera?

Spoiler: photo

**frontzosd** · 20th September 2024, 06:28 PM

And this edition....Automatically reset Average Speed counters, Only if we have "Really" Speedcams!, Not "Simple" Alerts!
I think this is the correct way!

but even so, even though the result of the measurement is more correct
because of zeros...
and re-measurement and elimination of cumulative errors, the measurement comes from the application's computer.

For the next update:
I thought the next measurement should be done by dividing the distance of the cameras by the time...

display of course every time we have a real camera...
and compare the result....

**Papp G** · 20th September 2024, 08:16 PM

With this, the amendment #260 was lost again:
"Couldn't the red background only turn on when we exceed the permitted speed with the set value, just as the color of the letter turns pink?"

Thread: Frontzosd Silver Skin for New NextGen 64 bit apps!

Thread Tools

Display

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions