Migrate string-based exceptions during initialization to localized error codes/types · obsproject/obs-studio#13394

(0 comments) (0 reactions) (0 assignees)C (72,387 stars) (9,239 forks)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
Issue 種別: refactor
難度: 3
推定時間: 1-3 hours
活動状況: fresh
明確さ: clear
前提条件: C++ exceptionsOBS initialization flowLocalization concepts
初心者向け度: 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.