Skip to main content

Use Input without a device connected

Feature Request


Input going to 0% functionality (current state) when no device is connected feels heavier than it needs to be.

It would be extremely helpful if we could work on our Input key-bindings without having the device connected. Changes would be limited to user action & multi-action section with ability to add, delete, modify, & organizing (group/folders in future updates). There's been so many times i've had a idea for a new shortcut or layout but was unable to access Input since I didn't have my CM2 device with me. ----- The action list can be stored locally so it's always available in the Input app. If a user modifies/deletes any action binded to a device key then push update to device when connected

If change mgmt is not feasible

  • create a new section called "Local Actions" that are then duplicated when added to a key-binding. Then the local action can be modified independently of key-bindings

  • OR

  • limit off-line editing to actions that are not binded to any device which allows users to modify/delete existing actions and create new actions (last resort IMO)

Positive Side Effects:

  • Allows potential customers to 'demo' Input and see what it has to offer! Also allows existing customers to "demo" other products

  • new customers can get a head start on device config while waiting for device to arrive. Helps to maximize chance of users getting max utility out of device sooner

  • Allows users to engage with Work Louder community, provide feedback, & learn best practices which can all help make the long waits for pre-orders less “painful”. Honestly, I was frustrated when I found out I couldn’t use Input over the ~5+ month waiting period.



100% Functionality Offline ( THIS IS THE WAY )

Recent news of the on screen cheat sheet provides a opportunity for `Input` to deliver utility to users with **and without** device.

  • Make the popup window interactive; when an action is clicked on -> fire that shortcut!

  • this allows users to access shortcuts & macros they’ve created while they are on the go without their device

  • to make sure the cheat sheet is always available, allow user to assign a hotkey to display cheat sheet in addition to the super secret touch sensor on CM2.

I repeat, ***THIS IS THE WAY***

Product
Input
Posted by Scott Lanning ·
Status: Under Consideration3 comments

Log in to comment and vote

Comments3

  • Davide // Work Louder

    Team•

    Mar 17

    Hi @Scott Lanning , thanks for your suggestion! This would require a restructuring of how input works as well as handling the arising conflicts between having one local copy of the keymap and the one on the device. That said, it’s doable and we will keep a look on it if it gets more interest from the community.

    • Scott Lanning

      •

      Mar 18

      Agreed this would indeed be a heavy lift. I tried to address challenge in the post via a temporary solution that fully blocks local:device conflicts by only allowing
      - new actions to be created
      - unassigned actions to be modified/deleted (not linked to any device)

      Since bothlayer.json and profile.json files ignore actions & multi-actions that are not assigned to device, the 2 user limitations should avoid conflicts. Actions may already have the required attribute `Assigned (bool)` to block conflicts.

      *"actions" = actions + multi-actions*

    • Scott Lanning

      •

      Mar 18

      As far as the full-send interactive cheat-sheet goes, I’d argue the value-add/justification is already proven given that users pay good money for apps that do the same thing. They are paying $15 to have a few macros available via on-screen radial. CM2 users needed a lot more slots than “a few” so having them available on-the-go feels like huge win.

      Big lift. Big impacc