Two UI gripes

[MBiddiscombe]

I'm running MWPro 7.12.6, on Win10 Home (Version 1903, build 18362.388).

I have two gripes about the UI. The first is arguably a missing configuration option. The second is arguably a bug.

1) The horizontal separators "Today (n items)", "Yesterday (n items)", "Last week (n items)", "Last month (n items)" and "All time (n items)". I don't find them useful, and would love to just make them go away. But they don't seem to be configurable.

2) When you have more mails that will fit on a single screenful, so you have to scroll to see the bottom of the list, then if you tick the 'Delete' box for that email, the whole list scrolls backwards by one email (so the one you've just ticked scrolls off the bottom of the screen). Why?! Surely that's a bug. Whenever I tick the 'Delete' box, I want to be able to see that the one I've ticked was the one I meant to tick. But that means that *every* time I tick the 'Delete' box for the last mail in the list (which is a very frequent use-case, if the list is sorted chronologically), then I have to scroll back down again, just to visually verify that the one I ticked was the one I meant to tick.

[rusticdog]

If you right click on your Received or Sent column heading, uncheck the Group By option, that will eliminate the email groupings.

The second issue certainly sounds like a bug, though I cannot reproduce it. Are you just mouse clicking in the delete check box ?

[MBiddiscombe]

Thanks for the solution for the first one. Done that, and it's what I wanted. Why was it so hard to find?

On the second one, it's 100% reproducible for me. As soon as I have more than a windowful of mails, and with the list scrolled fully down, then selecting (or unselecting) the 'delete' icon for any of them, actually, not just the bottom-most one, causes the list to scroll upwards by one item's worth (moving the bottom-most item out of view).

I've uploaded a screen recording of it happening: here.

[rusticdog]

OK great, thanks for that video. Can you first install the same version I have, just in case.
It'll install fine over the top http://cdn.firetrust.com/downloads/mail ... _12_10.exe

[MBiddiscombe]

Upgraded to that version; behaviour is identical.

Annotation 2019-10-23 105626.png (47.61 KiB) Viewed 5606 times

[rusticdog]

OK great.

If you can also fire me a set of logs. It's the UI settings I'm interested in, to see if I can reproduce the behaviour.

If you go Help >> Send Support Logs >> enter a brief note like 'as per forum' >> in the Ticket Number field enter chris >> Send Logs >> reply back once sent, so I can check their arrival.

Cheers

[MBiddiscombe]

Done.

[rusticdog]

Great, got them thanks, will keep you posted.

[rusticdog]

I can reproduce the issue if I first use Select All or the Delete option in the column heading to mark or unmark all for deletion. Is this something you also do ?

Edit : It also doesn't seem to happen when the window is maximised, not that this matters, just an observation.

[MBiddiscombe]

I never (well, virtually never) do "Select All", but I do regularly use the individual tickboxes in the Delete column (as in the video), and that's what triggers the issue for me.

[MBiddiscombe]

Just noticed that it also happens if I click on the 'Classify' option for a mail (but only if doing so results in its 'Delete' option being toggled). So "Thumbs downing" a good or neutral mail triggers the behaviour; but "Thumbs downing" an already bad mail, or one already checked for deletion, does not. Likewise, "Thumbs upping" a bad mail currently marked for deletion also triggers the behaviour, but "Thumbs upping" a neutral one not marked for deletion doesn't. It doesn't have to be the last mail in the list. (That suggests to me that it's the change in deletion status of a mail that triggers the behaviour, rather than necessarily directly clicking on the 'delete' checkbox.)

[MBiddiscombe]

Just upgraded to 7.12.25. The "list scrolling back by one" UI bug is still there, I see.

[rusticdog]

Yeah sorry, still on the fix list. We hoped the new grid update would resolve a lot of these, but sadly this was not one of the issues corrected.