No problem... its just not necessary, I think you'll find most users are using the 'latest post' view, so will see posts across all categories. (Ive closed the previous one. and deleted the challenges one, as it had no replies on it)
this was my suggestion in the previous version of this post.
can I just make one small point on the MI objects/modules that i created.
Id recommend for this release to use 'as is', and let me know if there are any minor(*) changes needed,
(*) I dont have much time for doing anything other than bug fixes though.
I would not recommend others creating variations for two reasons:
a) you can't edit the MI code, as its in the firmware - so this means theres not much you can do, over whats already exposed. (see this thread for more details)
b) Im hoping/planning for the next release to remove the MI code from the firmware, to remove the above restriction.
this WILL break any objects which try to use MI code.
of course, I will fix this for the my factory objects, so user's patches using these will not be affected - but I cannot make any guarantees that 'derivative objects' will be easy to fix... the MI code base will be different, by how much I cant say at the moment, but obviously want to keep my options open.
so, please experiment/play with these objects in 1.0.12 and provide feedback, its all useful... but just wait till the next release to create derivatives (where it will be much easer/controlled, assuming my current experiments work )