obsproject/obs-studio

Migrate string-based exceptions during initialization to localized error codes/types

Open

#13,394 创建于 2026年5月3日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)C (72,387 star) (9,239 fork)batch import
Good first issuekind/tech-debt

描述

Currently during initialization OBS will simply throw const char * for issues

https://github.com/obsproject/obs-studio/blob/085a51ab0f0573412a368905bb9a843e2de4cecd/frontend/OBSApp.cpp#L1054-L1061

and run_program happens to know to catch those with

https://github.com/obsproject/obs-studio/blob/085a51ab0f0573412a368905bb9a843e2de4cecd/frontend/obs-main.cpp#L693-L696

This is both messy and also means that these errors can not be localized.

All of these potential errors during initialization should throw a proper exception type that identifies the kind of error with an optional error message for developers, then catch the specific type and display the localized error message appropriate for the error.

贡献者指南

技术栈
ccpp
领域
desktop
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C++ exceptionsOBS initialization flowLocalization concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
The issue involves modifying the initialization error handling in OBSApp.cpp and obs main.cpp. Currently, string based throws and catches are used. The solution should create a proper exception class (e.g., ObsInitException) that includes an error code or type, then catch that specific exception in run program and display a localized error message. The localization system should be used to provide user facing messages based on the error code.