openfl / robotlegs Goto Github PK

Signal1 and Signal2 dispatch values are not being injection into commands.
This is using the SignalCommandMapExtension.

Hey @TomByrne

I'm getting the following error using targeting HTML5 with the latest Robotlegs and Starling 2.4.

IndexData.hx:73 Uncaught ReferenceError: openfl is not defined
    at IndexData.hx:73
    at IndexData.hx:73
    at ViewConfig.hx:21
EnterFrame.hx:39 Uncaught TypeError: Cannot read property 'addEventListener' of null
    at Function.mantle_time_EnterFrame.OnRunningChange (EnterFrame.hx:39)
    at EnterFrame.hx:30
    at haxe_Timer.t.run (Timer.hx:145)
    at Timer.hx:71

Is this a combo that you've tried lately? I haven't been able to isolate what is causing the issue, but there is a good chance it has something to do with the Macro DescribedType stuff.

other targets seem to work fine. (AIR, Flash, Electron)

This is really strange on its own, but it also seems to be incompatible with the API of the actual openfl.events.Event included with OpenFL.

https://github.com/openfl/robotlegs/blob/master/src/openfl/events/Event.hx

What's the reason for redefining the existing Event class? Is there some really old version of OpenFL that didn't have events yet? That seems unlikely...

haxe 3 error:
DescribeTypeRTTIReflector
Type not found : haxe.xml.Access

This was possible in RobotLegs 1. I couldn't find any docs in the Robotlegs' website. I am converting my project which has robotlegs 1 in it. There are tons of events dispatched from models. What would be the easiest way to convert? Is there any method for dispatching from Models (like extending from another class) or is it better to convert all dispatches in models to Signals.

Thanks.

I'd like to add CI and NPM builds to this repo, in line with the OpenFL and Starling repos.
I'm just having a little trouble working out how it actually works in those libraries.

I can see the CircleCI config, which seems to just be for docs.
I can also see the Travis config, which sets up a build environment, runs unit tests and builds js/ts version.
What I can't see is where it runs npm publish.
@jgranick, are you able to point me in the right direction?