-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
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
Attempt to call field 'rgba' a nil value #6
Comments
Hey, I just hit and fixed the exact same issue. I used this version of lume and everything worked: https://raw.githubusercontent.com/rxi/lume/da0d1bbae7be15f7dd4c26068b3df16a707f47fb/lume.lua |
I just pushed a commit (110d66a) — let me know if this fixes the problem. Thanks! |
Oh great, I'll check it out. Would be great if this really works 'cos it seemed what I've been looking for for some time. |
Hmm not it doesn't fix the issue for me. In fact I think that's the version of Lume I was using too which fixed the RGBA error but now I get the error: "If you fix the problem and update the file the program will resume". This error only occurs with certain changes but there is no error if I open a new love instance with this change in place. Also with other changes I noticed it doesn't really reload properly. If I change the resolution in conf.lua for example it says lurker is hotswapping conf.lua but nothing changes...but the screen size should change completely. If I open a new love instance of course the change is made in full. Other changes change things a bit...but not everything. Not sure why it's like that. So it works absolutely flawless for you? |
Does this still work? I noticed it's quite old. Sometimes it updates ok but sometimes I get the error 'attempt to call field RGBA'..I noticed this function is missing from the latest version of lume. I found the function in an older version of lume but adding it back in doesn't help. It just comes up with a different error - "If you fix the problem and update the file the program will resume"
There's no errors in my code though, if I open a new window it loads fine so there isn't actually any error but lurker doesn't seem to like something.
The text was updated successfully, but these errors were encountered: