Clicking the "set all to" button when a few rights are already specified toggles the rights in that column to "all enabled". I think it should be the other way around and should disable them all on the first click.
Imagine you have the following scenario: You want to remove all write access for a certain module role. The user has "read" rights to only some attributes, but not all of them. You notice there's a nice "set all to" button - great! You should be able to toggle off all write rights at once without affecting your read rights, right?
Unfortunately, that's not how it currently works. If in the write column, you click the "set all to" and it enables every "write" checkbox, it also automatically enables all the "read" checkboxes in the column on the left (as you can't have write access without read access). However, if you then click the "set all to" toggle again (because you wanted to remove all the access rights), the write column is empty, but the read column is still fully enabled instead of whatever settings you had it to first.
Reversing the operation so that "set all to" always toggles the whole column off first would fix this problem, and a single click on the "write" column would have no effects on the "read" column.