Deactivating a constraint throws away its desired value #49

New issue

Open

opened 2025-02-11 08:02:30 +00:00 by Vectornaut · 0 comments

Vectornaut commented

2025-02-11 08:02:30 +00:00

Collaborator

For example, suppose you want to turn off five constraints and then try turning them on again, one at a time, in various orders. In the current interface, the only way to accomplish this is to record the constraints' desired values outside the app and re-enter them as you turn the constraints back on.

In the planned initial implementation of observables, the only way to deactivate a constraint is to remove its desired value. This throws away information, making it inconvenient to reactivate constraints. For example, suppose you want to turn off five constraints and then try turning them on again, one at a time, in various orders. In the current interface, the only way to accomplish this is to record the constraints' desired values outside the app and re-enter them as you turn the constraints back on.

Vectornaut referenced this issue

2025-02-11 08:15:49 +00:00

Generalize constraints to observables #48

~~Vectornaut referenced this issue 2025-02-11 08:19:21 +00:00~~

Generalize constraints to observables #48

glen added the

prospective

label 2025-02-11 20:58:29 +00:00

glen changed title from ~~[prospective] Deactivating a constraint throws away its desired value~~ to Deactivating a constraint throws away its desired value

2025-02-11 20:58:43 +00:00