Closed GoogleCodeExporter closed 8 years ago
Although I also tested, it was correctly set as 0.
Original comment by kenz0.sa...@gmail.com
on 18 Oct 2009 at 6:02
There was a timing problem. If the skin deactivated itself immediately on the
first
update it was marked as active after the deactivation was already handled. This
is
fixed now in r283.
Original comment by kimmo.pekkola
on 18 Oct 2009 at 1:35
Original issue reported on code.google.com by
Kae...@gmail.com
on 17 Oct 2009 at 5:38