On Sat, Jul 27, 2024 at 3:19 PM Michael or Penny Novack via gnucash-user < gnucash-user@gnucash.org> wrote:
> > I don't agree. If the message, window, or whatever is worth seeing, it > > should persist until the user dismisses it. A fixed display time is > > going to annoy some (who just want to get on with their work) but its > > information will be lost to others (who take their eyes off the screen > > to pull papers from a file or pour a cup of coffee). > > > > And of course if it's not worth seeing, it shouldn't be displayed for > > any amount of time, but rather written to the log file o perhaps the > > trace file. > > Windows that do not close without user action obviously do not need a > delay in order to be seen. Nor do ones that do not need to be seen > EXCEPT to prevent user questions like we have been seeing "why don't I > see this anymore?" > > Keep in mind that we want "machine independence". The program might want > to display something to indicate "process running" when on machine X > (where tales noticeable time) but that message would flash by on machine > Y where took a fraction of a second. Remember, the program doesn't know > if it will be run on a machine where the external drive is HDD or SSD, > for example. > > Personally what I find abominable is something that flashes by so fast I > can't read and so don't know if significant. > > Michael > I agree with you... the file check, for example, needs either a delay or user interaction to know that it run and is finished... it's so fast these days that I cannot tell if it ran. But splash screens are not like that... usually, I turn them off if the program starts fast enough; hopefully, this setting is kept by machine. -- _________________________________ Richard Losey rlo...@gmail.com Micah 6:8 _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
