<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - ENHANCEMENT: Add a lock to caption frame; so frame being image (as prevention for unintended changes within the frame)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135884#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - ENHANCEMENT: Add a lock to caption frame; so frame being image (as prevention for unintended changes within the frame)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135884">bug 135884</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=135884#c3">comment #3</a>) > (In reply to Telesto from <a href="show_bug.cgi?id=135884#c2">comment #2</a>) > > You do sound like a FAQ bot :-) > > Always in hope you search the bugtracker first :-). We have several about > frames either being selected unintentionally when users want to get the > object or not the other way around. A quick search revealed <a class="bz_bug_link bz_status_NEW " title="NEW - Cannot select (move, resize) floating frame" href="show_bug.cgi?id=78583">bug 78583</a> and > <a class="bz_bug_link bz_status_NEW " title="NEW - Floating Frames can't be easily selected by mouse" href="show_bug.cgi?id=86598">bug 86598</a> (you might find better suited, I remember Regina arguing on one > ticket). I think you know the answer to that(◔_◔). Will try to find the ticket with Regina her argument > In this particular topic I don't see how this would be guidelinizable. The > minimum screen size is defined as WXGA having old notebooks/displays in mind. Screen size drifting off topic. Core question. Must tablet/phone taken into account. Selecting a frame with touch screen is even harder (compared to mouse cursor), so locking mechanism would really welcome in that case.. But not knowing enough about if this needs to be taken into account here. > Back to topic: you want to solve the issue of unintentionally moved images > by locking it, this might be your way to go. I don't get the point of global > lock/unlock in this regards. Didn't read my initial report, directly jumped into your suggestion. The initial proposal was the 'grouping' concept. So making frame & content a group (similar to shapes). Which can be ungrouped. Not enough experience with grouping shapes and stuff to now if the caption would be accessible in this model (I assume so) So 'lock/unlock' is same as 'group/ungroup'. Advantage of grouping is of course that no fixed position being set.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>