Lime 2.8.0 Assets issues

er453r · December 9, 2015, 9:24am

If I use Lime 2.8.0 in my project on html5 target I get following errors (lime 2.7.0 works fine, and surprisingly PiratePig works ok with 2.8.0… any ideas? ):

Export/html5/haxe/DefaultAssetLibrary.hx:1184: characters 14-26 : Null<lime.net.URLLoader> has no      field bytes
Export/html5/haxe/DefaultAssetLibrary.hx:1322: characters 14-26 : Null<lime.net.URLLoader> has no field bytes
Export/html5/haxe/DefaultAssetLibrary.hx:1482: characters 61-81 : lime.AssetCache has no field version
Export/html5/haxe/DefaultAssetLibrary.hx:1549: characters 37-57 : lime.AssetCache has no field version
Export/html5/haxe/DefaultAssetLibrary.hx:1641: characters 52-72 : lime.AssetCache has no field version
Export/html5/haxe/DefaultAssetLibrary.hx:1151: lines 1151-1202 : Field getBytes overloads parent class with different or incomplete type
Export/html5/haxe/DefaultAssetLibrary.hx:1151: lines 1151-1202 : id : String -> lime.utils.Bytes should   be id : String -> lime.utils.ByteArray
Export/html5/haxe/DefaultAssetLibrary.hx:1151: lines 1151-1202 : lime.utils.Bytes should be lime.utils.ByteArray
Export/html5/haxe/DefaultAssetLibrary.hx:1440: lines 1440-1498 : Field loadBytes overloads parent class with different or incomplete type
Export/html5/haxe/DefaultAssetLibrary.hx:1440: lines 1440-1498 : id : String -> lime.app.Future<lime.utils.Bytes> should be id : String -> lime.app.Future<lime.utils.ByteArray>
Export/html5/haxe/DefaultAssetLibrary.hx:1440: lines 1440-1498 : lime.app.Future<lime.utils.Bytes> should be lime.app.Future<lime.utils.ByteArray>
Export/html5/haxe/DefaultAssetLibrary.hx:1440: lines 1440-1498 : Type parameters are invariant
Export/html5/haxe/DefaultAssetLibrary.hx:1440: lines 1440-1498 : lime.utils.Bytes should be lime.utils.ByteArray

ibilon · December 9, 2015, 1:47pm

ByteArray was changed,
but lime and openfl should be synced,
are you using the latest openfl version?

er453r · December 9, 2015, 2:06pm

Yes:

lime: 2.6.9 2.7.0 [2.8.0] 2.6.8
openfl: 3.4.0 [3.5.0]

But like I say, this happens only for my project, PiratePig example works good.

ibilon · December 9, 2015, 2:14pm

Oh,

did you try a clean build? openfl test html5 -clean (equivalent to deleting the output folder)

er453r · December 9, 2015, 2:30pm

Yes, that was the first thing I’ve tried

bubba_169 · December 9, 2015, 3:01pm

I get this with Neko - all internal Lime errors I think. It looks like not all issues with changing the ByteArray have been cleaned up.

C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/text/Font.hx:166: characters 15-29 : haxe.io.Bytes has no field getInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/text/Font.hx:167: characters 15-29 : haxe.io.Bytes has no field getInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/text/Font.hx:168: characters 16-30 : haxe.io.Bytes has no field getInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/text/Font.hx:169: characters 11-25 : haxe.io.Bytes has no field getInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/text/Font.hx:170: characters 11-25 : haxe.io.Bytes has no field getInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:60: characters 3-16 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:61: characters 3-17 : haxe.io.Bytes has no field setUInt16
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:62: characters 3-17 : haxe.io.Bytes has no field setUInt16
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:63: characters 3-16 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:67: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:68: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:69: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:70: characters 2-16 : haxe.io.Bytes has no field setUInt16
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:71: characters 2-16 : haxe.io.Bytes has no field setUInt16
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:72: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:73: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:74: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:75: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:76: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:77: characters 2-15 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:81: characters 3-16 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:82: characters 3-16 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:83: characters 3-16 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/graphics/format/BMP.hx:84: characters 3-16 : haxe.io.Bytes has no field setInt32
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:1178: characters 71-75 : Array<{ type : haxe.macro.ComplexType, opt : Bool, name : String }> should be Array<haxe.macro.FunctionArg>
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:1178: characters 71-75 : Type parameters are invariant
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:1178: characters 71-75 : { type : haxe.macro.ComplexType, opt : Bool, name : String } should be haxe.macro.FunctionArg
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:1178: characters 71-75 : { type : haxe.macro.ComplexType, opt : Bool, name : String } should be { ?value : Null<haxe.macro.Expr>, type : Null<haxe.macro.ComplexType>, ?opt : Bool, name : String }
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:1178: characters 71-75 : { type : haxe.macro.ComplexType, opt : Bool, name : String } has no field value
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/text/Font.hx:25: characters 2-11 : Build failure
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:37: lines 37-883 : Defined in this class
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/net/curl/CURLEasy.hx:8: characters 2-7 : Build failure
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:37: lines 37-883 : Defined in this class
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/net/curl/CURL.hx:5: characters 2-7 : Build failure
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/Assets.hx:37: lines 37-883 : Defined in this class
C:/HaxeToolkit/haxe/lib/lime/2,8,0/lime/audio/AudioSource.hx:30: characters 25-49 : Unknown<0> cannot be constructed

ibilon · December 9, 2015, 6:55pm

@bubba_169 your errors come from haxe.io.Bytes, do you have haxe 3.2?

singmajesty · December 9, 2015, 8:23pm

Yeah, what version of Haxe are you guys using?

Pizzamakesgames · December 9, 2015, 8:44pm

Lime update 2.8.0 has been causing this afaik. There’s a thread discussing the same issue over at the HaxeFlixel forums: http://haxeflixel.com/forum/?place=msg%2Fhaxeflixel%2FA0ZUORP5NDM%2FYaxnGH0wDAAJ

Using all the latest dev branches,Haxe compiler 3.3.0 (git build development @ acc52ab), openfl 3.5.0…

downgrading lime to 2.7.0 fixes everything for me, though I would like to use the latest update.

By the way, what was that about ByteArray? I’ve been trying to compile with -Dnext to try and solve an openfl related issue but I didn’t even try to follow this error coming up: …/haxe/lib/openfl/3,5,0/openfl/utils/ByteArray.hx:7: characters 7-23 : Type not found : lime.utils.Bytes
Are you saying there might be an easy fix?

bubba_169 · December 9, 2015, 9:58pm

Just tried on another computer that’s running 3.2.0 and it compiles fine now but I have other issues. Will start another topic.

singmajesty · December 9, 2015, 10:21pm

Errors like “haxe.io.Bytes has no field…” suggest an old version of Haxe to me. The error “Type not found: lime.utils.Bytes” suggests an old version of Lime with a new version of OpenFL?

We do not test against development versions of the Haxe compiler, but if there are specific issues that appear there, then we can look at a solution

Pizzamakesgames · December 10, 2015, 12:15am

Thank you, I’ll look into it with the new information. Think that’s as far as we wanna go off topic in a thread that’s effectively over.

singmajesty · December 10, 2015, 12:17am

Please feel free to post again with any issues that come up!

er453r · December 10, 2015, 7:08am

I’m using 3.2.1, on linux x64

singmajesty · December 10, 2015, 7:41am

It seems odd, like lime.utils.Bytes should be lime.utils.ByteArray does not make sense – there is no lime.utils.ByteArray in Lime 2.8. Is there some way/reason your DefaultAssetLibrary could be mismatched? A custom template?

er453r · December 10, 2015, 7:55am

I’m extensively using haxeui, but I don’t know if this is the culprit…

IanHarrigan1982 · December 10, 2015, 8:27am

It might be because haxeui locks you into a specific version of lime/openfl… If you remove the versions in haxeui’s include.xml, does that fix the problem?

IanHarrigan1982 · December 10, 2015, 8:52am

Just upgraded openfl to latest haxelib and getting issues in haxeui1 and 2… will investigate now.

IanHarrigan1982 · December 10, 2015, 8:56am

Ok, so if you use latest haxeui in haxelib (1.8.2) it should be fixed. It was because of the include.xml.

er453r · December 10, 2015, 9:37am

It was it!

My project works with this setup (and you can see my previous…):

actuate: [1.8.6]
box2d: [1.2.3]
haxeui: 1.7.20 [1.8.2]
hscript: [2.0.5]
hxcpp: [3.2.193]
layout: [1.2.1]
lime-samples: [2.6.0]
lime: [2.8.1] 2.7.0
openfl-samples: [3.3.1]
openfl: [3.5.1] 3.4.0
swf: 2.1.3 [2.1.5]