Bug 163513

Summary:	provide obvious visual indicator when changes are made
Product:	[Unmaintained] kdelibs	Reporter:	Maciej Pilichowski <bluedzins>
Component:	kdeui	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	cfeck, finex
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maciej Pilichowski 2008-06-08 10:32:47 UTC

Version:            (using KDE 4.0.4)
Installed from:    SuSE RPMs

When you make a change it is hard to say if something was changed (activating buttons are not so obvious). Please add clear text -- in the title, or below the name of the module, or in status bar:
modified.

Comment 1 FiNeX 2008-06-08 18:52:29 UTC

It could be even more interesting if widgets themself will give a feedback. This could be useful not only in systemsettings, but even in all apps. What I'm thinking for is adding a visual indicator on field which was modified. Maybe it could be proposed to TT too.


What do you think Maciej?

Comment 2 Maciej Pilichowski 2008-06-08 20:14:02 UTC

Finex, _YES_!!! :-) It is a dream-wish for me, because it would become killer-feature for KDE.

I am only worried about complexity, but from user point of view -- a breeze, finally you _see_ all the changes.

Comment 3 FiNeX 2008-06-08 20:59:25 UTC

At first I change this bug to kdelibs->kdeui, let see what developers think about.

Comment 4 Christoph Feck 2010-09-01 01:33:24 UTC

Any ideas/suggestions/mockups about the visual representation? Ideally something that does not cause a relayout, i.e. nothing that adds, modifies or emboldens text, because it would be annoying when the widgets move just because of a change.

For all KConfigDialogManager based applications it should even be possible to check which widgets have changed contents.

Comment 5 Christoph Cullmann 2024-09-14 16:18:54 UTC

Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann