lkellar / neptune Goto Github PK

While we all love scalefactor, eventually, if you zoom too far out, it gets angry and crashes because the number is too big. at some point, the bounds must be resized and scalefactor set back to one.

When a zoom animation is in progress and another zoom is initiated, the first one should be canceled in progress and the new one should begin.

It should be possible to move around the graph via panning with the mouse or a finger. The arrow keys also need to be removed.

There is currently no code to make sure zero appears in the axes.

I feel like, if any of the y=0 or x=0 lines are visible in the axes, it should revolve around that so that line is always present when within the bounds

Additionally, probably even when those lines aren't in bounds, the other axes should probably be based upon them so that if a user moves the screen to a zone where those lines are in bounds, they'll match up.

The discontinuity detection needs to be relooked at to ensure it won't fail on basic functions. Probably tying it to zoom level is an acceptable compromise.

• If something goes above the top bounds and reappears under the lower bounds w/o passing through the middle, don't connect them.

On a sidebar / modal pop up (macOS/iPadOS and iOS respectively), there should be information about the line, its equation, anything its equal to, etc.

Find out what the standard modifier key is for zooming on macOS, and implement it.

Also, same as #10, where my cursor is should be where I zoom.

When hovering over a line on macOS and iPadOS there should be a mini information card similar to #3

If I pinch to zoom in a specific area, the graph should zoom into that area. Currently, it just moves into the center. This may need to be done after panning (see #2)

Zooming needs to be improved in the following ways:

• When zooming out, the axes should be regenerated correctly
• When zooming in into decimal territory, the axes should still generate
• #10
• #11
• #12
• Make notable axes have thicker stroke

How can you tell what the axes represent? There should be some subtle (but also readable) labels.