Menu

#4 dccassist refresh/display error

open
None
5
2004-05-04
2004-05-04
No

there are 2 transfers from the same bot and dccassist
displays these transfers alternately in one row instead
of two rows. and the row where the second transfer
should be displayed is not being refreshed.
i had this problem too when i had 2 transfers from 2
different bots. the first transfer has been displayed
correctly but the other hasn't been refreshed/displayed.

Discussion

  • Red Krane

    Red Krane - 2004-05-04

    Logged In: YES
    user_id=644528

    I am aware of the same bot, 2 transfers problem, and have
    been working on it for a little while. It should be fixed
    by version 1.9. The other problem of 2 transfers from 2
    different bots I have yet to see. Were the 2 transfers of
    the same file name? or pack number? Any pertinent info will
    help me fix it. Thanks for all your input, ptroll.

     
  • Philippe Trolliet

    Logged In: YES
    user_id=839062

    once i had 2 transfers from 2 different bots with a
    different file name and another time i had 2 transfers (2
    different files) from the same bot.
    is it not a problem with the bot, if it allows 2 transfers?

     
  • Philippe Trolliet

    Logged In: YES
    user_id=839062

    there is another problem. in xchat there is the file receive
    window. i had a xdcc transfer and aborted it. in dccassist i
    started the download again (same bot, same file, same
    network and same channel) but hadn't deleted the old
    transfer in the file receive window in xchat. then it
    displayed alternately the old aborted transfer and the new
    resumed transfer.

     
  • Philippe Trolliet

    Logged In: YES
    user_id=839062

    ok, now i deleted the aborted transfer from the file receive
    list in xchat and it still continues to display them
    alternately.

     
  • Red Krane

    Red Krane - 2004-05-06

    Logged In: YES
    user_id=644528

    Ah ptroll, my favorite user. Thanks again for all the bugs,
    I am working diligently to fix them.

     

Log in to post a comment.

MongoDB Logo MongoDB