[Starkit] Tclkit and Mac OS X 10.4

[Daniel A. Steffen]

JC, Frank,

On Saturday, Jun 4, 2005, at 18:24 Australia/Sydney, Jean-Claude 
Wippler wrote:

> Frank Pilhofer wrote:
>
>> One user reports,
>>
>>> The "Wish" window comes up just fine, but for some reason, I
>>> cannot get the gorilla-1.1.kit.sh to run....
>>
>> Another says,
>>
>>> If so, Gorilla has stopped working for me after installing OSX
>>> Tiger. Do you have any advice? I've installed the latest version
>>> of tcltk from http://tcltkaqua.sourceforge.net/. That opens with
>>> two blank windows now when I open Gorilla.
>>
>> As I am writing this message, I realize that the TclTkAquaBI
>> mailing list might be more relevant.
>>
>> But maybe somebody on this list has some insight, and could give a
>> tip what I could reply to my desperate users?
>
> I've seen the same behavior - a blank toplevel + console, when 
> double-clicking a .kit file in Tiger.  Did not think much of it since 
> I usually launch from the command line (and most of the time it's the 
> X11 version, not Aqua).
>
> Digging deeper: argv is set to "-psn_0_13500417", i.e. no filename 
> added (the added -psn stuff is "normal" on OSX).
>
> From the command line, typing "/usr/bin/wish blah.kit" works.
>
> I tried to make a script that would be double-clickable, but couldn't 
> figure it out.  Maybe someone else has a tip - I can't make more time 
> for this today.
>
> Have seen similar behavior with Vim, btw - when I drag a file to Vim 
> which I have in the dock, it comes up with a fresh screen.  Dragging 
> it again while it's running then opens up the right file.
>
> Look like 10.4 changed some startup detail.  Blech.

presumably double-clicked .kit was handled by my Launcher app in 10.3 ? 
are the .kit files still bound to Launcher in 10.4 ? otherwise you may 
have to reassociate them manually to Launcher (via the Finder Info 
window), maybe because something else on the system now claims .kit by 
default ? maybe Wishkit.app has become associated to .kit directly ? 
(why/how though?)

note that Launcher writes diagnostic output to console.log, so if it is 
indeed Launcher that is starting wishkit the log will have the exact 
arguments it passes along, but as it doesn't pass any -psn* arguments, 
the fact that you got this above makes me suspect that .kit somehow 
launched Wishkit.app directly.

can't test in Tiger here right now, I'll try to investigate this next 
time I reboot my box into Tiger, but it'll be a few days...

BTW, for the 8.4.10 BI, I'm switching the Launcher association for .kit 
to 'tclkit' directly, as this is now the new aqua tclkit (there is also 
a tclkit-X11 and a wish-X11 now); wishkit is no longer really needed 
(but may still be useful because it can have an icon and tclkit-aqua 
can't)

Cheers,

Daniel

-- 
** Daniel A. Steffen     **  "And now for something completely
** Dept. of Mathematics  **   different"    Monty Python
** Macquarie University  **  <mailto:steffen at maths.mq.edu.au>
** NSW 2109 Australia    **  <http://www.maths.mq.edu.au/~steffen/>