Home | History | Annotate | Download | only in wm

Lines Matching refs:BOUNDS

30 import static com.android.server.wm.TaskProto.BOUNDS;
65 // Bounds used to calculate the insets.
71 // For comparison with DisplayContent bounds.
75 // For retrieving dim bounds
230 // Update task bounds if needed.
265 public int setBounds(Rect bounds, boolean forceResize) {
266 final int boundsChanged = setBounds(bounds);
276 /** Set the task bounds. Passing in null sets the bounds to fullscreen. */
278 public int setBounds(Rect bounds) {
283 } else if (bounds == null) {
284 // Can't set to fullscreen if we don't have a display to get bounds from...
288 if (equivalentOverrideBounds(bounds)) {
292 final int boundsChange = super.setBounds(bounds);
300 * Sets the bounds used to calculate the insets. See
312 * Gets the bounds used to calculate the insets. See
344 * Prepares the task bounds to be frozen with the current size. See
353 * Align the task to the adjusted bounds.
355 * @param adjustedBounds Adjusted bounds to which the task should be aligned.
356 * @param tempInsetBounds Insets bounds for the task.
358 * bounds's bottom; false if the task's top should be aligned
359 * the adjusted bounds's top.
389 // No need to adjust the output bounds if fullscreen or the docked stack is visible
395 // The bounds has been adjusted to accommodate for a docked stack, but the docked stack is
409 * @param out Rect containing the max visible bounds.
445 /** Bounds of the task to be used for dimming, as well as touch related tests. */
458 // When minimizing the docked stack when going home, we don't adjust the task bounds
459 // so we need to intersect the task bounds with the stack bounds here.
461 // If we are Docked Resizing with snap points, the task bounds could be smaller than the stack
462 // bounds and so we don't even want to use them. Even if the app should not be resized the Dim
477 // The bounds has been adjusted to accommodate for a docked stack, but the docked stack is
521 // task bounds so it stays in the same place.
522 // - Rotate the bounds and notify activity manager if the task can be resized independently
566 // stack bounds, currently we only animate the task for the recents animation
611 // The bounds has been adjusted to accommodate for a docked stack, but the docked stack
694 // Bounds need to be relative, as the dim layer is a child.
712 getBounds().writeToProto(proto, BOUNDS);