trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: [trinity-devel] Request patch testing please

From: Darrell Anderson <humanreadable@...>
Date: Wed, 11 Apr 2012 10:52:44 -0700 (PDT)
> > While "Hide logout process" (process × progress) would
> be like earlier useFancyLogout = true. That's how I intended to.
> 
> I LIKE useFancyLogout :)  That's my vote for default...

Slavek and I are discussing the text string viewed in KControl. Basically, what do we call this dialog that appears and how do we phrase the check box text string in KControl?

Currently my patch says "Show feedback dialog."

The key names used in the ksmserverrc config file are more confusing. Currently there is showFancyLogout and doFancyLogout, which address two different functions. The former controls the dialog and the latter controls the gray fade effect. To avoid confusion, Calvin and I want to change the key names in ksmserverrc as well as in the code. Read the discussion in bug report 258 for details.

Slavek and I want to change the text string in KControl to be understandable to most users.

Calvin is adding the controls for the gray effect. The underlying code has always existed but no controls ever existed in KControl. Likewise, the underlying controls for the dialog exist but no check box in KControl.

When both sets of controls are added, users need to be able to distinguish between the two. The controls Calvin is adding will have the words "gray" and "fade" in the descriptions but that leaves the other dialog to describe.

Part of the problem is the dialog does not show any progress bar/thermometer. Second, although the dialog supports other text strings (read the sources), most users only see the one message of "Saving your settings...." If users saw other text strings within the dialog (which they would if they have other features enabled), then the dialog would seem less lacking.

Part of the problem is words don't always translate will to other languages.

Not to mention that after all of this is settled, the code calling the dialog contains a bug that prevents saving open documents (bug report 922), which demands attention before R14. The only known work-around at this time is to disable the dialog from showing, which without the check box can be performed only by editing the config file.

Little things that snowball into headaches. Sometimes my head hurts....

Darrell