Handle window movement/resize/close on our side and not in Android
This leads to much better performance and user interaction. Resizing still has some flickering but that is a different area of problems.
This commit is contained in:
parent
bd6e17ef70
commit
65531a3b82
17 changed files with 230 additions and 41 deletions
|
|
@ -31,5 +31,24 @@ status_t BpActivityManager::setFocusedTask(int32_t id) {
|
|||
return remote()->transact(IActivityManager::SET_FOCUSED_TASK, data, &reply);
|
||||
}
|
||||
|
||||
status_t BpActivityManager::removeTask(int32_t id) {
|
||||
Parcel data, reply;
|
||||
data.writeInterfaceToken(IActivityManager::getInterfaceDescriptor());
|
||||
data.writeInt32(id);
|
||||
return remote()->transact(IActivityManager::REMOVE_TASK, data, &reply);
|
||||
}
|
||||
|
||||
status_t BpActivityManager::resizeTask(int32_t id, const anbox::graphics::Rect &rect, int resize_mode) {
|
||||
Parcel data, reply;
|
||||
data.writeInterfaceToken(IActivityManager::getInterfaceDescriptor());
|
||||
data.writeInt32(id);
|
||||
data.writeInt32(resize_mode);
|
||||
data.writeInt32(rect.left());
|
||||
data.writeInt32(rect.top());
|
||||
data.writeInt32(rect.right());
|
||||
data.writeInt32(rect.bottom());
|
||||
return remote()->transact(IActivityManager::RESIZE_TASK, data, &reply);
|
||||
}
|
||||
|
||||
IMPLEMENT_META_INTERFACE(ActivityManager, "android.app.IActivityManager");
|
||||
} // namespace android
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue