-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102629/#review6563
-----------------------------------------------------------


I would suggest adding such application specific code to your application, i.e. 
your canvas implementation. There you can do whatever you want when a double 
click happens, including not passing it to the active tool or adding additional 
code to handle double click events.

- Jan


On Sept. 16, 2011, 9:29 a.m., Yue Liu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/102629/
> -----------------------------------------------------------
> 
> (Updated Sept. 16, 2011, 9:29 a.m.)
> 
> 
> Review request for Calligra.
> 
> 
> Summary
> -------
> 
> Changed double click behavior of default tool. Previously double click on a 
> path shape will enter path edit mode, but more often user expect creating a 
> text box on the shape. Now double click will create a textbox on the shape in 
> all applications except karbon, which is more concentrated on graphic editing.
> 
> 
> Diffs
> -----
> 
>   libs/flake/KoTosContainer.h a2162f0 
>   plugins/defaultTools/defaulttool/DefaultTool.cpp ccfce0e 
> 
> Diff: http://git.reviewboard.kde.org/r/102629/diff
> 
> 
> Testing
> -------
> 
> Runs correctly on each app. But when moving textshape attached shapes there 
> are some flickers when updating the textshape.
> 
> 
> Thanks,
> 
> Yue
> 
>

_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

Reply via email to