buyfakett/kazoottt-blog-v2
1
0
Fork 0
mirror of https://github.com/KazooTTT/kazoottt-blog-v2.git synced 2025-06-23 02:31:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update docs and sort content

Browse Source
This commit is contained in:
github-actions[bot]
2025-02-07 09:31:29 +00:00
parent 0defa34797
commit f0e2b9081e
4 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/content/note/Possible Causes and Solutions for Focusee Switching System Audio to Speaker Playback forcibly.md
View File

@ -11,7 +11,7 @@ tags:
- BlackHole2ch
finished: true
published: true
slug: possible-causes-and-solutions-for-focusee-switching-system-audio-to-speaker-playback-forcibly?lang=en
slug: possible-causes-and-solutions-for-focusee-switching-system-audio-to-speaker-playback-forcibly-en
description: 如果你想使用Focusee录制系统音，首先需要安装Gemoo Speaker，安装后可以将输出设备更改为Gemoo Speaker，并用它录制系统音。但是，注意不要在安装Gemoo Speaker的过程中也安装BlackHole2ch，这可能会导致无法正确录制音频。解释安装BlackHole2ch的方法是删除与其相关的文件夹。 如果你需要录制系统音时，可以使用OBS。首先，添加屏幕捕获源，然后选择是否要录制桌面音或应用音。 如果你需要录制系统音时，可以使用OBS。首先，添加屏幕捕获源然后选择是否要录制桌面音或应用音。
NotionID-notionnext: 80f19b4c-d207-45a0-bbbb-39641a9dc330
link-notionnext: https://kazoottt.notion.site/Possible-Causes-and-Solutions-for-Focusee-Switching-System-Audio-to-Speaker-Playback-forcibly-80f19b4cd20745a0bbbb39641a9dc330

2
src/content/note/Reasons Not to Recommend Purchasing Focusee for macOS Users.md
View File

@ -15,7 +15,7 @@ tags:
finished: true
published: true
category: 软件
slug: focusee-macos-review?lang=en
slug: focusee-macos-review-en
description: An analysis of Focusee's shortcomings on macOS, including severe color discrepancies, slow export speed, and sound card configuration conflicts, along with the author's refund experience.
NotionID-notionnext: c692f30c-bcbc-48fd-9739-19e23a3e1e40
link-notionnext: https://kazoottt.notion.site/Reasons-Not-to-Recommend-Purchasing-Focusee-for-macOS-Users-c692f30cbcbc48fd973919e23a3e1e40

2
src/content/note/open-graph intro.md
View File

@ -5,7 +5,7 @@ author: KazooTTT
tags: []
finished: true
published: true
slug: open-graph?lang=en
slug: open-graph-en
description: Open Graph is a protocol introduced by Facebook in 2010, designed to enhance the display of preview cards when sharing links on social networks like Twitter. It allows websites to control how their content appears when shared, differentiating between links that show previews and those that do not. Twitter also has its own card system, which takes precedence over Open Graph if both are present. Tools like OpenGraph.xyz and opengraph.dev help in previewing and generating Open Graph meta tags for better social media sharing.
NotionID-notionnext: 96e4d436-6fd9-4fec-865c-ac2d80b06be0
link-notionnext: https://kazoottt.notion.site/open-graph-intro-96e4d4366fd94fec865cac2d80b06be0

10
src/content/post/Share My Incorrect Usage Cases of Zustand.md
View File

@ -13,7 +13,7 @@ tags:
finished: true
published: true
category:
slug: share-my-incorrect-usage-case-of-zustand?lang=en
slug: share-my-incorrect-usage-case-of-zustand-en
description: Zustand is a state management library that is simple and easy to use. It allows you to access the state via a single selector or shallow comparison to prevent unnecessary re-renders of all components. When the state is updated, you can use `useShallow` to retrieve only the required data. Additionally, you should follow the principle of minimal granularity, only fetching the necessary data instead of using multiple stores to manage different states. Moreover, state that is unrelated to the UI does not need to be accessed via a selector. The correct approach is to directly access the store within the `handleSave` method.
toAstro: true
date_created: 2025-01-04T11:44:53+08:00
@ -115,11 +115,11 @@ const CurrentCamera: React.FC = () => {
In the official documentation [Flux-inspired practice - Zustand](https://zustand.docs.pmnd.rs/guides/flux-inspired-practice), it is mentioned that you should use a single store, not multiple stores for different states.
> **Recommended patterns**
>
>
> **Single store**
>
>
> Your application's global state should be located in a single Zustand store.
>
>
> If you have a large application, Zustand supports splitting the store into slices.
## Mistake 4: Accessing UI-unrelated state via selectors
@ -166,4 +166,4 @@ const ComponentA = () => {
[master branch notes/zustand learning notes](https://github.com/puxiao/notes/blob/master/zustand%E5%AD%A6%E4%B9%A0%E7%AC%94%E8%AE%B0.md)
[How to efficiently manage React local state? This time I chose Zustand! | Bosh's Technical Exploration Notes](https://notes.boshkuo.com/docs/React/zustand#%E7%82%BA%E4%BD%95%E9%81%B8%E6%93%87%E4%BD%BF%E7%94%A8-zustand-)
[How to efficiently manage React local state? This time I chose Zustand! | Bosh's Technical Exploration Notes](https://notes.boshkuo.com/docs/React/zustand#%E7%82%BA%E4%BD%95%E9%81%B8%E6%93%87%E4%BD%BF%E7%94%A8-zustand-)