summaryrefslogtreecommitdiffstats
path: root/ui/aura/client/activation_client.cc
Commit message (Collapse)AuthorAgeFilesLines
* Removes two properties that are defined else where. With these we getsky@chromium.org2012-08-261-1/+0
| | | | | | | | | | | | | link warnings. BUG=144155 TEST=none R=oshima@chromium.org Review URL: https://chromiumcodereview.appspot.com/10871076 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153398 0039d316-1c4b-4281-b951-d872f2087c98
* Add ActivationChangeObserver, replacing kRootWindowActiveWindowKeyoshima@chromium.org2012-06-041-1/+0
| | | | | | | | | BUG=123160 TEST=no functional change. all test must pass. Review URL: https://chromiumcodereview.appspot.com/10500006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140340 0039d316-1c4b-4281-b951-d872f2087c98
* Prevent a transient with 'kHideOnDeactivate' set from causing its transient ↵ben@chromium.org2012-03-261-0/+10
| | | | | | | | | | parent to lose its active shadow. http://crbug.com/120210 TEST=see bug Review URL: https://chromiumcodereview.appspot.com/9853030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128979 0039d316-1c4b-4281-b951-d872f2087c98
* * property can now manage value's memoryoshima@chromium.org2012-03-061-13/+3
| | | | | | | | | | | | * reduced boilerplate code * map now contains human readable key string. BUG= TEST=none Review URL: http://codereview.chromium.org/9560009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125153 0039d316-1c4b-4281-b951-d872f2087c98
* Migrate client API setters/getters to take a RootWindow.ben@chromium.org2012-02-261-5/+5
| | | | | | | | | http://crbug.com/112131 TEST=none TBR=sky Review URL: https://chromiumcodereview.appspot.com/9455081 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123690 0039d316-1c4b-4281-b951-d872f2087c98
* aura::Window only supports void* and int values for custom properties, which ↵benrg@chromium.org2012-02-111-6/+21
| | | | | | | | | | | | must be cast to and from the correct type at each use point. This CL introduces typed properties and templated aura::Window::[GS]etProperty methods that enforce the use of the declared type. Only pointer types and integral types that fits in intptr_t are supported, and ownership behavior is the same as before. This CL also adds support for default property values other than NULL/0. BUG=none TEST=updated unit tests Review URL: http://codereview.chromium.org/8533025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121583 0039d316-1c4b-4281-b951-d872f2087c98
* Shell related switches -> aura shell switches.ben@chromium.org2011-12-201-1/+3
| | | | | | | | | | | | Aura client window properties->client namespace. Move WindowType to client. BUG=none TEST=existing automation TBR=sky Review URL: http://codereview.chromium.org/8968022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@115182 0039d316-1c4b-4281-b951-d872f2087c98
* Move ActivationClient/Delegate to client namespace.ben@chromium.org2011-12-151-4/+4
| | | | | | | | | BUG=none TEST=existing automation TBR=sky Review URL: http://codereview.chromium.org/8956004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114657 0039d316-1c4b-4281-b951-d872f2087c98
* Move the concept of Activation to the Shell.ben@chromium.org2011-12-131-0/+23
| | | | | | | | | | | | | | | | | The Active Window is now stored in a property on the RootWindow. Classes wishing to observe changes to this can implement WindowObserver and attach to the RootWindow to be notified of changes in this property. We provide an ActivationClient interface in Aura for customers to use to set/get the active window, and deactivate a window. This is because setting the active window involves more than just changing the property, there is some additional book-keeping that must be done. The ActivationClient is stored in a property on the RootWindow. We also provide an ActivationDelegate interface in Aura that window owners can use to be notified of changes in activation state, and to specify whether or not a window can be activated. The ActivationDelegate should be stored on the relevant window in a property. I moved a lot of Activation-related functionality out of Aura, including all of the unit tests, now on ActivationController, and the associated WindowDelegate implementations which have now become a single TestActivationDelegate implementation. BUG=none TEST=unit tests Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=114095 Review URL: http://codereview.chromium.org/8894018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114121 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 114095 - Move the concept of Activation to the Shell.ben@chromium.org2011-12-121-23/+0
| | | | | | | | | | | | | | | | | | | The Active Window is now stored in a property on the RootWindow. Classes wishing to observe changes to this can implement WindowObserver and attach to the RootWindow to be notified of changes in this property. We provide an ActivationClient interface in Aura for customers to use to set/get the active window, and deactivate a window. This is because setting the active window involves more than just changing the property, there is some additional book-keeping that must be done. The ActivationClient is stored in a property on the RootWindow. We also provide an ActivationDelegate interface in Aura that window owners can use to be notified of changes in activation state, and to specify whether or not a window can be activated. The ActivationDelegate should be stored on the relevant window in a property. I moved a lot of Activation-related functionality out of Aura, including all of the unit tests, now on ActivationController, and the associated WindowDelegate implementations which have now become a single TestActivationDelegate implementation. BUG=none TEST=unit tests Review URL: http://codereview.chromium.org/8894018 TBR=ben@chromium.org Review URL: http://codereview.chromium.org/8926004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114101 0039d316-1c4b-4281-b951-d872f2087c98
* Move the concept of Activation to the Shell.ben@chromium.org2011-12-121-0/+23
The Active Window is now stored in a property on the RootWindow. Classes wishing to observe changes to this can implement WindowObserver and attach to the RootWindow to be notified of changes in this property. We provide an ActivationClient interface in Aura for customers to use to set/get the active window, and deactivate a window. This is because setting the active window involves more than just changing the property, there is some additional book-keeping that must be done. The ActivationClient is stored in a property on the RootWindow. We also provide an ActivationDelegate interface in Aura that window owners can use to be notified of changes in activation state, and to specify whether or not a window can be activated. The ActivationDelegate should be stored on the relevant window in a property. I moved a lot of Activation-related functionality out of Aura, including all of the unit tests, now on ActivationController, and the associated WindowDelegate implementations which have now become a single TestActivationDelegate implementation. BUG=none TEST=unit tests Review URL: http://codereview.chromium.org/8894018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114095 0039d316-1c4b-4281-b951-d872f2087c98