On Jun 2, 2010, at 11:41 AM, Alexander Wagner wrote: > >>> that button. >>> 4. The only option is to force-quit the program. >> At least, the smaller window dialogue should disappear. Does it? >> This sort of confusion may be the result of some of our wiser friends to no >> longer show scid's start-up banner by default. >> Starting scid may actually take quite some time. Are you sure that you do >> not kill the process while scid is still booting up (observe memory >> consumption or something like that in a process monitor)? > > Ok, you spelled out my concerns about disabling the start up dialogue. Can we > get some opinion about this point? IMHO it is a very sensible thing. IMHO it > is valuable especially as it displays the texts it does. But loud complaints > about usability made me to hide it by default. > > BUT: it should only be hidden in the CVS version not to the last release. > Therefore John should see it, not?
I just helped a user that had permissions problems with his $HOME and Scid would quit because of this, I was able to help him just because he took a screenshot of the splash window before Scid quit. Since he couldn't change any options using the menu and unless the errors would have appeared in the terminal if I had instructed him to run Scid from there, I wouldn't have been able to help him without the splash window. I think that having the splash window can be helpful for problems where Scid doesn't finish the start-up process, like the one I mentioned before. I vote to keep it. Israel ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
