13 Dec 2009, 22:41
FinderPop 2.2.4b4 THRILLSEEKER BETA (tagged "Can you feel that heartbeat under the sea?") is now available.
* Now works with the Snow Leopard Finder in 32-bit mode (apparently some intel Macs can't run 64-bit apps - thanks Stephane for the info!)
* A few more smallish bugfixes - FinderPop menu items with labels now appear correctly in the FinderPop daemon under Snow Leopard (they'd been clipped previously.)
* This should (ok, "might") work in 10.5 Leopard but I can't tell as the disk drive with my 10.5 partitions on it has started making strange clicking noises
-- I'll have to grab another disk and reinstall 10.5. Hopefully during the week.* Adds a goofy scripting facility to run scripts or programs before generating the FinderPop menu, allowing these scripts to add or remove items from the FinderPop Items folder (or indeed any folder.) Basically any file whose name ends in ".fpsh" in the FinderPop Items folder (or one level below it, ie in a folder inside the FinderPop Items folder) will be run before and after FinderPop runs; the Finder selection is passed to the script, the script can examine the selection and add or remove items to the FinderPop Items folder which will then appear (or not) in the FinderPop popup menus. I'll explain this in more detail in another post as it's not likely to be useful to any but a handful of people... but it could be used to reintroduce a measure of contextuality. I was looking at supporting old CM plugins but there are numerous problems with 64/32bitness.)
What remains to be done:
* Control-free-clicking
* Contextual Menu Support in apps other than the Finder
* FinderPop info help tag windows
Note that the menus popped up as a result of control-clicking in the unused menubar is handled by the old 32-bit finderpop-daemon so everything works as it used to there (although there was a drawing problem with labels in FP menus which has been fixed in 2.2.4b4.)
If you're installing this over a previous beta, you'll have to restart or logout for it to take effect. (Alternatively if your terminal skills are up to scratch, type killall finderpop-daemon and then open the newly-installed FinderPop prefPane which will cause the newly-installed daemon to start; any programs launched after this point will have the new FinderPop sauce added. Since the Finder will already have been patched using the previously installed version, you'll have to restart the Finder too, you can type killall Finder for that.)
--turly
I will eventually pull everything together into a 10.4/10.5/10.6-compatible release.
As usual, if there are any issues with this: http://www.fnarr.net/fp
PS: Anyone wishing to see the (rather impressive) results of my recent shoulder operation might like to look here...
14 Dec 2009, 09:03
thank you turly new beta
it works very well for the users who have their home directory under /Users/.
but it doesn't work well for the users who moved their home directory to other disk partition.
14 Dec 2009, 09:47
My home directory is on a separate disk and FP works for me.
What does echo ~ print when you type it into Terminal.app?
I presume you've made a symlink to point at the new location:
- Code:
ln -s /Volumes/OtherDisk/TurlyHomeDir /Users/turly
14 Dec 2009, 18:40
Thank you quick responce.
turly wrote:My home directory is on a separate disk and FP works for me.
What does echo ~ print when you type it into Terminal.app?
"echo ~" command returns "/Volumes/HOME". I have set my home directory to it through Acount preference pane's "Advances Option...".
turly wrote:I presume you've made a symlink to point at the new location:
- Code:
ln -s /Volumes/OtherDisk/TurlyHomeDir /Users/turly
Yes, I done it now and set my home directory to original position ("/Users/banjo") through Acount preference pane's "Advances Option...". Then restart the machine.
"echo ~" command returns "/Volumes/banjo" now.
..........but FP does not work still......
I will do clean install FP. Please let me know all files that FP creates.
14 Dec 2009, 18:49
When you say FP does not work for you, can you be more specific?
Does FinderPop install correctly (ie without complaint)?
Is anything unusual printed out in Console.app when you open the FinderPop preference pane, or when you reboot?
Does clicking-in-the-unused menubar area work? (Assuming you have it enabled.)
Does clicking on the "Open FinderPop Items" button in the prefPane's "Items" tab open the FinderPop Items folder? Where is it?
To uninstall FP, just click on the "Uninstall FinderPop" button in the preference pane's "Etc." tab.
14 Dec 2009, 20:37
turly wrote:When you say FP does not work for you, can you be more specific?
Does FinderPop install correctly (ie without complaint)?
Is anything unusual printed out in Console.app when you open the FinderPop preference pane, or when you reboot?
Does clicking-in-the-unused menubar area work? (Assuming you have it enabled.)
Does clicking on the "Open FinderPop Items" button in the prefPane's "Items" tab open the FinderPop Items folder? Where is it?.
At first, I want to notice "it works very well for the users who have their home directory under /Users/".
My enviroment specific:
Machine - iMac 8.1
RAM - 2GB
OS - 10.6.2
My startup disk has 5 partition. 1st partition is startup disk. 2nd partition is my home directory. 3rd is for boot camp. 4th is for 3rd party apprications. 5th is empty.
"Open FinderPop Items" button works. "~/Library/FinderPop Items" is opened.
"clicking-in-the-unused menubar area" is OK.
"inline menu" is OK.
"desktop" & "process" submenu are OK.
contents submenu is NG.
bundle's submenu is NG.
can't open file through inline menu's appication. (Only application is started but the selected file is not opend.)
When I open a text file through FP's inline menu's text editor, console message is followed: ("mi" is a japanese text editor")
- Code:
12/15/09 4:22:11 AM [0x0-0xe00e0].mi[1284] SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0xd3bc00, p = 0xd3bc3c, pEnd = 0xd3be06)
not only text editor, image file with Preview.app has same problem.
14 Dec 2009, 21:04
SystemFlippers is an internal OS X routine; FinderPop doesn't call it and I don't think that message has anything to do with FP.
Are you running anything which might conflict with FinderPop?
It sounds like FP cannot see the Finder selection. When you right-click a file in the Finder, the filename should appear in bold in the FinderPop menu. Is this the case?
Are you running in 32-bit Finder or 64-bit? (The messages in Console.app that FinderPop prints each time it patches an app will say something like "FinderPop_x86-64-22404" when it's patching a 64-bit app, and "FinderPop-i386-22404" when it's patching a 32-bit app.
Sorry for all the questions - I'm not at my Mac and these are off the top of my head with no access to the code.
15 Dec 2009, 05:25
I wish to express my gratitude for your kind answer.
turly wrote:Are you running anything which might conflict with FinderPop?
•My Login items are followed:
Temperatue Monitor Lite
URL Manager Pro
Classic Menu --- Apple menu patcher
CrossOver CD Helper
MenuCalenderClock --- menu extra item
finderpop-daemon
ProFire Agent --- Audio interface driver
Kawasemi Enabler --- 3rd party Japanese Input driver
•Other preferencePane
Archives
DivX
FinderPop
Flip4Mac WMV
HHKB Lite2 for Mac --- 3rd party keyboard customizing tool
M-Audio Profire --- Audio interface setting tool
MacFUSE --- installed by Parallels
multiXFinder
Perian
SANE
turly wrote:It sounds like FP cannot see the Finder selection. When you right-click a file in the Finder, the filename should appear in bold in the FinderPop menu. Is this the case?.
There is no bold file name in the context menu with FP on my desktop.
turly wrote:Are you running in 32-bit Finder or 64-bit? .
I think I'm runnning 64-bit Finder.
- Code:
12/15/09 12:47:08 PM [0x0-0x15015].com.finderpop.fp-injector[383] ===============================================================================
12/15/09 12:47:08 PM [0x0-0x15015].com.finderpop.fp-injector[383] 12:47:08: INIT FinderPop-beta-i386-22404 on 10.6.2 (built Dec 13 2009 21:44:07)
12/15/09 12:47:08 PM [0x0-0x15015].com.finderpop.fp-injector[383] ===============================================================================
12/15/09 12:47:08 PM [0x0-0x15015].com.finderpop.fp-injector[383] FinderPop-beta-x86_64-22404: Patching 'Finder' 0:7007 (Immed-e)
12/15/09 12:47:19 PM [0x0-0x15015].com.finderpop.fp-injector[383] {FPopLoad AESendMessage fails (-1712)}
12/15/09 12:47:23 PM [0x0-0x15015].com.finderpop.fp-injector[383] FinderPop-beta-x86_64-22404: Hey! We patched Finder only 246 ticks ago - it must have crashed (?) so we're not patching it again
12/15/09 12:47:25 PM [0x0-0x15015].com.finderpop.fp-injector[383] FinderPop-beta-i386-22404: Not patching Rosetta app 'URL Manager Pro' 0:00010010
15 Dec 2009, 11:26
Yes, thanks, that's definitely 64-bit Finder. OK, now I need to figure out why FinderPop does not appear to know what files you clicked on in the Finder. And you say it works OK if your home directory is in /Users but not if it's on another disk?
I'll have to download and install some of your extensions (multiXFinder and Classic Menu) to see if they conflict somehow with FP.
15 Dec 2009, 16:38
I just downloaded it and tried it on an iMac 2.66ghz running Snow Leopard. Contextual menus seem wickedly fast; no hesitation at all as you drill through. Looks good so far!
16 Dec 2009, 00:17
No problems here in New York.
16 Dec 2009, 05:26
turly wrote:And you say it works OK if your home directory is in /Users but not if it's on another disk?
Yes.
And I have tried to startup without all login item and other preference panes except FP. But it doesn't work well....
I will report when I find anything. Thank you.
17 Dec 2009, 17:49
2.2.4b4 conflicts with MaxMenus 1.5.1 (from Proteron) >http://www.versiontracker.com/dyn/moreinfo/macosx/13779<. When FinderPop is installed, menus drawn by MaxMenus lose the file/folder icons EXCEPT when drawing the Applications folder menu. I assume both prefpanes are patching some of the same routines. FWIW, it looks like Proteron has bit the dust since their website seems to be gone, although the download link still works. Their app hasn't been updated for a couple years, but seems to work fine under Snow Leopard. I know there's some functional redundancy in using both FP and MaxMenus, but I like them both.
Running 10.6.2 on a new white unibody MacBook 6.1.
23 Dec 2009, 17:55
There is a weird thing happening when using any of the bash finderpop extensions.
When applied to a single object (file/folder), the path to the object is correctly transmitted to the script; when applied to a multiple selection, it seems that the first item of the selection is lost.
Here is a simple demo script:
#!/bin/bash
echo $# $1 >>~/Desktop/log.txt
I am guessing that it is a bug in the way finderpop builds up the selection list.
It was already present in b3
Best regards, and merry christmas all !
23 Dec 2009, 22:13
Alain - this should be fixed in 2.2.4b6
shulcslt - similarly, I haven't downloaded MaxMenus, hopefully after Christmas!
hikki - I made one very minor tweak to how I try to get the Finder selection; I really doubt that it will fix your problem which alas I cannot reproduce. I still haven't had time to download and install your other extensions to see whether FP conflicts with them.
If worse comes to worst, I will send you a debug version of FP with lots of logging sometime to see if we can get to the bottom of the problem.
In the meantime, have a good Christmas and an even better New Year!