Tab is really slow.
I do a lot of reviews and the tab function is really slow and many times skips fields.
Send this for your information. Maybe so fix needs to be done to the program. Working on City directories
Tab is really slow.
I do a lot of reviews and the tab function is really slow and many times skips fields.
Send this for your information. Maybe so fix needs to be done to the program. Working on City directories
0
Best Answer
-
In some cases, images with hundreds of names may cause the indexing program to slow down significantly or freeze. If this happens to you, please close your internet browser and open it again.
0
Answers
-
I did that several times
0 -
Can you please share the batch ID you are working on.
Cache or cookies afect the proper functioning of your computer:
- Your computer does not respond quickly and efficiently.
- Data on FamilySearch displays poorly or not at all
If you clear all cookies, it can affect your access to other websites. Try these steps first:
- Make sure you use a supported Internet browser: Mozilla Firefox, Google Chrome, Microsoft edge
- Delete just the cookies that FamilySearch uses.
- Go to https://FamilySearch.org/cookies.
- When the message Reset your cookies? appears, click Yes.
- If the problems still occur, clear all of your temporary files and cookie. Then restart your computer. Please search the web for instructions for your specific browser.
Try the steps indicated above and let us know if the problem persist.
0 -
If the other suggestions don’t sufficiently help, try switching from Table Entry Mode to Form Entry Mode. I like to move the Form to the right of the image (click the 3 dots) so that I can read across the image left to right (using the ruler to guide me) and index down the form top to bottom. I also reorder the Fields to match the image, putting the Directory Place and Directory Date at the bottom (out of the way). The size of the batch doesn’t noticeably affect the brisk performance of Form Entry mode. I use Column Entry Mode selectively to augment Form Entry mode, and Table Entry mode only for the occasional QC. Or if you really like the look and feel of Table Entry Mode, try Row Entry Mode. It gives you a very short table (1 high) that should respond much better than Table mode.
0 -
Batch ID [M34C-5
0 -
I am, and always have used form entry. Still rotten tabbing.
0 -
Wow. That is surprising. Please repost the Batch ID. It looks like part of it is chopped off. Thanks.
0 -
would using the enter key make a difference?
0 -
It might, but the Tab Key and Enter Key have different effects. It depends upon what behavior @ShirlJNichols wants whether Enter is acceptable, even if it is more responsive. But if @ShirlJNichols has auto-suggest off, then Enter might be faster and have the same effect as Tab. From Keyboard Shortcuts listing:
In Universal Input Mode (12/04/2017):
Enter and Tab are the biggest differences:
• Enter accepts the highlighted auto-suggest value, if one exists, and advances to the next field.
• Tab keeps only what you typed and ignores the auto-suggested values and advances to the next field.
• Right Arrow accepts the auto-suggested value and keeps you on the same field so you can keep typing. Auto-suggest continues to make suggestions as you type.
0 -
Can you please share the batch ID you are working on.
Let us know if clearing the cookies, or changing the browser made any difference. SOme question to think about: How old is your computer? are you using laptop, computer desk, tablet, are you using an external monitor attached to your main device.?
Try John's advise of changing the format of indexing from Form to Table or Column.
0
This discussion has been closed.