Separate names with a comma.
Discussion in 'Official V1Driver Discussion Section' started by mswlogo, Jun 26, 2018.
Yep, looking better already!
Note that when there is only 1 pin the horizontal axis is dimensionless. The only difference is I shifted the map slightly.
The chart calculates the "scale" on X Axis from the data. If there is only one point it doesn't know what to do.
Sometimes it does put a number. It could be a layout issue too, but I don't think it is.
I didn't write the chart. It's a 3rd party. It might need some parameter tweaking. I could add "fake data" (0 Y value) when it's just one point, but that is often bug prone.
I'm not overly concerned when it's just one pin because the primary purpose of the chart is to look at overall "distributions".
If you are down to a single pin, click the pin
I'll keep an eye on it though. I appreciate your meticulous feedback.
What you could do is widen your Sweeps and either mute those extra regions or attach a custom Voice (e.g. "Ka Out of Tolerance") so you can get a feel for how wide you want to set your Sweeps.
The main reason I added the mute anything is to cover the case where you can't disable the Pop region of Ka with Custom Sweeps on the V1 in addition to the extra non USA region on K.
Attaching the custom Voice is just for fun and some users on YaV1 used to attach unique WAV files to frequencies to ID a particular gun or ID jurisdiction based on what LEO's use which guns.
Version 22.214.171.1249 Beta release.
Enhanced - Mute in Box, Voice in Box, and Pin Editing will now automatically fill the content of the box you are editing with the current value (rather than display it only).
I hope this solves @Deacon issue with editing.
I love the V1 app, but have to respectfully say I haven't got a damn clue what you guys are talking about. As a result, I have to guess that means to not worry about these new features ( whatever they do).
All these new features allow you to do is something when a particular frequency is seen do something custom.
You can either mute it or have V1Driver day saw something about it.
V1Driver already did that. It would say Ka ahead or K behind. And was based on the frequency. Now you can be more selective over the frequency and what it might or you can decide to always mute it.
Certain frequencies can be problematic or mean something important. Like a unique radar gun is being shot at you in your area. So you might want it to call special attention to it.
Personally I don’t care and is why I put off adding this for so long. Most users don’t care. But a few users wanted it. And it was fairly easy to add.
This is definitely OCD geek territory.
You can safely ignore it.
Ah, great to know that some ignorance is bliss. Regardless of my cluelessness, kudos for developing and supporting a cool and highly useful App!
It does indeed, thank you. It’s really weird, though, that it doesn’t populate a field UNTIL you tap in that field. Otherwise it looks like an empty field with grayed out example values.
If you know officer Odie's frequency, you can have his proximity announced as "Officer Odie" or whatever you want. Maybe "Deputy Dawg Eating Donuts."
It’s just my preference of how I use that control. Those dialogs are built dynamically. You choose what options to use on the fly and no layout issues etc.
They are usually used for “new” data your gonna enter. Not for editing.
I had to provide labels and units.
There isn’t an easy way to add labels. But you can add a template (a hint for the user). I used that hint to show label, units and current value.
But once you type, the hint is gone. Standard behavior for that control.
So I added code to stuff only the value in their when it clears the hint, so you can “edit” the current value.
I could do full custom controller but that is a bit more work.
There are 3rd party libraries that extended this to have labels. But I try to minimize how much 3rd party libraries I use because they can add other issues. Like let’s say iOS 12 issue pops up and they have not updated their library yet.
So it’s all about ease of maintenance.
It wasn’t so bad on POIs but editing these required a real good memory and was a valid criticism
The state of Android V1Driver needs even more work in this area.
@Deacon this concern you raised is address in Version 126.96.36.1990 Thanks.
Note that you won't be able to test it without doing a restore to a database prior to this feature.
How does one go about updating the app, or does it do it on its own?
Both Official and Beta are automatic.
I add Beta users that tend to have more experience with V1Driver and/or V1 or found bugs that are fixed in beta.
I hope to release the current Beta to the App Store probably by the end of the week.
OK. Thank you Appreciate that information.
Not sure if this is normal or a bug. When driving an an area that has pins dropped from savvy user set speeds I noticed that new pins don’t always drop if I encounter radar unless im driving over the speed set from the savvy setting. Does this make sense?
Good observation. It does not drop new pins if you are under savvy speed. If a pin (new, learning, or locked) pin exists then it will promote, demote, and gather statistics.
This is to reduce an excessive amount of pins that you are always under savvy. If you are ever above Savvy then it will create a pin and process it as above.
So to confirm, although it doesn’t physically drop a new pin, it uses an existing pin to mark the area accordingly. Makes sense.
When you make the bata version official, does the app automatically update or do I have to go to App Store and redownload?
No. If you are above savvy speed it drops a pin. If later you are below savvy speed it will continue to update THAT pin.
If you are always below savvy speed in some location, it will never drop a new pin so there will never be no pin to update.
There is no point in adding PINs for things like Mall parking lots, which could generate a lot of unnecessary pins where you are always 5-10 MPH
The App will update like any other iPhone App update. You can hurry it along by poking it.