Repository navigation
fix(studio): proportional 41/59 setpoint layout, equal phasor/wave, commit-only numeric editing #277
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
Closed
masarray
wants to merge
8
commits into
fix/p0-studio-responsive-start-first-click-20261021
from
fix/p0-signal-matrix-commit-layout-20261021
Closed
fix(studio): proportional 41/59 setpoint layout, equal phasor/wave, commit-only numeric editing #277
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
ff2a94a
fix(layout): 41/59 compact split, equal phasor-waveform height and lo…
masarray f2e4332
fix(matrix): atomic Enter/Tab/blur/outside commit; no 90ms TX while t…
masarray 2f6c397
test(ui): enforce compact 41/59 split, equal previews, decimal normal…
masarray 1bd2003
test(matrix): allow explicit context-menu SET, forbid obsolete keystr…
masarray a1f4abf
test(layout): retire old 265px phasor cap; require equal-height resiz…
masarray f1a42b4
fix(layout): hide redundant selection readback at narrow widths to pr…
masarray 8c1e811
test(layout): require Quality controls fit the narrow setpoint matrix…
masarray 5068468
ci(studio): publish exact-head direct setup EXE before long Windows i…
masarray File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the frequency editor, the new normalization does not actually make both
0.5and0,5enterable regardless of locale:frequencyFieldstill has a locale-awareDoubleValidatorat line 1176, which validates or rejects keystrokes beforeparseOperatorNumber()receives them. Thus on locales whose decimal separator differs from the typed character, the alternate form can be filtered or interpreted under grouping rules; the field needs a validator that explicitly accepts both syntaxes, or validation must be left to this parser.Useful? React with 👍 / 👎.