X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 29 Jul 2019 18:42:34 +0200 (CEST) From: Roland Lutz To: geda-user AT delorie DOT com Subject: [geda-user] Locking and unlocking Message-ID: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Reply-To: geda-user AT delorie DOT com Hi, I'm somewhat puzzled by the lock/unlock functionality. What is this intended for? Is it just some special-case logic to prevent accidentally moving the titleblock? What else do you use it for? There is a special lock color, but locking a component doesn't appear to change its color. It does change the color of attached attributes, but titleblocks don't usually have attributes attached. Is this intentional? Locking a component can have two different sets of effects: - When the titleblock for a new file is locked, or a locked component is read from a file, the component itself is made un-selectable; nothing else is changed. (In the latter case, the attached attributes may have been specified as "locked" color in the file, though.) - When a component and its attributes are locked in the GUI, both the component and its attributes are made un-selectable, and the attributes are changed to "locked" color. It seems to me that the default titleblock should be in the same state as a component locked in the GUI, and that writing a file to disk and reading it back again shouldn't change anything. Just, which of the observed behaviors is correct? Roland