|
November 05, 2003
Save My Screen
I've been working on the Panther update for FruitMenu, and was planning to add an option to invoke a screen saver from the menu, so you can assign a hotkey to it and whatnot. Sadly, it appears that this feature will have to wait because I've accidentally stomped on a Panther bug with that. Since many of you are developers, I figured I'd share the problem with you so you don't step in the same pile as I did. I have filed a bug on Apple's Radar. Quoting myself: If I use Terminal or LaunchServices to invoke ScreenSaverEngine.app in /S/L/Frameworks/ScreenSaver.framework/Resources/ to activate screen saver, and "Require Password to wake this computer from sleep or screen saver" option is set in the Security preference pane, I get a black screen when I try to wake the system up from the keyboard. Normally, the screen goes black and raises the password request dialog when the above mentioned option is enabled, but in this case, the screen goes black, like it should, but the dialog never appears. The only way to exit from the situation, it seems to me, is SSH in and kill the WindowServer or a related process. * STEPS TO REPRODUCE Apple's Developer Technical Support acknowledged the method descibed above is indeed the correct way to invoke a screen saver, and also confirmed the bug. So if you need to invoke a screen saver, be aware of the problem (exists in the Panther 10.3 7B85). As for me, I'll have to comment out the "Lock Screen" feature until it is fixed, to not cause the confusion among users. And to answer your question, "When is the Panther update?", I'll answer "Real Soon Now". =) Trackback Pings: TrackBack URL for this entry: Related:
Comments
Sounds great, but here's my question: where's the Panther version of Dock Detox? All these bouncing icons are giving me a headache. :) Posted by: jason on November 5, 2003 11:57 AMWOAH! In a way that's good to know, Slava. I have a little app that a former NeXT developer and no OS X user/developer wrote up for me and him that simply locks the screen, so I could invoke it from the Apple menu, placed near restart, shut down, and log out. The reason for this app is that I did not want the screen saver to normally lock the screen. So this app invoked its own screensaver with its own option of locking the screen. Anyway, so I've been using it since 10.1.x, but when I tried it in 10.3, I got the same problem as you. So good to hear that it's the OS and not the app itself, since I can't seem to get a hold of the guy these days. Anyway, also good to hear about the progress on FruitMenu. I was hoping that the lull in the blog was due to that. :) I'm going insane (or unsane is it?) without it in 10.3! Posted by: Ken on November 5, 2003 12:11 PMBtw, for now I am using the KeyChain app in the menu bar to lock the screen. I prefer it in the Apple menu, though. I hope Apple fixes this soon. Posted by: Ken on November 5, 2003 12:16 PMOkay, one more comment. Slava, if you could add the functionality to FruitMenu to lock the screen but keep that password requirement seperate from the regular screensaver password option, that would be great. Basically to be able to lock the screen from the Apple menu, but have the normal screen saver setting do its own thing without requiring a password when resuming. For what it's worth, locking the screen from the Keychain Access menubar icon works fine. Posted by: Ken on November 5, 2003 12:51 PMDude, why'd you remove the Radar number? It's not like it's confidential information. Posted by: rentzsch on November 5, 2003 2:14 PMSpeaking of FruitMenu problems... For some time now FruitMenu beta has been showing some System Preference panels twice in the submenu on one of my systems. Currently, these items are duplicated: .Mac Selecting either of the duplicates results in the panel opening correctly. I've sent Slava emails but have gotten no response. Is anyone else havin this problem? Also, does anyone have ideas about what might be causing it and how I might resolve it? -mono Posted by: monoclast on November 5, 2003 2:16 PMAny chance of getting the "fast user switching menu" functionality in FruitMenu? I *SO* want that damn menu to go away. I use it once a week and it takes up a good inch or two on my menubar (need to get a shorter name I suppose). Posted by: schwa on November 5, 2003 2:18 PMI'm not sure why DTS is claiming that invoking ScreenSaverEngine is the right way to launch. Its not and never has been the way they do it internally. When its launched that way the WindowServer doesn't notice the screensaver is already running and will reinvoke it when the user's screensaver timeout occurs. This leads to the "double" screensaver issue, where both fight to be front. Or at least that's the way it worked in Jaguar. To get around this I spent some time in gdb with the Keychain NSMenuExtra seeing how they invoked the saver. Its all a private API in the screensaver framework. Take a look at the source for SleepTight http://www.ragingmenace.com/software/sleeptight/index.html. I haven't tested it on Panther yet since Panther now includes the "lock at wake from sleep" functionality, but I suspect the API still works. Bas Posted by: Basilisk on November 5, 2003 5:16 PMActually, another feature for screen locking which is more secure than Screensaver has been suggested over at MacOSHints.com.. Please see - '10.3: Use a more secure screen lock alternative', here: http://www.macosxhints.com/article.php?story=20031031112407491#comments I'm beginning to agree with users who just want FUS (Fast User Switching) without the long user name clogging up the menubar. Maybe this is an op for FruitMenu? Just have 'Login Window...' without a user list, or a FM item called 'FUS' that lists the users and has 'Login Window...' - which I would -immediately- assign a hotkey to. ;) Posted by: Leo Marihart on November 6, 2003 2:10 AMi used to use a hotkey command to launch the screensaver. it always caused it to freeze when trying to exit the screensaver... ever since the first build of panther this has been a problem Posted by: paul on November 6, 2003 8:42 AMSteve, try the 3.2 beta that Slava posted. It's working just fine for me under 10.3, or at least I don't think it's related to the couple of kernel panic / screen freezes I've had. http://www.unsanity.org/archives/000266.php
Schwa wants Fast User Switching. Here's an interesting way to do it: http://www.macosxhints.com/article.php?story=20031102031045417 Perhaps that can help in implementing it in FruitMenu? Posted by: Avi Drissman on November 7, 2003 8:06 AMReal simple. Make a *.command file -- then make an alias to this file in FruitMenu Items and assign it a hotkey. Unfortunately there's a bug in FM Items in the current beta. :( Posted by: Leo of BORG on November 7, 2003 11:26 AMI'd like to pose a new suggestion and reiterate an old one. First, the old one: the ability to select icon size in the Apple menu would be wonderful. In particular, being able to customize it for each menu level would be great. (i.e. 64x64 for the top level, 48x48 for second level, etc.) I also assume that this would be easily migrated to contextual menus, though I myself am only concerned with the Apple menu. The new suggestion is this: it would be awesome to put a "Move To..." item in contextual menus, where clicking on it would open up a box to select a particular folder. Yes, I could use the "Move To..." submenu, but I never know where I might want to move something. Posted by: Scottish on November 10, 2003 7:59 PMI'm using FruitMenu 3.2b1 under Panther. I'm also using FruitMenu 3.2b1 under Panther, and I have Hide's CalculateSizeCM 1.2 installed as well. When I click on the "Calculate Size..." context menu nothing happens (it's supposed to popup a dialog which calculates/shows the size of the selected item). This worked like a charm with older versions of FruitMenu on Jaguar. You can find Hide's CalculateSizeCM here; http://www.pixture.com/macosx.php Hope this gets fixed as well... :) Posted by: Richard Hess on November 11, 2003 2:37 PMoops, forgot to mention that CalculateSizeCM works just fine if I disable haxies... :) Posted by: Richard Hess on November 11, 2003 5:00 PMEnabling the FruitMenu 3.2b1 context menu is actually disabling other context menu items. I use QuickImage and Terminal Here. I'll email it in as a bug report. I wish you guys would give some feedback on bug reports, though. Posted by: Ken on November 11, 2003 8:28 PMKeep comments on topic. If a comment is unrelated to this post, it may be removed or moderated. |

