[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [trojita] [Bug 324309] Disconnected for inactivity
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2013-08-31 14:02:34
Message-ID: bug-324309-17878-ufdYQ3fsb3 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=324309

--- Comment #2 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to comment #1)

> Trojita will periodically ask for a STATUS of the visible mailboxes 
> ("visible" == shown on the left). The IMAP standard guarantees that INBOX 
> shall always be present, so there will always be at least one mailbox to 
> poll. However, this polling does not happen when no mailboxes are "visible" 
> (It's based on calls to QAbstractItemModel::data() via QTreeView after the 
> model emits dataChanged; I know for sure that those mailboxes which are not 
> visible in the view's viewport are not polled, and I don't know whether 
> this hapens also when the window is minimized or in the systray, for 
> example.

I didn't see any explicit calls to data() for "visible" items in the code, so
this probably relies on the access through the repaint in return of the
protected dataChanged() slot of the view - and in this case the answer is "no".
All widget repaints are compressed for invisible widgets since "show" will
trigger a repaint anyway, so repaint won't cause a paintEvent here.

This should fail if
- the "left" splitter part is collapsed
- the "one item" layout is used and on the "wrong" view too long
- the window is minimized (and not kept mapped by the compositor for a "live
thumbnail")
- trojita "minimized" (actually "closed" ;-) to systray

This is also the pending main issue (resp. it's trigger) with multiple accounts
and there needs resolution to either explicitlly disconnecting collapsed resp.
completely invisible (out of widget bounds) accounts or by explicitly calling
to the data of one index (per account) when focusing on merging that.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]