We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joshua Granick There's been some confusion around <haxedef /> and <set />
<haxedef />
<set />
<haxedef /> affects Haxe only
<set /> affects project parsing only (edited)
Originally -D was the same as <set />, but for convenience, became synonymous with setting both
Lime recently got a new tag called <define /> that does the same as having both tags
<define />
So give... oh, wait
Do you have <haxelib name="hxtelemetry" /> in before OpenFL or Lime?
<haxelib name="hxtelemetry" />
If you do, that should be all that's required, I think
I think that's how it's designed to work
Jeff Ward Thanks for the info. Here's the old testcase project.xml: https://github.com/jcward/hxtelemetry/blob/master/test/DisplayingABitmap/project.xml#L28-L30 (edited)
So it sounds like, if I put <haxelib name="hxtelemetry" /> before the <haxelib name="openfl" />, the tools might take care of the rest?
<haxelib name="openfl" />
I want to update this and the User Guide section of hxscout.com
Joshua Granick Yeah, give it a try. I think the goal was to make it as automatic as possible
Figured, if you include the telemetry lib, you want telemetry
though there might also have been an option to do -Dtelemetry and have the lib included automatically
yeah
https://github.com/openfl/openfl/blob/develop/include.xml#L49-L54 github.com openfl/include.xml at develop · openfl/openfl · GitHub openfl - The "Open Flash Library" for fast 2D development
<section if="telemetry || advanced-telemetry"> <haxelib name="hxtelemetry" /> <config:hxtelemetry allocations="true" host="localhost" /> </section>
so if you -Dtelemetry or <set /> or <define /> telemetry
then it should include hxtelemetry
(-Dtelemetry also works for the Flash target)
so -Dtelemetry or <define name="telemetry" /> is perhaps best
-Dtelemetry
<define name="telemetry" />
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Joshua Granick
There's been some confusion around
<haxedef />
and<set />
<haxedef />
affects Haxe only<set />
affects project parsing only (edited)Originally -D was the same as
<set />
, but for convenience, became synonymous with setting bothLime recently got a new tag called
<define />
that does the same as having both tagsSo give... oh, wait
Do you have
<haxelib name="hxtelemetry" />
in before OpenFL or Lime?If you do, that should be all that's required, I think
I think that's how it's designed to work
Jeff Ward
Thanks for the info. Here's the old testcase project.xml: https://github.com/jcward/hxtelemetry/blob/master/test/DisplayingABitmap/project.xml#L28-L30 (edited)
So it sounds like, if I put
<haxelib name="hxtelemetry" />
before the<haxelib name="openfl" />
, the tools might take care of the rest?I want to update this and the User Guide section of hxscout.com
Joshua Granick
Yeah, give it a try. I think the goal was to make it as automatic as possible
Figured, if you include the telemetry lib, you want telemetry
though there might also have been an option to do -Dtelemetry and have the lib included automatically
yeah
https://github.com/openfl/openfl/blob/develop/include.xml#L49-L54
github.com
openfl/include.xml at develop · openfl/openfl · GitHub
openfl - The "Open Flash Library" for fast 2D development
so if you -Dtelemetry or
<set />
or<define />
telemetrythen it should include hxtelemetry
(-Dtelemetry also works for the Flash target)
so
-Dtelemetry
or<define name="telemetry" />
is perhaps bestThe text was updated successfully, but these errors were encountered: