Changeset 9854278 for owl.c


Ignore:
Timestamp:
Dec 23, 2003, 3:22:21 AM (17 years ago)
Author:
James M. Kretchmar <kretch@mit.edu>
Branches:
master, barnowl_perlaim, debian, owl, release-1.4, release-1.5, release-1.6, release-1.7, release-1.8, release-1.9
Children:
e9f239b
Parents:
952bb256
Message:
First pass at AIM away messages.  It is a little different from
  what most clients seem to do, in that an away reply is sent for
  each message received.  Most clients only reply to the first one
  per away-session.  Also, it's completely tied to the zaway
  functions, it should probably be separated out into aaway
  functions with a new "away" function that will get everything.
  Loop detection stuff should work and has been tested, but I'm
  not completely sure I did this right ... so odd behavior should
  be reported.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • owl.c

    r5a95b69 r9854278  
    472472
    473473      /* do we need to autoreply? */
    474       if (owl_global_is_zaway(&g)) {
     474      if (owl_global_is_zaway(&g) && !owl_message_get_attribute_value(m, "isauto")) {
    475475        if (owl_message_is_type_zephyr(m)) {
    476476          owl_zephyr_zaway(m);
    477477        } else if (owl_message_is_type_aim(m)) {
    478           /* can't do this, there's no mechanism not to start a loop */
    479           /* owl_aim_send_im(owl_message_get_sender(m), owl_global_get_zaway_msg(&g)); */
     478          owl_function_send_aimawymsg(owl_message_get_sender(m), owl_global_get_zaway_msg(&g));
    480479        }
    481480      }
Note: See TracChangeset for help on using the changeset viewer.