How to prevent the user from clicking 'Test' in Screen Savers (Was: ScreenSaverView gets instantiated several times)
Thanks a lot for all the responses, and sorry for bothering you again with this. The problem I'm having is the following: is there an elegant way to prevent the user from clicking the 'Test' button in the Screen Savers panel in System Preferences? The reason why I'm asking: when the user changes the configuration in my screen saver, I start a Spotlight query that could take up to 30 seconds (about 10 seconds for the initial phase of the search itself, plus 20 seconds for retrieveing the results from the query). The results of that query then change what the screensaver renders. Therefore, I would like to give the user some feedback that the query is still in progress *AND* I would like to prevent the user from clicking that 'Test' button in System Preferences' Screensaver pane. Right now I'm using an asynchronous NSMetadataQuery, which seems to work, except that the only way to prevent the user from clicking that 'Test' button I found was to keep the configuration sheet up until the search has completely finished. IMHO, this doesn't look very elegant ;-/ Any ideas will be highly appreciated. Best regards, Gabriel. smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How to prevent the user from clicking 'Test' in Screen Savers (Was: ScreenSaverView gets instantiated several times)
Why not just fake it ... in other words ... since it's a test, just supply some generic data for the screen saver to display. Then, when they truly activate it, you provide the real data. Seems that's what others have done, that i've experienced. Not knowing for sure or not, but i believe you can determine whether the button was clicked to test or otherwise. Jack On Oct 5, 2009, at 11:45 AM, Gabriel Zachmann wrote: Thanks a lot for all the responses, and sorry for bothering you again with this. The problem I'm having is the following: is there an elegant way to prevent the user from clicking the 'Test' button in the Screen Savers panel in System Preferences? The reason why I'm asking: when the user changes the configuration in my screen saver, I start a Spotlight query that could take up to 30 seconds (about 10 seconds for the initial phase of the search itself, plus 20 seconds for retrieveing the results from the query). The results of that query then change what the screensaver renders. Therefore, I would like to give the user some feedback that the query is still in progress *AND* I would like to prevent the user from clicking that 'Test' button in System Preferences' Screensaver pane. Right now I'm using an asynchronous NSMetadataQuery, which seems to work, except that the only way to prevent the user from clicking that 'Test' button I found was to keep the configuration sheet up until the search has completely finished. IMHO, this doesn't look very elegant ;-/ Any ideas will be highly appreciated. Best regards, Gabriel. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/intrntmn%40aol.com This email sent to intrn...@aol.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How to prevent the user from clicking 'Test' in Screen Savers (Was: ScreenSaverView gets instantiated several times)
On Oct 5, 2009, at 10:45 AM, Gabriel Zachmann wrote: The problem I'm having is the following: is there an elegant way to prevent the user from clicking the 'Test' button in the Screen Savers panel in System Preferences? The reason why I'm asking: when the user changes the configuration in my screen saver, I start a Spotlight query that could take up to 30 seconds (about 10 seconds for the initial phase of the search itself, plus 20 seconds for retrieveing the results from the query). The results of that query then change what the screensaver renders. Therefore, I would like to give the user some feedback that the query is still in progress *AND* I would like to prevent the user from clicking that 'Test' button in System Preferences' Screensaver pane. Right now I'm using an asynchronous NSMetadataQuery, which seems to work, except that the only way to prevent the user from clicking that 'Test' button I found was to keep the configuration sheet up until the search has completely finished. I don't know of a way to disable the Test button, but I wonder if that's the right approach. When the user changes the configuration of your screen saver (assuming this is done by selecting the Options button and changing the settings presented), what do you show in the Preview pane? Perhaps displaying some static view with a progress indicator in your screen saver view would be a better option? - Mike ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How to prevent the user from clicking 'Test' in Screen Savers (Was: ScreenSaverView gets instantiated several times)
This is a much better approach IMO. If your user is trying out a bunch of options to find a particular combination that works for them, and the machine goes away for ~30 secs each time they test a new change, the'll get pretty irriated with your screen saver pretty quickly. Showing the results of the changed config using faked data that has no loading delay, will give a much more satisfactory experience. paulm On 6/10/2009, at 5:08 AM, Jack Carbaugh wrote: Why not just fake it ... in other words ... since it's a test, just supply some generic data for the screen saver to display. Then, when they truly activate it, you provide the real data. Seems that's what others have done, that i've experienced. Not knowing for sure or not, but i believe you can determine whether the button was clicked to test or otherwise. Jack On Oct 5, 2009, at 11:45 AM, Gabriel Zachmann wrote: Thanks a lot for all the responses, and sorry for bothering you again with this. The problem I'm having is the following: is there an elegant way to prevent the user from clicking the 'Test' button in the Screen Savers panel in System Preferences? The reason why I'm asking: when the user changes the configuration in my screen saver, I start a Spotlight query that could take up to 30 seconds (about 10 seconds for the initial phase of the search itself, plus 20 seconds for retrieveing the results from the query). The results of that query then change what the screensaver renders. Therefore, I would like to give the user some feedback that the query is still in progress *AND* I would like to prevent the user from clicking that 'Test' button in System Preferences' Screensaver pane. Right now I'm using an asynchronous NSMetadataQuery, which seems to work, except that the only way to prevent the user from clicking that 'Test' button I found was to keep the configuration sheet up until the search has completely finished. IMHO, this doesn't look very elegant ;-/ Any ideas will be highly appreciated. Best regards, Gabriel. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/intrntmn%40aol.com This email sent to intrn...@aol.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/list%40no-tek.com This email sent to l...@no-tek.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
