-
-
Notifications
You must be signed in to change notification settings - Fork 365
Fix Application.Current null exception #3401
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
Conversation
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.
Pull Request Overview
This pull request addresses the Application.Current null exception by adding null-checks before invoking Dispatcher methods on Application.Current.
- Updated calls to Dispatcher.Invoke to use a null-conditional operator.
- Adjusted comments to reflect the possibility of Application.Current being null during application exit.
Small patch and it is good to me. |
This comment has been minimized.
This comment has been minimized.
🥷 Code experts: onesounds Jack251970, onesounds have most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: To learn more about /:\ gitStream - Visit our Docs |
Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX. |
📝 WalkthroughWalkthroughThis change updates the Changes
Sequence Diagram(s)sequenceDiagram
participant VM as MainViewModel
participant App as Application.Current
participant UI as Dispatcher/UI Thread
VM->>App: Check if Application.Current exists (null-conditional)
alt Application exists
App->>UI: Invoke UI operation via dispatcher
else
VM-->>VM: Skip UI operation (safe exit)
end
Possibly related PRs
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (4)
🔇 Additional comments (2)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@check-spelling-bot Report🔴 Please reviewSee the 📂 files view, the 📜action log, or 📝 job summary for details.
See ❌ Event descriptions for more information. If the flagged items are 🤯 false positivesIf items relate to a ...
|
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.
Pull Request Overview
This pull request addresses the Application.Current null exception by updating UI thread invocations in the Show() and Hide() methods.
- Updated invocation calls to use the null-conditional operator in both Show() and Hide()
- Revised comments to clarify behavior when Application.Current is null during application exit
Fix this exception: