You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
Currently, Yomitan automatically takes a screenshot of the screen where the word is added from (usually the screen with browser window). This works fine most of the time but becomes a bit inconvenient when using dual-monitor setups. For example, I use my secondary screen for looking up words on the search page, but the content I actually want a screenshot of (in this case a visual novel) is on my primary screen. Since Yomitan doesn’t let me choose which screen to screenshot, it ends up capturing the browser, which isn’t helpful when studying the words I added.
Proposed Solution:
It would be great to have an option in the settings to choose which screen the screenshot comes from. For example, an option to always capture the primary screen or the ability to select a specific screen instead of always defaulting to the one where the word is added from.
The text was updated successfully, but these errors were encountered:
Problem:
Currently, Yomitan automatically takes a screenshot of the screen where the word is added from (usually the screen with browser window). This works fine most of the time but becomes a bit inconvenient when using dual-monitor setups. For example, I use my secondary screen for looking up words on the search page, but the content I actually want a screenshot of (in this case a visual novel) is on my primary screen. Since Yomitan doesn’t let me choose which screen to screenshot, it ends up capturing the browser, which isn’t helpful when studying the words I added.
Proposed Solution:
It would be great to have an option in the settings to choose which screen the screenshot comes from. For example, an option to always capture the primary screen or the ability to select a specific screen instead of always defaulting to the one where the word is added from.
The text was updated successfully, but these errors were encountered: