There is one thing to note about that dialog. If you compile a development version, it will show everything unassigned, even if types *are* indeed assigned (to the other version). Also, if you enable automatic assoc checking with two different copies of Code::Blocks, they will be fighting over the associations on every application start (this has always been the case).
That "problem" arises because the application does not only check whether or not a type is generally assigned, but also whether it is assigned with itself.
I was uncertain for quite a while whether this should be "fixed", and whether this is actually a bug or a misfeature. Finally, I settled it as "correct behaviour". Not only because it is a lot less work :lol: but also because it is really correct. You normally don't have two different versions of Code::Blocks running on the same machine, and if you install a new version, you're normally interested mainly in that one, and having your files open in the wrong version although everything looks OK in the config dialog is a big turn-off.
If you really do have two versions regularly, you are either a developer (so you know about the issue) or you are doing something wrong.
