-
Notifications
You must be signed in to change notification settings - Fork 892
[shortcut] Add shortcut to focus textbox input #209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kyan-yang
wants to merge
1
commit into
sohzm:master
Choose a base branch
from
kyan-yang:textbox-shortcut
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing
isDestroyed()guard before accessingmainWindow.The
emergencyErasehandler (line 298) checksmainWindow && !mainWindow.isDestroyed()before interacting with the window. This handler does not, which can throw if the window has been destroyed while shortcuts remain registered.🛡️ Proposed fix
if (keybinds.focusInput) { try { globalShortcut.register(keybinds.focusInput, () => { console.log('Focus input shortcut triggered'); + if (!mainWindow || mainWindow.isDestroyed()) return; if (!mainWindow.isVisible()) { mainWindow.show(); } else { mainWindow.focus(); } mainWindow.webContents.focus(); mainWindow.webContents.send('focus-input'); });🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
intended; if window is closed and you focus textbox, it is good that it auto opens and focuses. much faster
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kyan-yangGot it! The auto-open behavior when the window is hidden works great with the currentisVisible()check—that's already handling your use case.My concern was specifically about the destroyed case: if
mainWindowis destroyed (not just hidden), callingmainWindow.isVisible()would throw an error before the check executes. TheisDestroyed()guard prevents that crash. It doesn't change your intended behavior—hidden windows would still auto-open—it just adds safety for the edge case where the window object is gone entirely.That said, if you're confident this scenario won't occur in practice, feel free to keep it as-is!
✏️ Learnings added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh wait i confused the two states of visible and destroyed.
if window is destroyed though, app is like shut off and done so no need to check for that; just adds bloat.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kyan-yangFair enough! You're right that in typical app lifecycle scenarios, if the window is destroyed, the app is shutting down and shortcuts won't be triggered anyway. I'll defer to your judgment on keeping it lean. 👍🧠 Learnings used