| Summary: | Ability to lock objects | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Nick Harvey <niharvey> |
| Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | al.views, buzea.bogdan, rb.henschel, robinson.libreoffice |
| Priority: | medium | ||
| Version: | Inherited From OOo | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=156549 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 113354 | ||
|
Description
Nick Harvey
2015-03-04 21:18:34 UTC
(In reply to Nick Harvey from comment #0) > It would be great to lock objects (images, Text, lines, etc) in Impress to > keep them from being accidently clicked on. Sounds like a plausible enhancement request. Severity -> enhancement Status -> NEW Nick: How would this feature be helpful beyond what master slides can provide? (Just looking for some additional information/inspiration for whoever might work on this functionality in the future) Thanks for the quick response! When I'm building a deck, I like to organize things in a way that they may "stack" on one another or overlap. It would minimize a significant amount of frustration from a user if I can "lock" an object in a slide without having to build a new master slide (especially if that content is only going to appear once). For instance, if I put an image and then draw an arrow overlapping onto it. It would be great if I could "lock" the picture so that when I'm trying to move my arrow around I don't accidentally click the picture and move it instead. The code still contains the layers for Impress as they exists for Draw. The UI was removed, because it too confusing in Impress. From a technical point of view it would be possible to add a "locked" as property to an object. "Lock" would put the object to a different, for user not directly accessible locked layer, and "unlock" would revert this. It might be possible by a macro. *** Bug 148300 has been marked as a duplicate of this bug. *** |