An explanation for this would be really helpful. It pollutes my debug console big time and I don't like it.
Adobe staff, please respond!
Adobe, please respond
I found a solution to this. There is a compiler flag that you can set to ignore these errors.
See this link for a summary, but -compiler.show-binding-warnings is the one you want
Not to be rude, but even if it did work, disabling all your binding warnings to hide one false warning is not a solution at all. I've never seen this one but it looks like a bug to me.
The issue of bogus warnings (particularly from design mode) in FB has a long history. And really, I wish some more attention would be paid to these, as it causes people to miss real warnings (by polluting and obscuring your console or problems tab) or to disable a whole class of warnings which may have otherwise prevented the creation of a bug. Warnings aren't there to be ignored.
Yes, well spoken. Although at times you get so desperate that you start looking for less-optimal solutions. This "multiple describe type" issue has been posted in this forum several times, never receiving a response:
Try posting over at http://bugs.adobe.com where the engineers working on this stuff can actually see your posts. I think these forums are mostly for user to user discussions. To get a bug fix/feature request, you must provide a way to reproduce your error. Paste in exactly what your compiler flags look like and the warnings you get. Also, the lines of code that cause the warnings. It may sound like a lot, but thats the only way they can work on it.
I use ChangeWatcher to set some bindings manually and I've had success with the compiler flags. Maybe what you're doing is another kind of compiler warning? After you open a bug, post a reference to the bug number and we can watch / vote for you.