What steps will reproduce the problem?
1. Receive more than one message in flashing notification timeframe.
2. A good way to see bug in action with greater likelihood is increase flashing
duration.
What is the expected output? What do you see instead?
I expect the flashing to leave the triggered light where it was originally. To
explain better- if scroll lock is off before flash, it should be off after
flash. However, when receiving concurrent messages in flash duration, it can
sometimes screw up the internal timing of the plugin, resulting in the
triggered light ending up opposite of what it was.
What version of the product are you using? On what operating system?
Capsnot-1.0, Pidgin 2.10.9, and Windows 7 x64 Professional.
Original issue reported on code.google.com by metallic...@gmail.com on 22 Jun 2014 at 7:31
Original issue reported on code.google.com by
metallic...@gmail.comon 22 Jun 2014 at 7:31