Nevermind, since you could get the previous state this is really easy to fix.
** Patch added: "Patch 1/2 check the previous state to ignore transitions coming from the DATA state" https://bugs.launchpad.net/adchpp/+bug/1132332/+attachment/3544135/+files/check_data_state.patch -- 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++: New 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 _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
