[Feature Request]: Separate custom storage paths for Projects, Videos, and Screenshots (Crucial for Local/Desktop Licenses)

未关闭
#1,857 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
rust, tauri
领域
desktop

调研方向

从桌面 Settings 面板开始,追踪项目、视频导出和屏幕截图现有的保存路径。明确每个位置如何选择和持久化,然后验证项目、MP4/GIF 导出和屏幕截图是否使用各自配置的目标位置。

由索引模型根据 Issue 内容生成。

描述

Hi @richiemcilroy,

For users operating entirely on the standalone Desktop License without Cloud features, storage management is a massive priority.

Currently, there is no option in the settings panel to manually define where projects, exported videos, and screenshots are saved.

The Problem:
By default, many users have their system "Pictures" or "Movies" folders automatically synced to cloud providers (like iCloud, Dropbox, or OneDrive). Since video project files are massive compared to screenshots, I would consider not the same path.

I want my screenshots to go to my cloud-synced folder for quick sharing, but my heavy video & projects separated on different drives.

Proposed Solution:
Please add a "Storage" or "Paths" section in the Settings panel with the following options:

  1. Default Project Location: Choose a custom path where raw recording segments and project files are stored.
  2. Video Export Destination: Define a default folder for finished MP4/GIF exports.
  3. Screenshot Destination: Set a custom path specifically for saving local screenshots.

Giving local power-users full control over their directory geometry would be a massive quality-of-life improvement for storage management.
Thanks, Denny

主要语言
Rust
星标
25k
派生
2.4k
平均合并
1 天 8 小时
30 天内合并 PR
676

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CapSoftware/Cap 的其他 Issue

查看 CapSoftware/Cap 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。