| Summary: | Imposible to disable drag-n-drop of selected text | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Teodor <teod0r> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | cfeck, gladhorn, turkeyman |
| Priority: | NOR | Keywords: | accessibility, usability |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Teodor
2013-06-08 13:37:08 UTC
The description of this bug is incomplete. Please add more information, such as steps to reproduce (including the application you were using), actual behavior, and expected behavior. Additionally, since this bug has been marked as "critical", please add a description about how data can be lost. Just need an ability to COMPLETELY disable drag'n'drop in DE.
> Additionally, since this bug has been marked as "critical", please add a
> description about how data can be lost.
The content of text files could be accidently messed because of drag'n'drop (in some posible situations CTRL+Z will not help you). It is not comfortable for me when I can't reselect part of text, which is already selected. I'm not going to be "addicted" to clicking somewhere before I can reselect a part of text. Not for me
(In reply to comment #2) > Just need an ability to COMPLETELY disable drag'n'drop in DE. I mean drag'n'drop only for text of course I still need the information in which application you need this feature. (In reply to comment #4) > I still need the information in which application you need this feature. I need that feature in all applications. It would be great if there will be an option in MOUSE section of systemsettings Applications do not share code for drag handling of text. Since you talk about text editing, I reassigned this to Kate developers. Please report new wishes for other applications. This is a wont-fix, sorry. Drag & drop is a de facto standard, and we don't have the resources to implement (and maintain) such special behavior. Therefore, we decided to not implement this for now, sorry. @Frederik: If you think this is a needed usability / accessibility feature, please let us know. *** Bug 325139 has been marked as a duplicate of this bug. *** |