I had a little look at this and made some changes to launch the correct
version of scid. Hopefully they work.
Steve
--- scidvspc/scripts/sc_remote.tk (revision 834)
+++ scidvspc/scripts/sc_remote.tk (working copy)
@@ -1,8 +1,8 @@
#!/bin/sh
# Emacs please open me in -*-Tcl-*- mode
# the next line restarts using wish if it is in the path \
- exec wish "$0" ${1+"$@"}
-#
+exec `dirname $0`/tkscid "$0" "$@"
+
###############################################################################
#
#
@@ -38,7 +38,7 @@
# use wish to get the winfo and send commands).
#
wm withdraw .
-#
+set SCID "[file dirname $::argv0]/scid"
set debugging 0
#
# showStatus determines whether a status window is displayed or not
@@ -477,7 +485,7 @@
# 2. $next may contain spaces.
updateStatus $next "Done (Open new Scid)" green
dputs "Gave up waiting for interp $interp exec a new one for $next"
- eval {exec nohup scid} $scidArgs {$next} &
+ eval {exec nohup $::SCID} $scidArgs {$next} &
# wait a short time for the new Scid to startup so that it
# will show up in the updated slot list
dputs "waiting 250ms"
@@ -494,7 +502,7 @@
# execute scid to open $next.
dputs "Couldn't find any free slots, start a new interp for $next"
updateStatus $next "Done (Open new Scid)" green
- eval {exec nohup scid} $scidArgs {$next} &
+ eval {exec nohup $::SCID} $scidArgs {$next} &
# wait a short time for the new Scid to startup so that it
# will show up in the updated slot list
dputs "waiting 250ms"
--- On Sat, 12/3/11, Joost 't Hart <joost.t.h...@planet.nl> wrote:
> From: Joost 't Hart <joost.t.h...@planet.nl>
> Subject: Re: [Scid-users] Opening a second base by double clicking on it
> To: "Alexander Wagner" <a.wag...@physik.uni-wuerzburg.de>
> Cc: scid-users@lists.sourceforge.net
> Received: Saturday, 12 March, 2011, 9:44 PM
> On 03/11/2011 05:54 PM, Alexander
> Wagner wrote:
> > On 03/10/11 22:21, Joost 't Hart wrote:
> >
> > Hi!
> >
> >>>>> I often open game files by double
> clicking on them from Nautilus and
> >>>>> would like the system not to launch a
> second Scid instance when there
> >>>>> is already one. Is that possible?
> >>>> There is a helper app called sc_remote
> that should do the trick. Ie.
> >>>> calling sc_remote instead of Scid.
> However, as I try it I fear that
> >>>> something got messed up there. I'll take a
> note.
> >>> For me it works, but launches the wrong scid
> version - the one in my
> >>> path (4.2.2). Hm, again my scid preferences
> (board and the like) are
> >>> nuked :-(
> >>>
> >>> $
> sc_remote<path-to-dbase>/<dbase-name-without-file-extension>
> >>>
> >>> If it does not work for 4.3 (only systems),
> something in scid seems to
> >>> have fallen apart.
> >>
> >> No worries. Got it working here by patching lines
> 480 and 497 of
> >> sc_remote:
> >
> > I fell upon the main issue you mentioned. (Ie. it
> invoked the wrong
> > scid version). It works indeed one just gets a
> superflous window.
> >
> >> scid => ./scid
> >>
> >> thus making sure the local scid app is invoked.
> >>
> >> Not the most elegant solution...
> >
> > I think setting the PATH environment variable
> correctly would be a
> > more elegant solution.
>
> Maybe not :-)
> Setting up PATH ensures that the correct sc_remote is
> executed. I feel
> that sc_remote can (should?) trust that the target scid
> executable is a
> sibling in its own parent directory (in just the same
> fashion as the
> scid script is locating the tkscid binary), instead of
> parsing the PATH
> environment once more.
> Simpler and more intuitive, imho.
>
> My patch is really ugly in that it only works if scid sits
> in the
> current working directory (regardless of sc_remote's
> location!).
>
> Cheers,
> Joost.
>
> >
> > cu
> > Alexander
> >
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Scid-users mailing list
> Scid-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scid-users
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
