Issue 24489 - Inconsistent behaviour in drag and drop in different data views
Summary: Inconsistent behaviour in drag and drop in different data views
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 24490 (view as issue list)
Depends on:
Reported: 2004-01-17 01:23 UTC by kelvine
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description kelvine 2004-01-17 01:23:42 UTC

It is hard to determine if this issue is a bug or enhancement. Given that it 
produced unexpected behaviour and over wrote my data causing me an issue, I am 
submitting it as a bug.

I then decided to do a quick review of the various data views in Why I reviewed the various views of data is because I opened 
the data source browser, went to drag a field value to the document and 
changed my mind and released the mouse button.

The mouse was over the primary key field of another record and thus pasted the 
contents to this field.

IMHO this behaviour is a concern (possibly dangerous) for more novice users. 
Control+z does not undo but pressing Escape does, so the problem is fairly 
easily fixed.

I decided to see what happened in all three ways you can view data in

There are three approaches to using/viewing data on
1. Data source browser
2. Form as a single record
3. Form using table control

The following is only about dragging and dropping data within the current view 
of the data. Not about dragging and dropping to another application. I will 
raise those issues separately.

- In a form (table control for multiple records) it is only possible to drag 
and drop within a field. This acts as a move.

- In a form (single record) it is possible to drag and drop within the control 
and to other controls within the same form. Dragging and dropping within the 
field acts as a move. Dragging and dropping the entire field or part of the 
field to another field, acts as a move and places the contents at the cursor 
position. So it acts as a move in both cases.

- In the data source view it is possible to drag and drop within a field which 
acts as a move. It is possible to drag and drop the entire field to another 
field within the current record and to another record which acts as a total 

Don't get me wrong, I think this feature is very good. My concern is there are 
three different approaches being used in the program.

As an experienced user I can adjust my behaviour and take advantage of the 
different behaviours.

I am simply offering feedback as I inadvertently overwrote my data and can see 
less experienced users doing the same.

IMHO drag and drop should operate the same in all three data views.

If I was to suggest a compromise it would be, drag and drop within the field 
and record but not to another record. When dragging within the field the move 
to be the default behaviour. When dragging outside of the field but within the 
same record the copy and paste to be the default behaviour.

The developers may consider the current behaviour valid (which it is) and thus 
this issue can immediately by closed. I am simply offering my feedback. 


Comment 1 hans_werner67 2004-02-02 12:33:20 UTC
change subcomponent to 'none'
Comment 2 marc.neumann 2004-02-12 11:07:04 UTC

I will set this to ENHANCEMENT and send it to 

Maybe we should think abount a better D&D handling in the future.

Bye Marc
Comment 3 marc.neumann 2004-02-12 11:12:55 UTC
*** Issue 24490 has been marked as a duplicate of this issue. ***
Comment 4 marc.neumann 2004-02-12 11:14:25 UTC
from issue 24490:


I noticed that when I drag and drop data from the data source window to a 
Writer document it acts as a copy and paste.

When I drag and drop data from a form (either a single record or table 
control) to a Writer document, it acts as a cut and paste which effectively 
destroys the data.

IMHO the data source window approach should be the standard approach.




this should be keep in mind when chnage the D&D handling in the future.

Bye Marc
Comment 5 bettina.haberer 2010-05-21 14:55:13 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".