1) Start with new copy of App - spaces does not recognise it.
You'll have to be more specific about the starting point, like giving
the URL of the App that Spaces doesn't recognize, or at least giving
its Info.plist.
You mentioned before that maybe some UNIX setting might be an issue.
Well, you're not telling us any of those, either.
2) Replace plist with the one below.
Replace plist how? With the Finder? A Terminal command-line?
Something else?
For the experiment to be repeatable, or even analyzable, you have to
be specific about exactly what you're starting with, and just as
specific about exactly the actions taken and the means used.
3) Now change the name of the app in the Finder, launch, quite,
change name back. Spaces seems to pick up the name and icon at last.
When you change the name of an app-bundle, that's one of the things
that triggers Finder into updating the LaunchServices database.
Sometimes moving the app also triggers an update, but sometimes it
doesn't, and I have no explanation why.
Copying the app to another volume (partition or disk-image) also
updates the LS database.
Removing or replacing an app also triggers an update.
Greg - how do you "touch" an app?
In Terminal, enter the command:
touch /path/to/Your.app
You can type in 'touch' followed by a space, then drag your app onto
Terminal's window and drop it. Terminal will automatically fill in
the pathname of your app.
What 'touch' does in this case is change the modified-date of the
directory that is the app-bundle. You can do the same thing entirely
in the Finder by choosing "Show Package Contents" from the contextual
menu, then creating a new folder (it will be adjacent to the Contents
folder), then trashing that new folder.
If you only change things in the Contents sub-folder, this DOES NOT
affect the modified-date of the Your.app directory that contains
Contents. This is why editing Info.plist does not trigger the Finder
into updating the LS database. You have to do something that affects
the mod-date of the Your.app directory, and you have to do it after
the Info.plist is correct and saved.
That's not a great choice of a bundle identifier. It should be
something that's more uniquely distinguishable, like a DNS domain-
name followed by "ClickRepair".
By the way, it's possible there's more than one entry for
ClickRepair.app in the LaunchServices database, and the presence of
those entries might be contributing to the problem. To dump the
database as text, google for the keyword lsregister. It's a command
you enter in Terminal, and it's located in an inconvenient place that
requires a long pathname. If you redirect lsregister's output to a
text file, you can open it in TextEdit and see if there are multiple
entries for ClickRepair.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
