On 06/03/2010 12:00 AM, Joost 't Hart wrote: > On 06/02/2010 11:48 PM, Israel Chauca F. wrote: > >> On Jun 2, 2010, at 11:41 AM, Alexander Wagner wrote: >> >> >>> Joost 't Hart wrote: >>> >>> Hi! >>> >>> >>> >>>>> 1. Yesterday i downloaded Scid 4.2.2, and i also bought the >>>>> "scidtactics.zip" package. >>>>> 2. When i launch Scid, two windows open, one of them saying it cannot >>>>> find the bases directory - see the attached .jpg. >>>>> >>>>> >>>>> >>>> This is normal behaviour. This "bases" directory is - sort of - the >>>> standard path to all your databases. Once scid is running, you can set it >>>> through one of the options. >>>> Having said that: This is alert not exactly user friendly and personally I >>>> do not use the standard path at all. Hence I feel there is no reason >>>> whatsoever for this pop-up. >>>> >>>> >>> Should we move it to the inital startup of the tactics training? Ie if no >>> path is set alert it there and move on to the proper dialogue? I could >>> check how to do this. Opinions? >>> >>> >> Sounds reasonable to me. >> >> >> >>>>> 3. Though the smaller window has a button marked "Ok", nothing happens >>>>> when i click on 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? >>> >>> >> While I think that showing the splash window by default is useful, John is >> talking about the bases not found dialog, not the splash window. I don't >> know why, but once that dialog pops-up, it cannot be dismissed, clicking on >> the ok button or typing Enter doesn't work (actually, seems like the button >> doesn't receive the click or the keystroke) and you can't interact with any >> other window on Scid, so it looks like it froze, but I think it didn't. >> >> > Hm, I cannot confirm this on my Linux box. Pressing OK dismisses the > "bases not found" dialog. Most of the time I do this rather quickly, > that is, before the real scid windows pop up. >
Aha, maybe some helpful addition: Scid startup is actually blocked until I press the OK button in the "base directory" popup. If John is really not able to effectively hit this button (which is something Israel needs to figure out for Mac), it may be the case that scid is hanging indeed! > I understand that John was not talking about the splash screen indeed. > But this screen may produce some insight as to understand at what stage > the scid app crashes - if it does do so. > > >> >> >>> >>> >>>>> 5. I have a 27" iMac intel duo, running OS X 10.6.3. >>>>> 6. I have lots of experience maintaining my Macs, but nothing i've tried >>>>> makes any difference. >>>>> 7. What suggestions do you have? >>>>> >>>>> >>>> Did you have an older version of scid on your system? If so, you may want >>>> to try to set your existing ~/.scid folder aside. >>>> >>>> >>> I think John is using a Mac. What's the translation of ~/.scid on the Mac? >>> >>> >> It's the same path. >> >> >> >>>> Can you start scid from a command line, and check if some information is >>>> dumped there? >>>> >>>> >>> I may add that the "command line" is AFAIK called "Terminal" on the Mac >>> (and its starter is well hidden). Depending on the dmg setup it might not >>> be too obvious how to start the app from there as far as my little >>> experience with the Mac tells me. Israel, could you give a helping hand >>> here? You're the expert. >>> >>> >> Launching Scid from the terminal is not that intuitive, assuming the >> Scid.app is in the Applications folder, the command to lunch scid would be: >> >> /Applications/Scid.app/Contents/MacOS/scid >> >> 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 > > ------------------------------------------------------------------------------ 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
