On Wed, 2010-02-24 at 11:48 +0000, Peter TB Brett wrote: > On Wed, 24 Feb 2010 10:30:20 +0000, Peter Clifton <[email protected]> wrote: > > On Tue, 2010-02-23 at 22:32 -0800, Jared Casper wrote: > >> On Tue, Feb 23, 2010 at 3:53 PM, Peter Clifton <[email protected]> wrote: > >> > I can't help but feel that some log messages are important enough to > >> > bother the user about - and others are not.. we'll have to see what > >> > people actually using it think, I'm not doing any PCB design work at > >> > the > >> > moment myself. > >> > > >> > >> Maybe add a Warn function along side Message (or something along those > >> lines), and add a flag to HID.log that says whether or not to bring > >> the log window to the foreground? Or go all out and add an enum for > >> severity. It'd be easy to add the plumbing, the hard part would be to > >> go through and decide what Message()s should be Warn()s, etc. > > Why not have a bar (in a "warning" colour) that pops up at the top of the > layout window, and disappears after a short interval (say, 2 seconds). > Clicking the bar would bring up the message window. This is what my phone > (N900, runs Linux) uses for displaying transient warning/notification > messages, and it works really nicely. > > Peter
Neat idea.. and also seems to be a growingly common idiom in other apps due to the recognition that focus-stealing and popping up dialogs when the user isn't expecting them is poor interaction design, resulting in bad usability if it happens often. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
