[Kde-games-devel] Kigo - command line check

[Albert Astals Cid]

El Thursday 25 February 2016, a les 07:29:06, Frederik Schwarzer va escriure:
> OK, if put the absolute path in there, it works.
> On first run, it inserts just the executable name "gnugo" in there,
> which then does not work.
> 
> So I guess I will try to find a way to look for gnugo on first start
> and put its absolute path in that field.

You can have code in the kcfg that runs QStandardPaths::findExecutable 

Cheers,
  Albert

> 
> Regards,
> Frederik
> 
> Am Donnerstag, 25. Februar 2016, 02:31:13 schrieb Frederik Schwarzer:
> > Hi,
> > 
> > in Kigo the user is able to state the command to be used for the Go
> > backend. On my machine, this does not work at all. Neither in the
> > KDE 4 version, nor in the frameworks branch.
> > 
> > QProcess::start() does seem to start the command in "the current
> > dir", wherever that might be.
> > 
> > However, to not chase after deamons here, I ask for others to check,
> > if their Kigo shows the same behaviour. Just to be sure that my
> > system configuration isn't the culprit here.
> > 
> > Just go to the configure dialog and e.g. remove the last letter of
> > the command line, press Apply and see if a disturbingly large error
> > message panel is popping up. After that happens, try to fix this by
> > re-adding the last letter and pressing Apply again. Here I am not
> > able to restore the game to a playable state anymore.
> > 
> > Thanks,
> > Frederik
> > _______________________________________________
> > kde-games-devel mailing list
> > kde-games-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-games-devel
> 
> _______________________________________________
> kde-games-devel mailing list
> kde-games-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-games-devel