WindowManagerClient::AddAccelerator() should take an array

ash/mus/accelerators/accelerator_controller_registrar.cc

Index: ash/mus/accelerators/accelerator_controller_registrar.cc
diff --git a/ash/mus/accelerators/accelerator_controller_registrar.cc b/ash/mus/accelerators/accelerator_controller_registrar.cc
index 79d7ea794ccaf9247c1c76c5187e4a1abfe8b742..7c80269cfd08c33d9d99363e3e4f378a4a01277c 100644
--- a/ash/mus/accelerators/accelerator_controller_registrar.cc
+++ b/ash/mus/accelerators/accelerator_controller_registrar.cc
@@ -13,7 +13,7 @@
 #include "ash/mus/bridge/wm_window_mus.h"
 #include "ash/mus/window_manager.h"
 #include "base/logging.h"
-#include "services/ui/common/event_matcher_util.h"
+#include "services/ui/common/accelerator_util.h"
 #include "services/ui/public/cpp/window_manager_delegate.h"
 #include "services/ui/public/cpp/window_tree_client.h"
 #include "ui/base/accelerators/accelerator_history.h"
@@ -126,12 +126,16 @@ void AcceleratorControllerRegistrar::OnAcceleratorRegistered(
   post_event_matcher->accelerator_phase =
       ui::mojom::AcceleratorPhase::POST_TARGET;
 
-  window_manager_->window_manager_client()->AddAccelerator(
-      ComputeAcceleratorId(id_namespace_, ids.pre_id), std::move(event_matcher),
+  window_manager_->window_manager_client()->AddAccelerators(

[sky, 2016/12/01 22:17:04]

Is this only the first change you're intending to do? As the way you have it now
you only call add with a single vector, so that in effect this change makes the
call have more overhead.

[thanhph, 2016/12/01 23:32:41]

To change this I need to change the callback function OnAcceleratorAdded to
handle multiple accelerators. I can create another bug which is to reduce
overhead of registering accelerators. This seems relate to this one I'm working
on next https://bugs.chromium.org/p/chromium/issues/detail?id=632050.

[sky, 2016/12/02 00:11:16]

I don't think that would help as registration adds accelerators one at a time.
Instead I think you need a function to be called on
AcceleratorControllerRegistrar after AcceleratorController::Init has been
called. Something like OnAcceleratorsRegistered(). This function would then
iterate over the internal structure and make the request to register the
accelerators as a single array.

You should do this separately. I just wanted to make sure you were going to make
use of the function that takes an array.

[thanhph, 2016/12/02 15:11:18]

Thanks Scott, I'll keep this in mind. Should I put this comment thread also in
this bug https://bugs.chromium.org/p/chromium/issues/detail?id=632050 ? 

For what I understand, bug 63250 is to resolve what you mention here.
Alternatively, we can merge these 2 bugs into bug 63249 and I can proceed with
the refactor. Thanks!
 

+      ui::CreateAcceleratorVector(
+          ComputeAcceleratorId(id_namespace_, ids.pre_id),
+          std::move(event_matcher)),
       base::Bind(OnAcceleratorAdded, accelerator));
-  window_manager_->window_manager_client()->AddAccelerator(
-      ComputeAcceleratorId(id_namespace_, ids.post_id),
-      std::move(post_event_matcher),
+
+  window_manager_->window_manager_client()->AddAccelerators(
+      ui::CreateAcceleratorVector(
+          ComputeAcceleratorId(id_namespace_, ids.post_id),
+          std::move(post_event_matcher)),
       base::Bind(OnAcceleratorAdded, accelerator));
 }