SOLVED IN 1.4: Class lock prevents class from being added to elements

Bricks Version: 1.4b

If a class is locked, it’s not able to be added to an existing element. Class lock is supposed to prevent rules of the class from being edited (i.e. make them read-only) but still allow classes to be used in normal ways (i.e added to elements, removed from elements, deleted completely, and inspected).

The current implementation makes the feature fairly useless…in order to add a class (that is locked to prevent changing its rules) to an existing element, one has to:

  1. Unlock the class
  2. Add it to the element
  3. Lock it again.

And then if you want to see what rules are applied to the class you have to

  1. Unlock it
  2. Select it
  3. Inspect the rules
  4. Lock it again.

Looks the implementation of this feature was really rushed…hopefully it can be revisited before finalizing v.1.4.

Hi Eric,
Thanks so much for the report! We seem to have taken the Access thing a bit too seriously :sweat_smile: Of course, it should be possible for someone with full access to assign the classes and view them. We take care of it.

Best regards,
timmse

1 Like

Thanks…do keep the “can’t change rules of a locked class” behaviour…that is golden!