[sw-issues] [Issue 13645] moving rows and columns in a table (don't overwrite but move target cells)

[ds13]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=13645





--- Additional comments from [EMAIL PROTECTED] Tue May  3 11:41:29 -0700 
2005 ---
I agree, especially to peterthevicar (10/2/2004): It works yet in older versions
of MS Word, and the most intuitive and comfortable way I've seen so far is in
Lotus WordPro, where you can drag'n drop rows and columns to insert them
*between* others.
I would like to see this in Calc, too. (Cloph 12/26/2004, issue 21280, 14007)

Deleting the old columns/rows is neither expected by novice users (intuition...)
would expect nor very fluid in working, since you have more steps to do.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[sw-issues] [Issue 13645] moving rows and columns in a table (don't overwrite but move target cells)

[alvarezp2000]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=13645





--- Additional comments from [EMAIL PROTECTED] Fri Apr 22 18:34:55 -0700 
2005 ---
Is there any updates on this issue? It's still present in 680m91. I agree with 
the enhancement because a drag and drop is a move, like a cut and paste. Doing 
cut and paste with the rows works correctly.

I can reproduce the apparently-same bug it in another context:

1. I create a table, say, 3 columns, 6 rows.
2. Put data in row 3, 4 and 5. (1, 2 and 6 remain empty).
3. Select rows 3, 4 and 5.
4. Drag them to row 1.

Writer moves 3 and 4 to row 1. Row 5 is deleted. Although in the original bug 
report this can clearly be interpreted as "replacement", this is not exactly 
the 
case: looks like Writer first copies the info and THEN it removes the "extra" 
(why?) row. Can the entire algorithm be simply wrong.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]