development.git - development

	Commit message (Collapse)	Author	Age	Files	Lines
*	Follow API changes.	Dianne Hackborn	2011-01-17	1	-2/+2
\| \| \| \|	Change-Id: Ieb1df7fc0708f22aae3d851f74ade1343eb44e08
*	API CHANGE: startDrag() now takes "int flags" instead of "boolean localOnly"	Christopher Tate	2011-01-11	1	-7/+2
\| \| \| \| \| \| \| \| \|	startDrag() that crosses application boundaries will remain @hide until we get more of the surrounding behaviors nailed down. Drag-and-drop demo updated to only show app-local drag operations pro tem. Change-Id: I9cdcd132c1aae45bc472e70293b7187b4cba9bca
*	Rename drag "thumbnail" to the drag "shadow"	Christopher Tate	2011-01-07	1	-7/+7
\| \| \| \| \| \|	No functional changes; just a rename of the relevant class/method/parameters. Change-Id: I506f8b541027cf104553c27547d3e9972cd1add8
*	Add drag/drop demo to ApiDemos	Christopher Tate	2010-12-01	1	-0/+266
	Drag/drop among four big dots on screen. Drags to a dot will have the identity of the originating dot put into a text field below the dots. In all cases, a text field to the right of the dots reports whether the drag ended in a successful drop. Attempting to start a drag from a dot reading "Drag ANR" should ANR and be cleaned up properly. Attempting to drop onto a dot reading "Drop ANR" should similarly ANR and be cleaned up properly. Drags from a dot labelled "Local" are restricted to targets within the app's own window -- they are not draggable to the system "shirt pocket" drop target, etc. A drop onto the same dot that it originated from will append text to that effect to the message that notes the dropped payload. This uses the "local state" convenience mechanism in startDrag() and DragEvent.getLocalState(). Change-Id: Ic5cd6a29186a84c91d3dc4187e83e7bcf530ba2f