On Nov 21, 2005, at 2:50 PM, Rowan Christmas wrote:
I would think that you wouldn't want the widget to actaully quit.
But my widget has a back-end that may be modified at a low level by
another process, and if this happens, then I want all instances of
it to quit... Otherwise, if it stays open, then it will be unstable
at worst and unusable at best. Re-launching won't work, because the
widget will most likely be an older version that doesn't support
the new back-end.
So the goal is that there is a back end which can get updated, and
you want all Widgets using the old back end to go away?
How about using the NSDistributedNotificationCenter to broadcast a
notification that all your Widget plugins were listening to, to let
them know that the backend has gone away, and then the Widget can
change it's state to the rough equivalent of a "zombie" state -
displaying information telling the user that they need to close that
Widget and update to the new Widget (and if they try to launch
another copy of the old version, there will be versioning code
between the plugin and the backend that causes the same thing)
That way the user will know that something is going on, they don't
just loose those widgets.
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
Widgetarium | the quickest path to widgets
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Dashboard-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/dashboard-dev/email@hidden
