microsoft/PowerToys

Multiple Commands on the Same Keys and Values Should be Shown in Top-right Pane

Open

#25,552 opened on Apr 15, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (7,978 forks)batch import
Help WantedIdea-EnhancementNeeds-TriageProduct-Registry Preview

Repository metrics

Stars
 (133,154 stars)
PR merge metrics
 (Avg merge 14d 20h) (117 merged PRs in 30d)

Description

Microsoft PowerToys version

0.69.1

Installation method

Microsoft Store

Running as admin

Yes

Area(s) with issue?

Registry Preview

Steps to reproduce

Type text as per screenshots

Here, it looks like the key is not ultimately deleted: If Key edited multiple times not all actions are shown in top right pane (1)

Here, it looks like the key is deleted whereas it is recreated: If Key edited multiple times not all actions are shown in top right pane (2)

✔️ Expected Behavior

Sometimes keys and values are deleted and recreated again in .reg files to clear them. Multiple actions should be shown in the top-right pane.

Mockup: If Key edited multiple times not all actions are shown in top right pane (Mockup)

❌ Actual Behavior

Currently, not all actions on the same key or value are reflected in the top-right pane.

Other Software

n/a

Contributor guide

Research direction
Investigate the UI update logic in the Registry Preview's top right pane to ensure all multiple commands on the same key are displayed.
Tech stack
csharp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NETWindows Registry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70