yishayw commented on issue #1095:
URL: https://github.com/apache/royale-asjs/issues/1095#issuecomment-805544448


   Thanks for reporting this. mx:Repeater is not implemented. I would suggest 
to rewrite that part of your code for now.
   ________________________________
   From: dhendargo1 ***@***.***>
   Sent: Tuesday, March 23, 2021 7:47 PM
   To: apache/royale-asjs ***@***.***>
   Cc: Subscribed ***@***.***>
   Subject: Re: [apache/royale-asjs] Having <mx:Repeater /> causes compiler 
Error: Unable to resolve resource bundle 'core' (#1095)
   
   
   Update: using build 3047, I am getting the following stack trace:
   src/RepeaterBug.mxml 
c:\development\royale-bugs\RepeaterBug\src\RepeaterBug.mxml line 9 column 1 
Error: Internal error in ASBlockWalker subsystem, when generating code for: 
c:\development\royale-bugs\RepeaterBug\src\RepeaterBug.mxml line 9 column 1: 
java.lang.IllegalArgumentException: No handler specified for nodes of type 
'MXMLRepeater' at 
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:200)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
 at 
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitArray(MXMLRoyaleEmitter.java:3174)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.visitArray(MXMLBlockWalker.java:305)
 at 
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:77)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
 at org.apache.royale.compiler.internal.
 
codegen.mxml.royale.MXMLRoyaleEmitter.emitPropertySpecifier(MXMLRoyaleEmitter.java:3086)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.visitPropertySpecifier(MXMLBlockWalker.java:273)
 at 
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:111)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
 at 
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitDocument(MXMLRoyaleEmitter.java:877)
 at 
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleBlockWalker.visitDocument(MXMLRoyaleBlockWalker.java:69)
 at 
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:89)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
 at 
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleBlockWalker.visitFile(MXMLRoyaleBlockWalker.java:61)
 at org.apache.royale.compiler.
 internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:95) at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.visitCompilationUnit(MXMLBlockWalker.java:187)
 at 
org.apache.royale.compiler.internal.codegen.mxml.MXMLWriter.writeTo(MXMLWriter.java:69)
 at 
org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:411)
 at 
org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:259)
 at 
org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:216)
 at org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:363) at 
org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:298) at 
org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:256) 
at org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:238)
   
   —
   You are receiving this because you are subscribed to this thread.
   Reply to this email directly, view it on 
GitHub<https://github.com/apache/royale-asjs/issues/1095#issuecomment-805186503>,
 or 
unsubscribe<https://github.com/notifications/unsubscribe-auth/AAQBE7JO57J2OVHLJII2IV3TFDV6NANCNFSM4ZVYAYUA>.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to