This seems Not Right (TM). If you find a reproducible case of this,
please let me know -- I'm not sure how that would happen. However, I
HAVE seen the lingering error if you change a class or API file that
WOD files do not auto-update, so you need to just touch the file and
resave if to kick off a WOD rebuild. This is kind of a tricky
problem to fix. It may be that if any API or Java file changes, then
just automatically force a rebuild of any WOD file that has an error.
ms
On Sep 19, 2006, at 5:55 PM, Stephen R. Smith wrote:
> Hi Markus,
>
> I’ve noticed a number of times that this occurs, and you can fix it
> by reordering the bindings in the .wod – compare the troublesome
> one with another of the same type and see how the bindings are
> ordered. I get this when I’ve copied elements from layout view in
> WOBuilder and pasted them back in, not all the time, but often
> enough to have figured out how to make the error flags go away.
>
> Cheers,
> :Steve
>
>
> --
> Stephen R. Smith Tel: 905.633.9178
> Senior Developer Fax: 905.634.1064
> Align Software Inc. Email: ssmit..lignsoft.com
> WWW: http://www.alignsoft.com/
> WWW: http://365tomorrows.com/
>
This archive was generated by hypermail 2.0.0 : Tue Sep 19 2006 - 19:27:19 EDT