Make it clear that all our callback setters *replace* the existing callback
Bug #1635138 reported by
Chris Halse Rogers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Triaged
|
Low
|
Chris Halse Rogers | ||
| mir (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Gerry finds it unclear. Let's try to make it more obvious that there's exactly one callback, and that you can unset it with NULL.
| Changed in mir: | |
| assignee: | nobody → Chris Halse Rogers (raof) |
| tags: | added: clientapi docs |
| Changed in mir: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Michał Sawicz (saviq) wrote | #1 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
Syncing task from Mir.