On Tue, Mar 01, 2016 at 03:46:52PM -0800, Ben Pfaff wrote:
On Tue, Mar 01, 2016 at 06:37:49AM +0100, John Darrington wrote:
> On Sun, Feb 28, 2016 at 10:00:41AM -0800, Ben Pfaff wrote:
>
> I suggest putting it into the output window at startup, once. This
is
> easy to do, it is likely that users will notice, and it is not as
> obnoxious as some of the other options.
>
> For example:
>
> diff --git a/src/ui/gui/psppire-output-window.c
b/src/ui/gui/psppire-output-window.c
> index 469966a..1da4b24 100644
> --- a/src/ui/gui/psppire-output-window.c
> +++ b/src/ui/gui/psppire-output-window.c
> @@ -182,6 +182,15 @@ psppire_output_window_setup (void)
> output_driver_init (d, &psppire_output_class, "PSPPIRE",
> SETTINGS_DEVICE_UNFILTERED);
> output_driver_register (d);
> +
> + text_item_submit (
> + text_item_create (TEXT_ITEM_PARAGRAPH,
> + _("This is a development version of PSPP.
Please be "
> + "alert to the likely possibility that it
contains "
> + "more bugs than a PSPP release. If you
encounter "
> + "bugs, please consider reporting them to
the PSPP "
> + "developers at bug-gnu-p...@gnu.org, to
enable them "
> + "to be fixed.")));
> }
>
>
> The wording seems find to me.
>
> I'm not so sure that is will be as noticable as we would like - it
> will scroll off the top of the screen after a large output.
Why can't the user see it at startup?
The output window is (at least on the window manager I use) below the data
window, unless
explicitly raised. Typically, a user will only raise that window, when she
explicity
has interest in what she thinks is there. The users who stand to benefit
from this
message, are those who are unaware of its content. Such users will typically
start psppire,
run a procedure and THEN look in the output window. Typically the user does
not look in
the output window the moment it starts up.
> And in cases like reported here:
>
> https://lists.gnu.org/archive/html/pspp-users/2016-02/msg00007.html
>
> The user would not have seen the message until after experiencing the
bug, if at all.
The user will see the message as soon as he (or she) starts PSPP. You
are saying that the user in that case experienced a bug before PSPP
started? I don't understand.
No. For reasons mentioned above he will (probably) not see the message. He
will :
Start Psppire; Load the large file (at this point he has not looked in the
output
window - he has no reason to) ; Run a procedure (whereupon, due to the bug, it
enters a very long loop - appears to hang).
J'
--
Avoid eavesdropping. Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
signature.asc
Description: Digital signature
_______________________________________________ Pspp-users mailing list Pspp-users@gnu.org https://lists.gnu.org/mailman/listinfo/pspp-users
