Am Donnerstag, den 15.09.2005, 10:08 +0200 schrieb Alexander Larsson: > On Thu, 2005-09-15 at 01:28 +0000, Nate Nielsen wrote: > > Alexander Larsson wrote: > > > The real GnomeVFSVolumeManager runs in the gnome-vfs daemon, and > > > GnomeVFSVolumeManager objects in actual gnome-vfs apps are just copies > > > of the daemon objects that are sent over from the daemon. You can't just > > > change your local copy of the volume and expect the daemon copy and all > > > other copies to change. > > > > When I change the GConf key corresponding to a 'Connected Server' (ie: > > /desktop/gnome/connected_servers) it seems to update all the various > > views of it. Or is this just cosmetic? > > Looking at it, it does seem to handle this, but by removing the old > volume and creating a new one. This might be good enough though... Yeah, the code is in a good shape, we do a good job at parsing for changed volumes. However, I think we should still use the same GnomeVFSVolume, since it will be way more simple for clients to keep the same object around rather than querying the monitor for the changed URI. This is feasible and shouldn't be much of a problem. The code is located at gnome-vfs-volume-monitor-daemon.c:update_connected_servers. We may want to add "uri", "icon" and "activation-uri" properties, so that clients can connect "notify::icon" and such. I've filed a bug report [1] and did some hacking. I think the API is straightforward and the implementation very simple. [1] http://bugzilla.gnome.org/show_bug.cgi?id=316403 -- Christian Neumair <chris gnome-de org>
Attachment:
signature.asc
Description: This is a digitally signed message part