[fixed] "clear filter notes"
[fixed] "clear filter notes"
That command (the X at the right of the search box) doesn't work for me in MyInfo 7. Is anyone else having that problem?
Bill
I've now double-checked, and I find the X command does in fact work on the screen of my Surface Pro. So once again the problem seems to be connected with my medium-resolution (1920 x 1080 pixels, 23") second screen.
Bill
I'm having the same issue for the Filter search box. MyInfo 7.0.5 build 6393
So, you click the X and nothing happens? Or the text in the quick filter is cleared, but the results are not refreshed?
The X in the filter box does nothing. Doesn't respond to mouse (over). And clicking has no effect either. Uploaded a screencast
If you click in the quick filter edit box and press ESC there, does it clear the text and does it reset the filter as expected?
Hmm, needs further investigation. Now it's working again The button is highlighted on mouse over & clicking it works. Mystery to me.. However, surely not the first time it refused to work..
And it's blocked again. Still no clue what I did to produce it.
1. It global problem. The button is blocked for all open databases
2. ESC is working as expect.
1. It global problem. The button is blocked for all open databases
2. ESC is working as expect.
Finally, a way to reproduce the annoyance
1. Open notebook A.mnb (dropbox)
2. CTRL+SHIFT+K
3. Search dfc & Enter
4. Delete & confirm
5. View -> Trash
6. Empty trash
7. Undo trash + delete in the revision manager (two steps back)
8. Go out of trash (green arrow or view -> Trash)
9. Type dfc in the filter
10. Try to click the empty filter box cross -> Not responding
1. Open notebook A.mnb (dropbox)
2. CTRL+SHIFT+K
3. Search dfc & Enter
4. Delete & confirm
5. View -> Trash
6. Empty trash
7. Undo trash + delete in the revision manager (two steps back)
8. Go out of trash (green arrow or view -> Trash)
9. Type dfc in the filter
10. Try to click the empty filter box cross -> Not responding
I was not able to reproduce it with these steps, but this issue should no longer happen with build 6434.