https://medium.com/flutter-community/a-deep-dive-into-draggable-and-dragtarget-in-flutter-487919f6f1e4

This article is the sixth in a series of articles which take an in-depth look at Flutter’s built in widgets.

  1. ListView/ScrollPhysics
  2. TextFields
  3. FloatingActionButtons
  4. Hero Widget
  5. Transform Widget

In this article, we will look at Draggable and DragTarget.


Exploring Draggable and DragTargets

Draggable and DragTarget allows us drag a widget across screen. First we will look at the basics of Draggables and DragTargets then dive into details of customizing them.


Draggable

A “Draggable” makes a widget movable around the screen. Let’s use a chess knight as our example.

 

Using a DragTarget to drag a chess knight around

The code for this is relatively straightforward:

Draggable(
child: WhiteKnight(
size: 90.0,
),
feedback: WhiteKnight(
size: 90.0,
),
childWhenDragging: Container(),
),

There are three main parts to the Draggable widget:

  1. Child: The child parameter is the widget that will be displayed when the draggable is stationary
  2. Feedback: The feedback is the widget that will be displayed when the widget is being dragged.
  3. Child When Dragging: The childWhenDragging parameter takes the widget to display in the original place of child when the widget is being dragged.

In the example above,we have a white knight as the child.When the knight is being dragged, we show an empty Container in its place.


Let’s customize the widget

First, let’s change the feedback parameter.

In the example below, we change the feedback parameter to a white bishop. Now, when the widget is not being dragged, a white knight is shown however as you start dragging, our bishop is shown.

Draggable(
child: WhiteKnight(
size: 90.0,
),
feedback: WhiteBishop(
size: 90.0,
),
childWhenDragging: Container(),
),

Result of the above code:

 

Now let’s move on to the third parameter, childWhenDragging. This takes a widget to be displayed in the original position of child as the widget is being dragged.

We’ll display a white rook when the widget is being dragged:

Draggable(
child: WhiteKnight(
size: 90.0,
),
feedback: WhiteBishop(
size: 90.0,
),
childWhenDragging: WhiteRook(
size: 90.0,
),
),

This becomes:

 

Restricting motion for Draggables

Setting the axis parameter helps us restrict motion in one dimension only.

Axis.horizontal makes the feedback widget on,y move in the horizontal axis.

Draggable(
axis: Axis.horizontal,
child: WhiteKnight(
size: 90.0,
),
feedback: WhiteBishop(
size: 90.0,
),
childWhenDragging: Container(),
),
 

Similarly, we also have Axis.vertical for vertical movement.


Adding data to Draggable

Data can be attached to a Draggable. This is useful to us since we use Draggables and DragTargets.

Considering our example, if we were to have multiple chess pieces, each piece would need to have unique data associated with it. Pieces would need properties such as color (White, Black) and type (ie: Rook, Bishop, Knight).

Below shows an example of how data can be attached to a Draggable for use with DragTarget.

We will take a look at this more in-depth in the DragTarget section.

Draggable(
child: WhiteKnight(
size: 90.0,
),
feedback: WhiteKnight(
size: 90.0,
),
childWhenDragging: Container(),
data: [
"White",
"Knight"
],
),

Callbacks

The draggable widget supplies callbacks for actions on the widget.

These callbacks are:

onDragStarted : This is called when a drag is started on a widget.

onDragCompleted : When a draggable is dragged to a DragTarget and accepted, this callback is called. We will look atDragTarget is in the next section.

onDragCancelled : When a draggable does not reach a DragTarget or is rejected, this callback is fired.


DragTarget

While a Draggable allows a widget to be dragged, a DragTarget provides a destination for the draggable.

For example, in chess, a chess piece is a draggable whereas a square box on the chessboard is a drag target.

 

Here, the knight is accepted by the DragTarget.

The code for this example goes:

bool accepted = false;
DragTarget(builder: (context, List<String> candidateData, rejectedData) {
return accepted ? WhiteKnight(size: 90.0,) : Container();
}, onWillAccept: (data) {
return true;
}, onAccept: (data) {
accepted = true;
},),

NB: The DragTarget is surrounded by a black colored container which is not shown in the code for brevity.

Let’s look at the parameters of the DragTarget in more detail.

Note: The “data” in the following sections refers to the data parameter of the Draggable.

Builder

The builder builds the actual widget inside the DragTarget. This function is called every time a Draggable is hovered over the DragTarget or is dropped onto it.

This function has three parameters, context, candidateData and rejectedData.

candidateData is the data of a Draggable whilst it is hovering over the DragTarget, ready for acceptance by DragTarget.

rejectedData is the data of a Draggable hovering over a DragTarget at moment it is not accepted.

Note that both of these are dealing with Draggables which are hovering over the DragTarget. At this point, they are not dropped onto it yet.

Now, how does the DragTarget know what to accept?

onWillAccept

onWillAccept is a function which gives us the Draggable data for us to decide whether to accept or reject it.

This is where the data we attached onto the Draggable becomes important. We use the data passed to accept or reject specific Draggables.

For example if our Draggable is:

Draggable(
data: "Knight",
// ...
),

then we can do:

DragTarget(
// ...
onWillAccept: (data) {
if(data == "Knight") {
return true;
} else {
return false;
}
},
),

This will only accept the Draggable if the data is “Knight”.

This function is called when the Draggable is first hovered over the DragTarget.

onAccept

If the Draggable is dropped onto the DragTarget and onWillAccept returns true, then onAccept is called.

onAccept also gives us the data of the Draggable and is usually used for storing the Draggable dropped over DragTarget.

onLeave

This was not implemented in the example. onLeave is called when a Draggable is hovered over the DragTarget and leaves without being dropped.


A Demo

Let’s create a simple demo app where the user is given a number and they are required to sort it as either “even” or “odd’. Depending on the choice, we will then display a message stating whether the choice is correct or wrong.

 

Source code:

 

A few more things

Draggable customisations

Draggable gives us a few more customizations.

One such customization is maxSimultaneousDrags. Multi-touch devicesare able to drag the same Draggable with two or more pointers and hence we can have multiple feedback on screen. For instance if the user is using a second finger to drag a child while one drag is already progress, we receive two feedback widgets at the same time.

maxSimultaneousDrags lets us decide the maximum number of times a draggable can be dragged at one time.

The feedbackOffset property also lets us set the offset of the feedback widget that displays on the screen.

Common error: DragTarget not accepting data

In the builder function, consider giving a type to the parameter candidateData. It returns a List by default, so if the data you’re passing is a string, the type would be List<String>.

builder: (context, List<String> candidateData, rejectedData) {
// ...
}

This solves a few type errors that occasionally comes up when passing data.

A more complete real-world example using Draggable and DragTarget

Sometime ago, I wrote a complete chessboard package using Draggables and DragTargets.

 

For the complete source code, you can check it out here.

Note: There is an update coming up to the package which includes a better architecture for the package, more boards, etc.

I used the chess_vectors_flutter package for the examples on this article.

A Deep Dive Into Draggable and DragTarget in Flutter的更多相关文章

  1. Deep Dive into Spark SQL’s Catalyst Optimizer(中英双语)

    文章标题 Deep Dive into Spark SQL’s Catalyst Optimizer 作者介绍 Michael Armbrust, Yin Huai, Cheng Liang, Rey ...

  2. X64 Deep Dive

    zhuan http://www.codemachine.com/article_x64deepdive.html X64 Deep Dive This tutorial discusses some ...

  3. 《Docker Deep Dive》Note - Docker 引擎

    <Docker Deep Dive>Note Docker 引擎 1. 概览 graph TB A(Docker client) --- B(daemon) subgraph Docker ...

  4. 《Docker Deep Dive》Note - 纵观 Docker

    <Docker Deep Dive>Note 由于GFW的隔离,国内拉取镜像会报TLS handshake timeout的错误:需要配置 registry-mirrors 为国内源解决这 ...

  5. Deep Dive into Neo4j 3.5 Full Text Search

    In this blog we will go over the Full Text Search capabilities available in the latest major release ...

  6. 重磅解读:K8s Cluster Autoscaler模块及对应华为云插件Deep Dive

    摘要:本文将解密K8s Cluster Autoscaler模块的架构和代码的Deep Dive,及K8s Cluster Autoscaler 华为云插件. 背景信息 基于业务团队(Cloud BU ...

  7. vue3 deep dive

    vue3 deep dive vue core vnode vue core render / mount / patch refs https://www.vuemastery.com/course ...

  8. Flutter: Draggable和DragTarget 可拖动小部件

    API class _MyHomeState extends State<MyHome> { List<Map<String, String>> _data1 = ...

  9. SQL optimizer -Query Optimizer Deep Dive

    refer: http://sqlblog.com/blogs/paul_white/archive/2012/04/28/query-optimizer-deep-dive-part-1.aspx  ...

随机推荐

  1. Django实现自动发布(1数据模型)

    公司成立之初,业务量较小,一个程序包揽了所有的业务逻辑,此时服务器数量少,上线简单,基本开发-测试-上线都是由开发人员完成. 随着业务量逐渐上升,功能增多,代码量增大,而单一功能上线需要重新编译整个程 ...

  2. UDP丢包原因总结

    丢包检查方法 给每个UDP包编号,对比收发端的接收到的包.对于UDP协议层上的包,例如RTP包,可以从RTP包中读出包的序列号进行判断. 抓包.发送端和接收端分别抓包.linux下可以使用tcpdum ...

  3. Asp.Net Core Cookie使用,Asp.net Core Cookie操作失效

    注:本文主要介绍Asp.net Core 3.0后增加cookie代理功能. 默认是增加了的. 默认增加的这个有些问题所在, 1.原来设置cookie方式将不可用,需要按照代理方式设置 2.对于ses ...

  4. LZW

    LZW https://www2.cs.duke.edu/csed/curious/compression/lzw.html https://www.golangprograms.com/golang ...

  5. Web打印的解决方案之证件套打

    由于以前未接触过套打,一直觉得套打是一个比较神秘和麻烦的事情,因为打印机的位置总是需要调整的,你总不能硬编码吧?但是如果位置可调,有需要直观一些来处理,那就比较麻烦了. 在前面介绍过<Web打印 ...

  6. chmod: changing permissions of ‘/etc/fstab': Read-only file system

    给passwd文件加权限,修改/etc/fstab目录下所有的文件夹属性为可写可读可执行,执行以下命令:chomd 777 /etc/fstab 的时候提示错误: chmod: changing pe ...

  7. 如何将业务代码写得像诗一样(使用注解+单例+工厂去掉一大波if和else判断)

    1.订单控制器,提供一个根据商品id和银行渠道id计算商品折后价格的接口: import org.springframework.web.bind.annotation.GetMapping; imp ...

  8. 【Base】死锁产生的四个必要条件

    死锁产生的四个必要条件 互斥条件:资源是独占的且排他使用,进程互斥使用资源,即任意时刻一个资源只能给一个进程使用,其他进程若申请一个资源,而该资源被另一进程占有时,则申请者等待直到资源被占有者释放. ...

  9. SDN实验---Ryu的源码分析

    一:安装Pycharm https://www.cnblogs.com/huozf/p/9304396.html(有可取之处) https://www.jetbrains.com/idea/buy/# ...

  10. Zynq 7020笔记之 GPIO MIO 和EMIO的学习

    1 参考 Xilinx ZYNQ 7000+Vivado2015.2系列(四)之GPIO的三种方式:MIO.EMIO.AXI_GPIO 2 理论指示 在PS侧,有PS自己的IO pin,称为MIO,共 ...