linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #07151
[Bug 1132332] Re: The transition to STATE_DATA is not marked when using setDataMode
To the people needing this in the future:
Fixing this caused a lot of crashes on the server I suppose because of code expecting STATE_NORMAL to happen only once.
As done with Bloom plugin it's easier to add instead a specific
notification when a particular instance of this happens (as of now this
only happens with the BLOM extension IIRC).
** Changed in: adchpp
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/1132332
Title:
The transition to STATE_DATA is not marked when using setDataMode
Status in ADCH++:
Won't Fix
Bug description:
When using the setDataMode function the client won't change to the
STATE_DATA state and thus scripts will not be noticed of the state
change, similarly the transition back to STATE_NORMAL won't be
notified.
The main reason why this is not a trivial change is that a lot of our
scripts do expect that there will only be a single transition to
STATE_NORMAL in the whole life of the connection (see for example
motd.lua or history.lua) so events that should be triggered once may
get triggered various times instead.
No patch for this yet, sorry.
To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/1132332/+subscriptions
References