Proposed Change to Lock Behavior of Containers

[midikinetics]

Overview

Do you use the "Lock" feature on containers in Lemur?

Currently, locking a container prevents resizing and hides subcomponents in the project navigator. Modifying the behavior of this feature is under consideration so that locking only hides subcomponents but still allows resizing.

Justification

This adjustment aims to make the feature more user-friendly by reducing unnecessary restrictions while maintaining its utility for hiding internal components of containers. Preventing resizing is redundant because the Lemur Editor already allows containers to be dragged by their edges to move them without resizing. Additionally, locking does not prevent containers from being moved, which makes the current behavior unnecessarily restrictive—or not restrictive enough—for practical use cases.

Example

To understand the utility of this feature, download either MKPiano or MKConsole and inspect its content in the project navigator.

https://github.com/MIDIKinetics/MKConsole
https://github.com/MIDIKinetics/MKPiano

When the container is locked, try to resize it, and note that it cannot be resized. Unlock the container by going to the Object Inspector Panel and clicking the lock icon, and you will see that resizing is now allowed. However, unlocking also reveals the internal details of the container, which may not be desirable. This demonstrates how locking currently restricts resizing while protecting the container's internal details, and why modifying the behavior could simplify workflows.

Impact

Importantly, this change would not break any existing code. Feedback from the community is being sought before making this change. Please leave a comment if this change would break your project.