[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] GNUmed top level exception handler - language advice

From: J Busser
Subject: Re: [Gnumed-devel] GNUmed top level exception handler - language advice needed
Date: Wed, 9 May 2007 21:57:20 -0700

The English seems safe from any needed correction :-)

I might suggest two changes anyway, since technical people won't need it specified that they are running a client whereas non-technical users may be confused by the term, also a question or two at bottom:

However, it is strongly advised to close this client as soon as possible.

suggested (maybe even delete "client"):
However, it is strongly advised to close this GNUmed software ("client") as soon as possible.

It should then be safe to start the client.

It should then be safe to restart GNUmed.


1. Is the screen that is presented by the unhandled exception handler nonmodal, i.e. permitting the user to continue running GNUmed in a separate, already-running window? Will the handler permit the already- open GNUmed windows to be brought into the foreground, hiding this handler window, or will the handler window be "fixed" in the application foreground.

2. Two buttons are offered, OK and Close GNUmed. While the action of "Close GNUmed" seems clear enough, if the action of OK is to dismiss the window and to permit GNUmed to keep running (if it can) maybe we should relabel it "Keep running".

3. Is there value to insert a middle button "Copy to clipboard", this would reduce the work of having to manually select the content of the log (if that is what is displayed inside the text area) even if the copy-to-clipboard functionality is accessible from this part of GNUmed.

4. Is it worth to display the file specification of the log (or would the file specification be included inside the text field)?

On May 9, 2007, at 3:13 PM, Karsten Hilbert wrote:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]