quarto-dev / quarto-dev/quarto-cli
Chalkboard: annotations in speaker view are not mirrored to main presentation
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 6k
- Forks
- 458
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 41
Beschreibung
Bug description
When using the chalkboard feature and adding some annotations in a speaker view setting, the annotations are not mirrored to the main presentation.
This is an issue as usually one looks at the speaker view during a presentation on the laptop while the main audience looks at the mirrored slides behind/beside the speaker. For speakers, it's not easy to spot that things are not synchronized.
Adding annotations only on the main presentation view would require taking the mouse across screens which is fiddly and takes additional time.
quarto v1.1.120
Checklist
- Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
- Please format your issue so it is easier for us to read the bug report.
- Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
- Please document the operating system you're running. If on Linux, please provide the specific distribution.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
The issue names no source files, tests, or entry points. Start by reproducing the chalkboard behavior in speaker view and the main presentation, then trace how annotations are synchronized between them. Done means annotations added in speaker view appear on the main presentation.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript
- Bereich
- frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100