Inbox Focus jumping to the top after move to trash or folder

HCL Domino Domino Forum
1

I have been noticing an issue with a couple of my email users where the focus jumps to the top of the inbox after the trash icon is used to soft delete an email.

This also happens when using the move to folder icon.

One would think, especially when dealing with users who have very long lists of emails that the focus would remain at the same position after a move to trash or folder and indeed it does work that way some of the time, just not reliably.

The secondary problem that this can cause is that it actually ticks/selects the first document in the inbox and on the next move it grabs the first document along with the new selection and moves that too.

Has anyone out there also see this issue?

All users are on 8.5.2 clients, using Windows XP and on the latest 8.5 mail template.

2

Subject: Same problem - inbox focus moves randomly to top

I also have several users reporting this problem in 8.5.x, and possibly also 6.5.4 ( we have a mixed bag of clients, unfortunately). The servers are 8.5.1 FP1. It appears to be fairly random - accdg to the users, it may occur one day and not the next. They insist they do not have any column sortings active in the inbox ( not that that should matter, but still). I’ve found a report from 2004 (http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/72a6b441dc50fd2185256e68005e779e?OpenDocument) that seems to be about the same problem - so maybe it’s an old bug?? Any ideas, anybody?

3

Subject: Inbox: Email Selection Issue - Solved

Here is a very clear example of the issue.

  1. User Selects an email and moves the message to a folder

  2. Lotus Jumps to the top of the view area and auto selects a document/email. (Email 1)

  3. User Selects a different email to move. (Email 2)

  4. Note that despite that there are 2 ticked documents in the view, the status bar only shows that there is one document selected.

From our investigation, it seems as though the tick on Email 1 is misleading.

From a logical standpoint, although it appears selected/checked, Email 1 is not a part of the collection of db.unprocessedDocuments.

Email 2 is the only email truly selected or apart of the db.unprocessedDocuments collection.

This means that although both appear to be selected, only Email 2 will be moved to folder on the next move.

  1. At this point the user wants to move the Email 2 to a folder.

As the user sees that both documents are selected AND not wanting to move Email 1, the user then DESELECTS Email 1.

This is the most puzzling thing of all.

Note that although Email 1 is not selected (ie has no check mark) the number of selected documents in the status bar has increased to 2.

Our conclusion here is that the DESELECTION is actually causing Email 1 to enter the db.unprocessedDocuments collection!!

  1. Now the user sees only that Email 2 is selected and decides to move the email BUT because Email 1 is secretly apart of the db.unprocessedDocuments collection, IT GETS MOVED TOO!

I tried EVERYTHING to solve this issue,

  • compact

  • fixup

  • used cleanup tool and reinstalled

  • deleted caches

  • new copy of mail file

  • new replica of mail file

  • new computer with fresh install

After a very lengthy process with IBM support we found that the cause was due to none other than the user’s SCREEN RESOLUTION!

It appears there is a BUG when working with the Lotus Notes Mail file on high screen resolutions where there are more than 50 rows viewable in the inbox.

Lowering the resolution solved the issue.

So far I haven’t had any assurances that this will be fixed.

Bit disappointing seeing as though more and more people are working on higher resolutions and screen sizes seem to only be getting larger.

Hope this has helped someone out there and that IBM take this under advisement.

  • TB
4

Subject: Does rename <data_directory>/workspace help?

If you rename the <data_directory>/workspace, restart the client, it will create a brand new workspace directory, and thus remove any corrupted data, if any.