diff options
| author |   Jens Bocklage <jens_bocklage@mentor.com> | 2017-01-20 18:57:31 +0100 |
|---|---|---|
| committer | Jens Bocklage <jens_bocklage@mentor.com> | 2017-01-20 18:57:31 +0100 |
| commit | 0123e58dfc171ab28a707028dfe927721ce96971 (patch) | |
| tree | cde36593d13977db52439ee25702ac7b74bdcc84 | |
| parent | fe6c166985d97dcac27ca1e70735399ed9927e5b (diff) | |
Fix list in documentation
Signed-off-by: Jens Bocklage <jens_bocklage@mentor.com>
| -rw-r--r-- | homescreen/docs/homescreen_api.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/homescreen/docs/homescreen_api.md b/homescreen/docs/homescreen_api.md index 17a3bad..8f7b8f4 100644 --- a/homescreen/docs/homescreen_api.md +++ b/homescreen/docs/homescreen_api.md @@ -90,6 +90,7 @@ A surface can be visible or invisible (please do not confuse “visible” and � Right now an application has to pull this information.
This is not optimal and will change in the future. There are two options:
+
- The homescreen API will provide a signal that is emitted every time the visible status of surfaces changes. This would be way more efficient, because it would save time and avoid a re-occurring API call. __UPDATE:__ There is a D-Bus signal implemented in this API
- For Qt, there is already a patch available that provides this information as a base class property. See https://codereview.qt-project.org/#/c/176211/ This would be optimal for Qt widget applications. But not useful for other languages, e.g. Java. __UPDATE:__ This patch got reverted in AGL!
|