Hi all,
  [weaver] now contains code to handle field references in blueprinted
methods; however, the handling of non-public fields for some reason yields
bytecode that throws VerifyErrors at runtime.  Thus this code path has been
disabled and a warning issued when non-public fields are referenced.  I
think we are nearing the phase of proposing a vote to move [weaver] to a
proper component and hopefully to make a release shortly after.  Does
anyone have any specific thoughts on things that need to be addressed prior
to either of these goals?

Thanks,
Matt

Reply via email to