After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 702292 - Paste and Paste Special write on locked worksheet
Paste and Paste Special write on locked worksheet
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Main System
1.12.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-06-14 21:33 UTC by dgt224
Modified: 2013-10-06 19:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Proposed patch (422 bytes, patch)
2013-06-15 16:27 UTC, dgt224 		needs-work Details | Review

Description dgt224 2013-06-14 21:33:42 UTC 
If the Manage Sheets dialog is used to lock a worksheet, most functions refuse to modify the worksheet's contents. However, Edit -> Paste and Edit -> Paste Special perform the requested operation, replacing the "protected" contents. Similarly, clicking on the border of a selected range of cells in a locked worksheet and dragging the selection moves the selected cells to a new location, possibly replacing "protected" contents.

This behavior does not appear to have changed between 1.10.x and 1.12.x.
Comment 1 dgt224 2013-06-15 16:27:16 UTC 
Created attachment 246900 [details] [review]
Proposed patch

The attached patch appears to fix the problem completely, but I am not sufficiently familiar with the Gnumeric code base to be confident that this is the best way to make the fix.
Comment 2 Andreas J. Guelzow 2013-10-06 19:51:18 UTC 
Review of attachment 246900 [details] [review]:

This patch causes warnings on compile (related to pointer types)
Comment 3 Andreas J. Guelzow 2013-10-06 19:51:32 UTC 
Review of attachment 246900 [details] [review]:

This patch causes warnings on compile (related to pointer types)
Comment 4 Andreas J. Guelzow 2013-10-06 19:54:09 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.