[BUG] Does not detect OpenTTD source properly (Steam)

オープン
#5,688 コメント 0 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp
領域
desktop, devtools

調査の方向性

Start by locating the code that detects installed Steam games and maps them to package sources; the issue does not name a file or provide reproduction steps beyond OpenTTD installed through Steam on a separate SSD. Check how detection handles Steam libraries on other drives and how it determines the installed version. Done means UniGetUI recognizes this OpenTTD installation as Steam and stops reporting a spurious update.

索引モデルが issue の本文から書いたものです。

説明

bug priority: low winget
Please confirm these before moving forward
  • I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
  • I have tested that this issue has not been fixed in the latest (beta or stable) release.
  • I have checked the FAQ section for solutions.
  • This issue is about a bug (if it is not, please use the correct template).
UniGetUI Version

2026.3.3

Windows version, edition, and architecture

Windows 10 Pro 19045.7807 x64

Describe your issue

UnigetUI made a good work of recognized source of applications like game from Steam to avoid checking their update.
However from time immemorial UnigetUI thinks that my OpenTTD game was installed from Winget (it shows source Winget) instead of Steam, always displays "update avaliable" (because it also cannot detect version, obviously).
UnigetUI does not find strange the fact that game is even on separate SSD (Disk D for games) among other Steam games.

Of course, I just put it to "always ignore", but check the state from time to time.

Steps to reproduce the issue

No response

UniGetUI Log
You probably do not need logs
Package Managers Logs
You probably do not need logs
Relevant information

No response

Screenshots and videos

No response

主要言語
C#
スター
26.8k
フォーク
970
平均マージ
17時間 47分
マージ済み PR(30日)
126

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Devolutions/UniGetUI のほかの issue

Devolutions/UniGetUI の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。