1-2 of 2 Answers
It is true, the JLab team post tells the workaround: Win + Shift + S. This is going to become a lot more common because guidance from Microsoft deprecates the print screen button.
Sorry, there was a problem. Please try again later.The JLab JBuds Wireless Scissor Keyboard, like most modern keyboards, does not have a dedicated Print Screen key. However, it still has the functionality for taking screenshots, just not through the traditional Prnt Scrn button. Here's how you can capture specific portions of the screen with your JBuds keyboard: Using the Windows snipping tool: Press the Windows Key + Shift + S simultaneously. This will open the Windows snipping tool. Choose the desired snipping mode (Rectangular, Freeform, Window, or Fullscreen). Click and drag your mouse over the area you want to capture. The screenshot will be copied to your clipboard. You can then paste it into any application, like your messaging software or image editing tool. Using a third-party snipping app: Choose your preferred snipping app, many of which support capturing specific regions with custom hotkeys. Popular options include Greenshot, Snagit, or ShareX. Configure the app's hotkey settings to use one that doesn't conflict with any existing keyboard shortcuts on your JBuds keyboard. Press the assigned hotkey and follow the app's instructions to capture your desired region. The screenshot will be saved to the location you specified in the app's settings or copied to your clipboard for immediate use. Alternative methods: Windows Key + Prnt Scrn: This will capture the entire screen and save it as a PNG image in the Screenshots folder under your Pictures Library. Alt + Prnt Scrn: This will capture the currently active window and copy it to your clipboard. While the JBuds keyboard lacks a dedicated Print Screen key, you still have various options for capturing specific screen regions using native functionalities and third-party apps. Choose the method that best suits your workflow and preferred software.
Sorry, there was a problem. Please try again later.
