annotate src/dbus-service-end.xml @ 11261:b53606580f68

[gaim-migrate @ 13439] Patch #1226486 from Levi Bard Fixes bug #1224178 If you change the topic in a chat room and that topic change is rejected, the topic field is wrong -- it shows the new topic even thought it didn't get set. This patch resets the GUI's topic immediately when you hit enter. Then, if the topic change is successful, the server will echo the topic change back to us and we'll update the GUI to the new topic. The only question is, does the server always echo the topic back to us? From the core's point of view, I'm ready to assume yes. It's the case for both IRC and Jabber*. If someone could test changing a topic in SILC or Zephyr, that'd be great. If servers using those protocols do not echo the topic back, the prpl will have to fake it as appropriate. * I didn't actually test on Jabber, but Nathan said the server will echo the topic change back. If it's broken, let me know. committer: Tailor Script <[e-mail]>

  </interface>
  

  <interface name="org.freedesktop.DBus.Properties">
    <!-- We implement properties ourselves rather than relying on
	 GObject property access.  This is because currently in gaim
	 we have one GObject that represents many dbus objects such as
	 buddies, accounts, etc.  Not for long! -->

<!--      <method name="Get"> > -->
<!--        <arg type="s" name="interface_name" />  -->
<!--        <arg type="s" name="property_name" />  -->
<!--        <arg type="v" name="value" direction="out" />  -->
<!--      </method>  -->
   </interface> 
</node>