Vectornaut
  • Joined on 2019-09-28
Vectornaut pushed to pointCoordRegulators at glen/dyna3 2025-10-09 05:14:28 +00:00
adc60ac5c1 Spruce up formatting and error messages
27edbfb010 Streamline axis naming
Compare 2 commits »
Vectornaut opened issue StudioInfinity/dyna3#125 2025-10-08 20:53:33 +00:00
Migrate to the 2024 edition of Rust
Vectornaut opened issue StudioInfinity/dyna3#124 2025-10-08 20:44:47 +00:00
Upgrade to Rust 1.90
Vectornaut suggested changes for StudioInfinity/dyna3#118 2025-10-07 23:45:10 +00:00
feat: Point coordinate regulators

Review complete, except for…

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-07 20:10:11 +00:00
feat: Point coordinate regulators

Here are updates on the prospective issues mentioned in the pull request description.

The new coordinate regulators create redundant display information with the raw representation…

Vectornaut commented on issue StudioInfinity/dyna3#122 2025-10-07 19:57:39 +00:00
Entity entries in Outline View

I've edited this a bit, saving the original in case you want to compare and revert any of the changes.

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-07 19:42:45 +00:00
feat: Point coordinate regulators

This is now covered by issue #120. Thanks for posting that!

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-07 19:40:43 +00:00
feat: Point coordinate regulators

The code and the resulting interface both look like what I expect, so I'd say this is resolved.

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-07 19:37:12 +00:00
feat: Point coordinate regulators

I agree that the comment in issue #90 is enough to remind us about this.

What sort of a redesign would you have in mind? How would you add this extra frozen coordinate? Would you want the…

Vectornaut commented on issue StudioInfinity/dyna3#90 2025-10-07 19:35:47 +00:00
Make element representations opaque to the assembly module

Instead, perhaps, the engine should be checking if all but one of the coordinates of an entity are frozen, and if so, freeze the third.

I'll expand on this a little, since we talked about it…

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-06 20:42:26 +00:00
feat: Point coordinate regulators

I'd prefer to just add a /* TO DO */ flag, because I think the best way to fix the issue would involve a broader discussion about the organization of the engine and assembly submodules, which is…

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-06 20:05:56 +00:00
feat: Point coordinate regulators

@glen wrote in StudioInfinity/dyna3#118 (comment):

OK, I think I've responded to everything so far, but of course a few of the items are far from…

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-03 21:22:38 +00:00
feat: Point coordinate regulators

The associated constant Axis::N_AXIS, which is defined by hand here, has the same value as the associated constant Axis::CARDINALITY, which is defined automatically when we derive the Sequence trait. I'd recommend removing N_AXIS and using CARDINALITY in its place. I'm confident that CARDINALITY is currently 3, because I get a compilation error if I replace it with a value different from 3 in the definition of Axis::NAME.

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-03 21:22:38 +00:00
feat: Point coordinate regulators

Design

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-03 21:22:38 +00:00
feat: Point coordinate regulators

In the outline items for previously implemented regulators, we use the regulator-label div to say which other element, if any, is subject to the regulator, and we use the regulator-type label to say what's being regulated. To bring the outline item for the point coordinate regulator in line with this convention, I'd rewrite it like this.

Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-03 21:22:38 +00:00
feat: Point coordinate regulators

I've been flagging desired edits like this with /* TO DO */ // This 3... rather than //FIXME: This 3.... I'd like to stick to that format, because I think keeping flags consistent makes it easier to search for flagged code. I just started a wiki page to document the code flags I've been using.

Vectornaut suggested changes for StudioInfinity/dyna3#118 2025-10-03 21:22:38 +00:00
feat: Point coordinate regulators
Vectornaut commented on pull request StudioInfinity/dyna3#118 2025-10-03 20:50:18 +00:00
feat: Point coordinate regulators

I've tested the point coordinate regulators on my machine, and they seem to work as expected!

I'm happy overall with the design of the new regulator. It seems to slot into the existing…

Vectornaut pushed to near-miss at Vectornaut/dyna3 2025-09-30 00:42:43 +00:00
de4c2ef482 Correct mixed-up angles
a309870968 Fix the order of the triangle list
5b331dbbee Calculate angle distortions
def40714a7 Add twice-augmented data
Compare 4 commits »
Vectornaut created branch near-miss_pinned in Vectornaut/dyna3 2025-09-22 23:56:30 +00:00