bu5hm4n pushed a commit to branch master.

http://git.enlightenment.org/core/efl.git/commit/?id=3b8648257b7278dc037c101a3da732439fac63e8

commit 3b8648257b7278dc037c101a3da732439fac63e8
Author: Xavi Artigas <xavierarti...@yahoo.es>
Date:   Tue Dec 3 12:51:52 2019 +0000

    Efl.Ui.Spotlight_Container: update docs after push/pop changes
    
    Differential Revision: https://phab.enlightenment.org/D10784
---
 src/lib/elementary/efl_ui_spotlight_container.eo | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/lib/elementary/efl_ui_spotlight_container.eo 
b/src/lib/elementary/efl_ui_spotlight_container.eo
index 766063c8f3..860d1beb71 100644
--- a/src/lib/elementary/efl_ui_spotlight_container.eo
+++ b/src/lib/elementary/efl_ui_spotlight_container.eo
@@ -72,9 +72,11 @@ class @beta Efl.Ui.Spotlight.Container extends Efl.Ui.Widget 
implements Efl.Pack
          }
       }
       push @beta {
-         [[Packs a new sub-widget before @.active_element, and move the 
spotlight there.
+         [[Packs a new sub-widget after @.active_element, and move the 
spotlight there.
 
            This is the same behavior as a push operation on a stack.
+           When sub-widgets are added using only @.push and @.pop you don't 
have to worry about @.active_element
+           since only the last sub-widget is manipulated, and this container 
behaves like a traditional stack.
 
            An animation might be triggered to give the new sub-widget the 
spotlight and come into position.
          ]]
@@ -85,10 +87,10 @@ class @beta Efl.Ui.Spotlight.Container extends 
Efl.Ui.Widget implements Efl.Pack
       pop @beta {
          [[Removes the sub-widget that has the spotlight from the widget.
 
-           The sub-widgets behind it naturally flow down so the next one gets 
the spotlight.
+           The spotlight is moved to the previous sub-widget.
            This is the same behavior as a pop operation on a stack.
-           When combined with @.push you don't have to worry about 
@.active_element since only the first sub-widget is
-           manipulated.
+           When sub-widgets are added using only @.push and @.pop you don't 
have to worry about @.active_element
+           since only the last sub-widget is manipulated, and this container 
behaves like a traditional stack.
 
            An animation might be triggered to give the new sub-widget the 
spotlight, come into position and the old
            one disappear.

-- 


Reply via email to