> On Sep 15, 2015, at 4:40 PM, Thierry Goubier <thierry.goub...@gmail.com> > wrote: > > Hi Martin, Skip, > > it makes sense, sort of. > > ClassReorganized could be handled already by just either discarding whatever > cache you would have on the protocols of the class (for example, in a > browser) or comparing the new class organisation with the old one.
As far as I know, you can’t compare to the old class organization because it is already changed to the new one.. > You may be pointing to, however, another issue: ClassReorganized not carrying > enough information (i.e. not the old set of protocols). Yes… it only has the class which has been affected. No way to compare it. > I'm not sure your ProtocolRenamed solves that. While it may not solve the problem of ClassReorganized lacking information, it does give extra information as to what happened. Right now you simply don’t know when a protocol was renamed. > But it won't do much harm... Unless Nautilus overeacts and refresh itself 20 > times, that it :) If Nautilus does not subscribe to ProtocolRenamed then nothing happens, no? I am willing to create an issue, propose a slice, etc. Thanks for your reply :) PS: There’s something else related to System-Announcements, namely that when I rename a category I get no CategoryRenamed announcement. I will send an e-mail about that later.
