Skip to content
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

@Callback not available in-Game #1006

Closed
KJA1582 opened this issue Apr 2, 2015 · 10 comments
Closed

@Callback not available in-Game #1006

KJA1582 opened this issue Apr 2, 2015 · 10 comments

Comments

@KJA1582
Copy link
Contributor

KJA1582 commented Apr 2, 2015

http://pastebin.com/xpsYcmn5

It gets initialized just fine, but I can't access the @callback in-game.

@fnuecke
Copy link
Member

fnuecke commented Apr 2, 2015

You probably aren't registering the driver.

Also, please use the IRC channel or forums for support, the issue tracker is meant for bug reports and feature discussions.

@fnuecke fnuecke closed this as completed Apr 2, 2015
@KJA1582
Copy link
Contributor Author

KJA1582 commented Apr 2, 2015

I call it an Issue since using the logging function, it clearly shows that it somehow gets to the point.

This OpenComputers.log.info("INIT FLAXBEARD") added behind the callback does get called.

@fnuecke
Copy link
Member

fnuecke commented Apr 2, 2015

Check your log, if it actually gets registered an instantiated, if anything is wrong with the implementation it should warn you about that in the log.

@fnuecke
Copy link
Member

fnuecke commented Apr 2, 2015

Also, just to make sure the computer isn't holding an old wrapper of the component, reboot it or re-place the adapter block.

Sorry, something went wrong.

@KJA1582
Copy link
Contributor Author

KJA1582 commented Apr 2, 2015

Replacing the actual block and reassigning the variable in lua doesn't do this??

Sorry, something went wrong.

@fnuecke
Copy link
Member

fnuecke commented Apr 2, 2015

Components are cached (for performance, very noticeable) by address, so there's a chance the GC didn't run, cleaning the weak entries from the cache, thus the old proxy being re-using.

Sorry, something went wrong.

@KJA1582
Copy link
Contributor Author

KJA1582 commented Apr 2, 2015

Aha. You were right. It now works as intended. Thanks again.

PS: I'm not very comfortable with IRC., nor did I ever use it before.

Sorry, something went wrong.

@fnuecke
Copy link
Member

fnuecke commented Apr 2, 2015

Great :-)

Consider registering on the forum then. The main reason I'd like to avoid the issue tracker being used for support is that I'd like to keep notifications on, to be able to quickly react to bugs; but don't want my inbox swarmed with questions, which can often be answered by others.

@KJA1582
Copy link
Contributor Author

KJA1582 commented Apr 2, 2015

I felt more of it beeing a bug though, but ok. Hope you might consider merging it once I'm comfy enough to call it somewhat complete.

@fnuecke
Copy link
Member

fnuecke commented Apr 2, 2015

Sure!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants