Bug 15300 - Add _call_when_ready() equivalent for every _run_until_ready()
Summary: Add _call_when_ready() equivalent for every _run_until_ready()
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: low enhancement
Assignee: Simon McVittie
QA Contact: Telepathy bugs list
URL: http://monkey.collabora.co.uk/tp-glib...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-01 06:48 UTC by Simon McVittie
Modified: 2008-05-02 08:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2008-04-01 06:48:32 UTC 
14:42 < ptlo> smcv: right; i stumbled upon a bug in empathy which calls send 
              assuming that the channel is ready when in fact it wasn't; i 
              "fixed" it using _run_until_ready(), is that proper way or is it 
              too hackish?
14:42 < ptlo> Zdra: ^^
14:45 < smcv> ptlo: that's what _run_until_ready() is for...
14:45 < ptlo> ok, thx
14:45 < smcv> ptlo: if Send() is called async, you might want to do some sort 
              of async chaining behaviour instead
14:45 < Zdra> isn't it better to connect to signal "notify::channel-ready" ?
14:46 < smcv> yeah, like that
14:46 < smcv> I should add a call_when_ready() really
Comment 1 Simon McVittie 2008-05-01 04:10:20 UTC 
tp_channel_call_when_ready() implemented in http://monkey.collabora.co.uk/tp-glib-smcv-15300/
Comment 2 Simon McVittie 2008-05-02 08:38:11 UTC 
Fixed in Darcs, will be in 0.7.7

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.