Vectornaut
  • Joined on 2019-09-28
Vectornaut commented on issue StudioInfinity/dyna3#51 2025-02-17 23:21:58 +00:00
Prototype 3D rendering view

Addressed by pull request #14. Benchmark measurements are recorded on the "Display benchmarking" wiki page.

Vectornaut closed issue StudioInfinity/dyna3#51 2025-02-17 23:21:58 +00:00
Prototype 3D rendering view
Vectornaut opened issue StudioInfinity/dyna3#54 2025-02-17 23:16:43 +00:00
Integrate engine into application prototype
Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-16 02:32:00 +00:00
Generalize constraints to observables

As for validation, I think it becomes clearer in this model. We can discuss further Monday, but I would propose that each regulator knows how to validate a possible set point, and a text-entry…

Vectornaut opened issue StudioInfinity/dyna3#53 2025-02-14 20:10:18 +00:00
Prototype entity list view
Vectornaut opened issue StudioInfinity/dyna3#52 2025-02-14 19:04:15 +00:00
Prototype constraint problem data structure
Vectornaut opened issue StudioInfinity/dyna3#51 2025-02-14 18:58:03 +00:00
Prototype 3D rendering view
Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-14 18:29:43 +00:00
Generalize constraints to observables

Ergo, when you are typing in one control for the set point, the other displays of the set point (textual or graphical) should not change, as they are merely displaying the current set point;…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-14 08:06:52 +00:00
Generalize constraints to observables

Whoops—I've rediscovered why the role field, or something equivalent, is needed to make regulator views act the way they currently do. This logic for determining…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-13 21:14:06 +00:00
Generalize constraints to observables

In my experience, having fewer places where the same information is kept or might be perceived to be kept actually makes the code easier to understand, as well as more concise (which also helps…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-13 20:49:20 +00:00
Generalize constraints to observables

And more importantly, it now seems to me that set_point_text is very likely a violation of the Model-View-Controller separation of concerns.

This field goes back to pull request #15, where it…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-13 10:00:49 +00:00
Generalize constraints to observables

I am still confused as to why Regulators have a role.

Another approach I considered was changing the type of set_point to Signal<Option<f64>> and using the following logic to determine…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-12 20:01:33 +00:00
Generalize constraints to observables

The pull request should be ready for review again now! I've made the following changes:

  • Renamed observables to regulators
  • Labeled the regulators in the outline view
Vectornaut pushed to observables_on_main at Vectornaut/dyna3 2025-02-12 19:56:08 +00:00
b3e4e902f3 Rename Regulator fields
24139ad5e9 Rename observables to regulators
de7122d871 Label observable type
Compare 3 commits »
Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-12 00:03:48 +00:00
Generalize constraints to observables

[…] it occurs to me that once we switch to a split view of Entities in one pane and Dials in the other, then the constraints will have to be labeled something like inversive distance(Deimos,…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-12 00:01:14 +00:00
Generalize constraints to observables

On the topic of what to name the class, I am OK with any of Dial, Thermostat, or Regulator, although I will say the last one speaks to me the least, perhaps because I have never used anything…

Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-11 08:19:21 +00:00
Generalize constraints to observables

I've added issues for both of the pitfalls we've identified and linked them from the pull request description.

I propose using the tag "prospective" for issues that would be introduced by pull…

Vectornaut opened issue StudioInfinity/dyna3#50 2025-02-11 08:10:48 +00:00
[prospective] You can't see the measured value of an unsatisfied constraint
Vectornaut opened issue StudioInfinity/dyna3#49 2025-02-11 08:02:30 +00:00
[prospective] Deactivating a constraint throws away its desired value
Vectornaut commented on pull request StudioInfinity/dyna3#48 2025-02-11 07:34:08 +00:00
Generalize constraints to observables

The term inversive distance sounds perfect for our use case. Nice find! With the current Lorentz product, -Q(I, J) is the inversive distance between the spheres represented by I and J. The…