| Summary: | Account::haveConnection() and ::connectionStatus() are poorly documented | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Will Thompson <will> |
| Component: | tp-qt | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git master | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Will Thompson
2010-09-20 06:49:00 UTC
Before the "industrialization" (factories) work, the first call to connection() after haveConnection had cycled from false to true did expensive initialization constructing the actual proxy etc. Therefore it made sense to have a separate checker. You're right however that it doesn't really make sense anymore - and we have plans to drop it in the API/ABI break (and have just a connectionChanged instead). ++ for suggestion to improve the docs... Will do at ~some point~ in the future. 0.5.0 removes haveConnection() and haveConnectionChanged() completely. The documentation issues still stands, however... As there is not such methods for a very long time, we have no any reason to document them. |
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.