I have noticed an annoying problem with FTM 22.0.0.1345.
If I am working with a 'Residence' fact (a very common activity when dealing with Census records), and all three fields of that fact (Date, Place, and Description) are populated, and I then want to make an edit to the data in the Description field, the cursor (the I-beam) won't "stick" in the Description field if I move the mouse between putting the cursor in the Description field and typing the first character of the edit.
In other words, when making an edit in the Description field, if I put the cursor (the I-beam) into an existing description for the purpose of editing it by moving the cursor into the Description field and then clicking once, I have to be very careful to not move the mouse one iota before I type the first character of the edit. If I accidentally move the mouse after having clicked in the Description field (but before I begin typing the edit), the I-beam will disappear from the Description field.
I kind of suspect this is a programming error. It is very easy for me to reproduce this behaviour consistently. The problem doesn't seem to affect the Date or Location fields.
I would appreciate it if the programming team would take a look at this and perhaps fix it in the next service release.
I have attached a picture below with an arrow calling out the Description field. Note that the problem only seems to happen when editing a data string that is already present in the Description field - if that field is empty, the I-beam sticks in that space after the mouse is clicked once in that space, even if the mouse is subsequently moved.
Thanks,
Michael
Just a postscript: I just noticed that when I took the screen-shot (after clicking once in the description field), I must have bumped the mouse, because the focus shifted up to the picture area, which is not what I was interested in...