How to clear out all auto-suggested point descriptions during manual typing?

[Dragonsnake]

Hello all. I have had my Javad LS-Plus for almost 3 years now. And in that time, I have typed in countless thousands of descriptions into my point description box.

The problem is that when I go to type in a description that has a common starting prefix, such as 'e' for "ep" which stands for "edge of pavement", I have so many other descriptions that start with 'e', that the entire collector slows to a crawl and literally freezes for a few seconds as it tries to search for all the other terms I've typed in that starts with 'e'.

I was wondering then, is there a way to clear out all of the stored and remembered typed in phrases for point descriptions? Or literally anything ever typed in? This would be very helpful if I could do that.

Also, is there a setting somewhere where I could ask the data collector to NEVER remember typed in point descriptions? So it does not auto-suggest anything while I am typing something in manually. I think that would speed things up really quick. I have an old trimble tsc3 data collector that does not ever suggest previous typed in things and it is very quick and snappy.

Thank you for your time.

 

[Matt Johnson]

You have to clear the keyboard dictionary.

Files > Delete Files > Clear Keyboard Dictionary

I agree that an option to disable the keyboard dictionary is needed for point descriptions.

 

[Nate The Surveyor]

Suggest:
It only keeps a memory key stroke for a settable time... like a month or 3 months, or something like that. Then, they fall off the end of the table.
OR, it keeps them for a number of shots, such as 300 shots, then the stack keeps sliding into the abyss, or some number between 10 and a thousand.
Nate

 

[Matt Johnson]

Suggest:
It only keeps a memory key stroke for a settable time... like a month or 3 months, or something like that. Then, they fall off the end of the table.
OR, it keeps them for a number of shots, such as 300 shots, then the stack keeps sliding into the abyss, or some number between 10 and a thousand.
Nate

For point descriptions that are often repeated it is easier and more desirable to use Codes for these and then if you need to enter additional information use either the attributes or Point Description field.

 

[Nate The Surveyor]

OR.... make it job specific, and key stroke counting. So, if you have 100 key strokes, it falls off the end of the table, but it stores a file for each job.
This way, it cannot get full, and it never goes slow.
Point codes.... I have never figured out how this works. Is there a tutorial?
Nate

 

[Matt Johnson]

OR.... make it job specific, and key stroke counting. So, if you have 100 key strokes, it falls off the end of the table, but it stores a file for each job.
This way, it cannot get full, and it never goes slow.
Point codes.... I have never figured out how this works. Is there a tutorial?
Nate

Codes are covered in the Quick Start Guide:

 

[Dragonsnake]

Thank you Matt that worked perfectly. You really are the 'Javad Guru' around here!