summaryrefslogtreecommitdiffstats
path: root/core/java/android/view
Commit message (Collapse)AuthorAgeFilesLines
* Implement support for scrolling a wallpaper.Dianne Hackborn2009-08-112-1/+6
| | | | | | This currently only works for a wallpaper that is larger than the screen. Set the scroll position with the new wallpaper API. Right now only does jump scrolls.
* Very primitive wallpapers in a surface.Dianne Hackborn2009-08-083-17/+44
| | | | | | | | | | | | | | This is all of the basic pieces: - The WallpaperService now creates a surface with the window manager for its contents. - There is a simple service that displays a bitmap. - The wallpaper manager takes care of starting and stopping the service. - The window manager knows about wallpaper windows and how to layer them with the windows that want to be shown on top of wallpaper. Lots and lots of issues remain, but at this point you can actually write a wallpaper service, select it in the UI, and see it behind an activity.
* Fix crash when MotionEvent is initialized with more than 2 fingers, and bumpDianne Hackborn2009-08-061-3/+19
| | | | its initial size to allow for up to 5 fingers.
* Fix documentation.Dianne Hackborn2009-08-051-2/+2
|
* Finish implementation of multiple pointer support for MotionEvent.Dianne Hackborn2009-08-042-156/+226
| | | | | | | | | | | | | | | | | | | | | | | | The major things going on here: - The MotionEvent API is now extended to included "pointer ID" information, for applications to keep track of individual fingers as they move up and down. PointerLocation has been updated to take advantage of this. - The input system now has logic to generate MotionEvents with the new ID information, synthesizing an identifier as new points are down and trying to keep pointer ids consistent across events by looking at the distance between the last and next set of pointers. - We now support the new multitouch driver protocol, and will use that instead of the old one if it is available. We do NOT use any finger id information coming from the driver, but always synthesize pointer ids in user space. (This is simply because we don't yet have a driver reporting this information from which to base an implementation on.) - Increase maximum number of fingers to 10. This code has only been used with a driver that reports up to 2, so no idea how more will actually work. - Oh and the input system can now detect and report physical DPAD devices.
* Update the comment for setBackgroundResource that 0 removes the background.Wink Saville2009-08-041-1/+1
|
* Merge change 9267Android (Google) Code Review2009-07-301-0/+2
|\ | | | | | | | | * changes: Don't invalidate view if setEnabled doesn't change the state.
| * Don't invalidate view if setEnabled doesn't change the state.Amith Yamasani2009-07-301-0/+2
| | | | | | | | | | | | | | Check the current enabled state before setting it, in case there's no change. Otherwise some apps are repeatedly redrawing buttons based on validation of some text field (like gmail or mms message bodies). Should slightly improve the performance of soft keyboard text entry.
* | am 25dff70f: Merge change 9039 into donutAndroid (Google) Code Review2009-07-301-1/+4
|\ \ | |/ |/| | | | | | | | | Merge commit '25dff70f153529b87f5ad4a92f4de21e8950b1de' * commit '25dff70f153529b87f5ad4a92f4de21e8950b1de': Fix #2018814: System cannot correctly render assets with "wrap_content" attribute in QVGA
| * Fix #2018814: System cannot correctly render assets with "wrap_content" ↵Dianne Hackborn2009-07-291-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | attribute in QVGA It turns out we were not returning the density for anything retrieved from a TypedArray... which basically means any bitmap references from a layout or style...!!! This is now fixed. Also fiddle with the density compatibility mode to turn on smoothing in certain situations, helping the look of things when they need to scale and we couldn't do the scaling at load time.
* | Merge change 8974Android (Google) Code Review2009-07-291-2/+2
|\ \ | | | | | | | | | | | | * changes: Fix OOB in arraycopy.
| * | Fix OOB in arraycopy.Owen Lin2009-07-291-2/+2
| | |
* | | am 159e1a9a: Merge change 8883 into donutAndroid (Google) Code Review2009-07-291-1/+7
|\ \ \ | |/ / |/| / | |/ | | | | | | Merge commit '159e1a9a13ccfa4d99941e21068994366e2bbc7b' * commit '159e1a9a13ccfa4d99941e21068994366e2bbc7b': fix [1973755] Surface.SURACE_FROZEN spelled SURACE_FROZEN
| * Merge change 8883 into donutAndroid (Google) Code Review2009-07-281-1/+7
| |\ | | | | | | | | | | | | * changes: fix [1973755] Surface.SURACE_FROZEN spelled SURACE_FROZEN
| | * fix [1973755] Surface.SURACE_FROZEN spelled SURACE_FROZENMathias Agopian2009-07-281-1/+7
| | |
* | | am a62f16ac: Merge change 8877 into donutAndroid (Google) Code Review2009-07-281-1/+4
|\ \ \ | |/ / | | | | | | | | | | | | | | | Merge commit 'a62f16accad31e03ede5e4e6525dbe30dccc6db0' * commit 'a62f16accad31e03ede5e4e6525dbe30dccc6db0': Remove warning in non-eng builds.
| * | Remove warning in non-eng builds.Romain Guy2009-07-281-1/+4
| |/
* | Support for selection of silent ringtone from the ringtone picker.Marco Nelissen2009-07-281-8/+23
| | | | | | | | This doesn't actually enable that, but adds the necessary code to make it work when enabled, and cleans up some ringtone related code.
* | Fix a bug that was causing ArrayIndexOutOfBoutExceptions when obtaining a ↵Adam Bliss2009-07-271-1/+1
| | | | | | | | MotionEvent from an older one that had a number of time samples.
* | Add support for power keys, improve behavior of virtual keys.Dianne Hackborn2009-07-245-4/+51
| | | | | | | | | | | | | | | | | | | | | | The platform now knows how to deal with a platform key, which at this point is "just like end call, but don't end a call." Also improve the handling of virtual keys, to allow for canceling when sliding off into the display and providing haptic feedback. Finally fixes a bug where the raw x and y in motion event were not always set which caused the status bar to not work.
* | am 11ea3347: Allow for screen density drawables in compatibility mode.Dianne Hackborn2009-07-243-3/+6
|\ \ | |/ | | | | | | | | | | Merge commit '11ea33471e1a14a8594f0b2cd012d86340dd3bd8' * commit '11ea33471e1a14a8594f0b2cd012d86340dd3bd8': Allow for screen density drawables in compatibility mode.
| * Allow for screen density drawables in compatibility mode.Dianne Hackborn2009-07-243-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change allows us to use drawables that match the current screen density even when being loaded in compatibility mode. In this case, the bitmap is loaded in the screen density, and the bitmap and nine-patch drawables take care of accounting for the density difference. This should be safe for existing applications, for the most part, since they shouldn't really be pulling the bitmap out of the drawable. For the small rare chance of them breaking, it worth getting the correct graphics. Also this will only happen when there is actually a resource of the matching density, and no existing apps should have resources for anything besides the default density (though of course all of the framework resources will be available in the native density). As part of this, the bitmap density API has been changed to a single integer provider the DPI unit density.
* | am 589cebe2: * Use the scaled size for surface view instead of native. The ↵Mitsuru Oshima2009-07-232-52/+10
|\ \ | |/ | | | | | | | | | | | | | | surface will be always scaled by surface flinger in compatiblity mode. The original approach confused the app because the surface size and the view size were different. * a few clean up. remo Merge commit '589cebe2d58591403de4a77077941c0454bc91bc' * commit '589cebe2d58591403de4a77077941c0454bc91bc': * Use the scaled size for surface view instead of native. The surface will be always scaled
| * * Use the scaled size for surface view instead of native. The surface will ↵Mitsuru Oshima2009-07-232-52/+10
| | | | | | | | | | | | | | | | | | be always scaled by surface flinger in compatiblity mode. The original approach confused the app because the surface size and the view size were different. * a few clean up. removed unsed arguments, obsolete conditions from getTranslator() (expandable check was a bug)
* | am e0ef973b: Merge change 8323 into donutAndroid (Google) Code Review2009-07-233-15/+68
|\ \ | |/ | | | | | | | | | | Merge commit 'e0ef973b1358585d039989ee5572e16751078aaf' * commit 'e0ef973b1358585d039989ee5572e16751078aaf': * a best effort fix for apps that uses get/set Matrix API on canvas.
| * * a best effort fix for apps that uses get/set Matrix API on canvas.Mitsuru Oshima2009-07-233-15/+68
| | | | | | | | | | | | | | | | - scale the matrix - but don't scale if the matrix *looks* like obtained from the canvas itself. (typically to set it back to original matrix) This is best effort change and not perfect (not even close), but works for one game, and hopes it can handle many other apps that uses set/get Matrix. If you have an alternative idea, please let me know.
* | am 98a44df4: Merge change 8235 into donutAndroid (Google) Code Review2009-07-221-16/+27
|\ \ | |/ | | | | | | | | | | Merge commit '98a44df4b4cc8cd28276ad888a7e17f81353ae44' * commit '98a44df4b4cc8cd28276ad888a7e17f81353ae44': * Revert the change that I introduced while refactroing in SurfaceView#dispatchTouchEvent
| * * Revert the change that I introduced while refactroing in ↵Mitsuru Oshima2009-07-221-16/+27
| | | | | | | | | | | | SurfaceView#dispatchTouchEvent * Don't scale back the event if the canvas is used in SurfaceView.
* | First stab at poly-finger support.Dianne Hackborn2009-07-211-175/+512
| | | | | | | | | | | | | | | | | | | | | | The MotionEvent API should be fairly solid, but there is still a lot of work to do in the input device code. In particular, right now we are really stupid about watching how fingers change -- we just take whatever the driver reports as down and dump that directly into the motion event. The big remaning work is to assign pointer IDs so that applications have help in determine which fingers go up and down, and adding support for the official multi-touch driver protocol.
* | am 38ed7d77: * Adjust canvas size under compatibility mode.Mitsuru Oshima2009-07-213-4/+36
|\ \ | |/ | | | | | | | | | | Merge commit '38ed7d7701514ee7127d0430e952930854608c4f' * commit '38ed7d7701514ee7127d0430e952930854608c4f': * Adjust canvas size under compatibility mode.
| * * Adjust canvas size under compatibility mode.Mitsuru Oshima2009-07-213-4/+36
| |
* | am fe6f45c8: Merge change 8098 into donutAndroid (Google) Code Review2009-07-213-11/+13
|\ \ | |/ | | | | | | | | | | Merge commit 'fe6f45c81463d2d28e11ac6083f2653e1286c5ef' * commit 'fe6f45c81463d2d28e11ac6083f2653e1286c5ef': cast is floor. Use round instead.
| * cast is floor. Use round instead.Mitsuru Oshima2009-07-213-11/+13
| | | | | | | | This fixes a few layout issues (that was due to smaller widnow size)
* | am 841f13c8: * Reverted the change in PackageParser that I checked by ↵Mitsuru Oshima2009-07-192-11/+7
|\ \ | |/ | | | | | | | | | | | | | | accident * More surface view fix. - correct event translation on surface view. - use compatible window * removed FLAG_NO_COMPATIBILITY_SCALE. It was my misunderstanding of how SurfaceView works, Merge commit '841f13c8e9ff3f7695b6c18a8abcec3c947983ff' * commit '841f13c8e9ff3f7695b6c18a8abcec3c947983ff': * Reverted the change in PackageParser that I checked by accident
| * * Reverted the change in PackageParser that I checked by accidentMitsuru Oshima2009-07-192-11/+7
| | | | | | | | | | | | | | | | * More surface view fix. - correct event translation on surface view. - use compatible window * removed FLAG_NO_COMPATIBILITY_SCALE. It was my misunderstanding of how SurfaceView works, and this was not necessary. * Added compatibility related info to package dumpsys
* | am e96bd129: Merge change 7707 into donutAndroid (Google) Code Review2009-07-171-2/+14
|\ \ | |/ | | | | | | | | | | Merge commit 'e96bd1291482175ac1740780cbd0f42bbe9ff746' * commit 'e96bd1291482175ac1740780cbd0f42bbe9ff746': * scale surface view's canvas
| * * scale surface view's canvasMitsuru Oshima2009-07-171-2/+14
| | | | | | | | This will not affect GL/Video views as they're directly using surfce but not canvas.
* | am 54f09101: Merge change 7613 into donutAndroid (Google) Code Review2009-07-172-2/+10
|\ \ | |/ | | | | | | | | | | Merge commit '54f09101381fa63dca35ae4ea0ba3802ee863236' * commit '54f09101381fa63dca35ae4ea0ba3802ee863236': * Use Fede In/Out animation if one of opening/closing apps is in compatibility mode.
| * * Use Fede In/Out animation if one of opening/closing apps is in ↵Mitsuru Oshima2009-07-172-2/+10
| | | | | | | | | | | | | | | | | | | | | | compatibility mode. * preserve compatibility window flag when the app updates window's layout params. * Added assertion in DEFAULT_COMPATIBILITY_INFO object to prevent unintentional modification. * A few minor updates * log/dump message improvement * Removed unnecessary method in FadeInOutAnimator * Fixed 100 char issue in WindwoManagerServer.java
* | Fixes merge conflict.Romain Guy2009-07-161-8/+0
| |
* | am b5c735d3: Merge change 7106 into donutAndroid (Google) Code Review2009-07-142-2/+33
|\ \ | |/ | | | | | | | | | | Merge commit 'b5c735d35c8c1d2fb4e4654fbffcdb62d5acab4d' * commit 'b5c735d35c8c1d2fb4e4654fbffcdb62d5acab4d': Return adjusted display for WindowManager.getDefaultDisplay()
| * Merge change 7106 into donutAndroid (Google) Code Review2009-07-142-2/+33
| |\ | | | | | | | | | | | | * changes: Return adjusted display for WindowManager.getDefaultDisplay()
| | * Return adjusted display for WindowManager.getDefaultDisplay()Mitsuru Oshima2009-07-142-2/+33
| | |
* | | am 30d86e51: Merge change 7124 into donutAndroid (Google) Code Review2009-07-141-0/+9
|\ \ \ | |/ / | | | | | | | | | | | | | | | Merge commit '30d86e5143d01815763f8c28b0fc72b0493ea9f8' * commit '30d86e5143d01815763f8c28b0fc72b0493ea9f8': Fixes #1977685. Prevent crash when the soft keyboard is brought up.
| * | Fixes #1977685. Prevent crash when the soft keyboard is brought up.Romain Guy2009-07-141-0/+9
| |/ | | | | | | | | | | | | | | | | ViewRoot keeps a reference to the previously focused View and use this reference when trying to scroll the window to the focused rect. There situations however in which the previously focused view might have been removed from the view hierarchy. This happens on Home for instance when you trash an icon, or with ListView's items. This change ensures the previously focused view is still part of the view hierarchy.
* | fix [1968839] tap on phonetop search couple of times will cause the runtime ↵Mathias Agopian2009-07-091-3/+5
| | | | | | | | | | | | restart ViewRoot wasn't calling Surface.clear() when releasing the Surface.
* | am 1ecf5d28: Re-implementation of large screen support using window manager. ↵Mitsuru Oshima2009-07-083-4/+16
|\ \ | |/ | | | | | | | | | | | | | | * added background filler surface to fill the outer rim. Using the same layer as dim surface because they never co-exists (in the same window) * clean up the obsolete code in Compatibilt Merge commit '1ecf5d28817f0a051e77488380dcd5bc622ea169' * commit '1ecf5d28817f0a051e77488380dcd5bc622ea169': Re-implementation of large screen support using window manager.
| * Re-implementation of large screen support using window manager.Mitsuru Oshima2009-07-083-4/+16
| | | | | | | | | | | | * added background filler surface to fill the outer rim. Using the same layer as dim surface because they never co-exists (in the same window) * clean up the obsolete code in CompatibiltyMode/ViewRoot for support large screen support.
* | am 790a604b: Merge change 6372 into donutAndroid (Google) Code Review2009-07-071-3/+6
|\ \ | |/ | | | | | | | | | | Merge commit '790a604b9c32647711599710e21f0f00eb3d839c' * commit '790a604b9c32647711599710e21f0f00eb3d839c': Fixes #1963217. Increases the invalidate region in compatibility mode.
| * Fixes #1963217. Increases the invalidate region in compatibility mode.Romain Guy2009-07-071-3/+6
| | | | | | | | | | To account for rounding errors when scaling the invalidate regions, increase the dirty rectangle by 1 pixel in each direction
generated by cgit v1.1 at 2024-09-11 00:09:29 +0000