Feature/kbar

[mwritter]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Added Kbar integration to see current keybindings and to preform actions. Dependency added: "kbar": "0.1.0-beta.36" in packages/spectacle/package.json

Fixes #1115

Type of Change

Please delete options that are not relevant (including this descriptive text).

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Added unit test for use-modes.ts, and 'platform-keys.ts'.
use mod+k to view/test feature.

Checklist: (Feel free to delete this section upon completion)

• I have included a changeset if this change will require a version change to one of the packages.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My code follows the style guidelines of this project (I have run yarn format)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes (I have run yarn test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[gksander]

This looks great! A couple small questions, and would be great to have @carlos-kelly kick the tires on this too!

[gksander]

Oh and also, @mwritter – can you add a commit to this branch with a changeset? Should be able to run something like:

pnpm changeset

and then select "minor" for "spectacle", with a note about the kbar implementation. That way, we'll have the changelog record ready when we go to publish this release!

[carloskelly13]

I really like it, wonder if it's worth adding a "return to default mode" when any of the 4 modes are picked

[carloskelly13]

Also let's use the same font styling as we do for Presenter mode

import { SYSTEM_FONT } from 'utils/constants';

[mwritter]

I really like it, wonder if it's worth adding a "return to default mode" when any of the 4 modes are picked

It would make sense 🤔 - What do we think about this @carlos-kelly @gksander