Page 1 of 1

Interesting screen corruption

Posted: Tue Aug 24, 2010 8:22 pm
by dvdvnr
Just had this rather interesting screen corruption. I think I'd just done a wash of unwanted emails.
Screen Corruption 1.jpg
Screen Corruption 1.jpg (226.51 KiB) Viewed 5363 times
As you can see, one of the "washed" emails was still visible with the delete tick still showing. I have blurred the email addresses for security.

If I collapsed all of the different status sections then it was still displayed:
Screen Corruption 2.jpg
Screen Corruption 2.jpg (36.9 KiB) Viewed 5363 times
Minimising MW didn't fix the problem. I had to close and restart it.

David

Re: Interesting screen corruption

Posted: Tue Aug 24, 2010 8:41 pm
by anniebrion
This is a known problem with the grid software that is used by MWP, this is supplied by a 3rd party and as such is difficult to get fixed :(

Re: Interesting screen corruption

Posted: Tue Aug 24, 2010 8:49 pm
by rusticdog
If scrolling doesn't clear the issue, you can just clear the grid by pressing C then Y on the keyboard, then just recheck the account. Much faster than restarting.

Re: Interesting screen corruption

Posted: Tue Aug 24, 2010 10:17 pm
by dvdvnr
anniebrion wrote:This is a known problem with the grid software that is used by MWP, this is supplied by a 3rd party and as such is difficult to get fixed :(
Thanks anniebrion - ah, 3rd party software, fine until it isn't! :)

Re: Interesting screen corruption

Posted: Tue Aug 24, 2010 10:23 pm
by rusticdog
dvdvnr wrote:
anniebrion wrote:This is a known problem with the grid software that is used by MWP, this is supplied by a 3rd party and as such is difficult to get fixed :(
Thanks anniebrion - ah, 3rd party software, fine until it isn't! :)

It may yet be our fault in how we're using it, yet to be fully proven. :oops:

Though we're sure we're doing everything right so far.

Re: Interesting screen corruption

Posted: Tue Aug 24, 2010 10:30 pm
by dvdvnr
rusticdog wrote:It may yet be our fault in how we're using it, yet to be fully proven. :oops:

Though we're sure we're doing everything right so far.
Inconsitencies between how they say it works and how it actually works? Documentation at least 1 version out of date? Situation absolutely normal then (going by my experience) :roll: