Skip to content

improvement of residual-chart hover info #579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 195 commits into
base: mainmast
Choose a base branch
from
Open

improvement of residual-chart hover info #579

wants to merge 195 commits into from

Conversation

ds26gte
Copy link
Contributor

@ds26gte ds26gte commented Feb 10, 2025

No description provided.

jpolitz and others added 30 commits March 11, 2018 11:46
- app.json is only read when FIRST CREATED, future deploys do
  not read it
- All values must be strings
Intended for embedding use cases, the type is:

type InitialState = {
    editorContents: string,
    interactionsSinceLastRun: string
}

On load the editor will automatically run definitions with the given
text and then run all the given interactions.

Currently only enabled in embedding contexts.

Need state for two more cases:

- Editing definitions but haven't run at all yet
- Editing definitions after a run
One thing that's challenging is the use of on('change') on CodeMirror,
which triggers for calls to setValue().

In the events API, we change these to all use replaceRange with an
explicit `origin`. However, there are setValue() calls elsewhere in the
codebase. We could ignore these by checking the origin of "setValue",
but this could be a mistake if we do want to propagate around updates
like those. Need to think about this.

For now, filter out ones that come in before we are initialized, and
wait for the reset event to start sending things out. This makes sure
that the initialization of setting e.g. `use context current` doesn't
get sent out as an event.

Sometimes we get "empty" resets from VMT, and this commit just filters
those out. But it's not clear when exactly that happens.
- Don't propagate setvalue events; these are coming from page setup,
  but we want to wait for our 'reset'
- Don't setValue at all if the page is “controlled”. Add a new
  #-parameter #controlled=true that tells the page to not do its usual
  initialization and instead wait for the reset events
- The first 'reset' has a state of '', so deal with that appropriately
  to handle initialization in events.js
@jpolitz jpolitz temporarily deployed to pyret-horizon May 2, 2025 16:07 Inactive
@jpolitz jpolitz temporarily deployed to pyret-horizon May 3, 2025 01:13 Inactive
@jpolitz jpolitz temporarily deployed to pyret-horizon May 6, 2025 17:34 Inactive
@jpolitz jpolitz temporarily deployed to pyret-horizon May 6, 2025 18:06 Inactive
@jpolitz jpolitz temporarily deployed to pyret-horizon May 6, 2025 18:26 Inactive
@jpolitz jpolitz temporarily deployed to pyret-horizon May 7, 2025 13:20 Inactive
@jpolitz jpolitz temporarily deployed to pyret-horizon May 8, 2025 16:03 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants