-
Notifications
You must be signed in to change notification settings - Fork 0
feat: improvements and bug fixes #22
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
Merged
Merged
Changes from all commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
6db3217
fix(zoom): improve error handling and fallback for zoom backend initi…
daiv05 f725318
fix(dxgi): implement UnmapGuard for safe D3D11 resource unmapping
daiv05 279d110
fix(window): implement mode locking for safe window rebuild and visib…
daiv05 eaad776
fix(zoom): convert stop_zoom_stream and freeze_zoom to async for impr…
daiv05 a244e16
fix(magnifier): add error handling for SetWindowRgn in set_circle fun…
daiv05 1f7e709
fix(canvas): clear autoErase timers and maps on cleanup
daiv05 1d235e3
fix(monitor): use scaleFactor from monitorContext for coordinate tran…
daiv05 2ee163b
fix(zoom): clamp zoom region size to MAX_ZOOM_REGION in capture_zoom_…
daiv05 0f85f67
fix(zoom): clear zoom window handle on mode destruction and validate …
daiv05 1ed0d62
fix(gdi): implement GdiDcGuard for resource management in GDI screens…
daiv05 a28121c
fix(monitor): manage fallback timer for monitor context retrieval
daiv05 c0e1e1f
fix(dependencies): add devtools feature to tauri and update CSP settings
daiv05 693cf06
feat(capabilities): update default capabilities and add mode-windows …
daiv05 463eb79
fix(persistence): implement queuePersist function for overlay and set…
daiv05 ba6f535
fix(cursor): ensure message loop runs correctly in start_mouse_hook f…
daiv05 c3ba11a
refactor(zoom): remove capture_viewport function and streamline dupli…
daiv05 39486f0
fix(zoom): ensure sourceBuffer is set before updating canvas with dec…
daiv05 de9ecb7
docs(zoom): add documentation for ZOOM_BACKEND_STATE initialization
daiv05 8d9d159
fix(overlay): rename handleHideDock to handleCloseOverlay and update …
daiv05 f31a580
fix(window): reassert transparent background for WebView2 and improve…
daiv05 c89966a
feat(onboarding): implement onboarding modal and related functionality
daiv05 cf356c4
feat(cursor): add border width and fill opacity settings for cursor h…
daiv05 183b584
feat: refactor and change default app color
daiv05 44e5741
[autofix.ci] apply automated fixes
autofix-ci[bot] 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| { | ||
| "$schema": "../gen/schemas/desktop-schema.json", | ||
| "identifier": "mode-windows", | ||
| "description": "Minimal capability for overlay mode render windows (no global shortcuts, no autostart)", | ||
| "windows": ["overlay", "whiteboard", "cursor-highlight", "spotlight", "zoom"], | ||
| "permissions": [ | ||
| "core:default", | ||
| "opener:default", | ||
| "store:default" | ||
| ] | ||
| } |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: daiv05/vynta
Length of output: 10441
🏁 Script executed:
Repository: daiv05/vynta
Length of output: 10421
🌐 Web query:
Tauri 2 devtools feature release mode docs💡 Result:
In Tauri 2.0, developer tools (DevTools) are enabled by default in development and debug builds, but they are disabled in production (release) builds by default [1][2][3]. To use DevTools in a release build, you must explicitly enable them. To enable DevTools for a release build, add the devtools Cargo feature to your project's src-tauri/Cargo.toml file [1][2]: [dependencies] tauri = { version = "2.0.0", features = ["devtools"] } Important considerations regarding this feature: 1. macOS Warning: The devtools API on macOS relies on private APIs [1]. Enabling this feature on macOS may cause your application to be rejected by the Apple App Store [1]. 2. Security and Best Practices: It is generally recommended not to ship applications with DevTools enabled in production [4]. The canonical approach for debugging production-like behavior without enabling DevTools in the final shipping binary is to run a debug build using the command: tauri build --debug This creates a build in src-tauri/target/debug/bundle that functions similarly to a release build but includes development features like the inspector [1][2]. If you find the --debug flag is not working as expected (e.g., due to specific environment configurations), ensure your package manager command is correctly passing the flag (e.g., npm run tauri build -- --debug) [5]. 3. Alternative Debugging: For production debugging, consider implementing dedicated logging solutions like the tauri-plugin-log, which allows you to capture logs to a file that users can share with you when issues occur [6]. Additionally, you can configure your bundler to generate source maps (e.g., in vite.config.ts) to make production errors easier to trace if you have access to the environment [6]. 4. Programmatic Control: You can also open or close DevTools programmatically within your Rust code using WebviewWindow::open_devtools and WebviewWindow::close_devtools, typically guarded by #[cfg(debug_assertions)] to ensure this code only runs in debug builds [1][2].
Citations:
tauri buildignores--debugargument tauri-apps/tauri#11768Keep
devtoolsout of the release dependency settauri’sdevtoolsfeature is enabled unconditionally insrc-tauri/Cargo.toml:18, so release builds will ship DevTools support too. The#[cfg(debug_assertions)]guard only skipsopen_devtools(); it doesn’t remove the capability from the binary. Move this behind a dev-only feature and enable it only for local debugging.🤖 Prompt for AI Agents