On Thu, 2015-10-08 at 10:34 -0500, lib...@acm.org wrote:
> I'm certainly open the idea of contributing this feature
> to Evolution proper, though. How would we explore this option
> further?
Hi,
simply file an enhancement request against evolution's Composer
component at
On Tue, 2015-10-06 at 23:01 -0500, Ben Liblit wrote:
> I've tested fetching the send activity from the action bar as
> outlined in my earlier message. It works well, feels clean, and
> requires no changes to Evolution itself. I'm going to proceed using
> this approach.
Hi,
you are
Milan Crha wrote:
> I'm not aware of any such race condition off head. As the composer
> andthe related parts are widgets, they operate these changes in the
> main (UI) thread, which gives a thread safety.
Ah, good point.
> I also think it is fine, and the direct get of the activity as you
>
On Mon, 2015-10-05 at 20:10 -0500, Ben Liblit wrote:
> Is there any possible race condition under which the activity might
> complete/cancel and go away before I have an opportunity to grab it
> like this? Or is there a race condition under which some *other*
> activity might be set as the
On Sat, 2015-10-03 at 17:21 -0500, Ben Liblit wrote:
> (A good start might be for e_msg_composer_send()
> to return the EActivity it creates: this exactly represents the
> current send attempt and could be monitored for status changes.)
Hi,
you are right, there is no good (and direct) API
Milan Crha wrote:
> you are right, there is no good (and direct) API to achieve what you
> want right now. There is an indirect API.
Thanks for your ideas, Milan. Using "notify::activity" to retrieve the
EActivity representing the send attempt is clever, but I agree that it
feels somewhat
I am working on an Evolution extension that adds a "Send and Archive"
menu item and toolbar button to Evolution mail composer windows. It
would be enabled only for replies or forwards. The intent is that
selecting this action first sends the newly-composed message, then
archives the forwarded or
