-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
C# Support #7
Comments
thanks for cutting this issue. I'll look further into this! since I have not personally tested the usage along with C#. |
hey came across this from the video; you should be able to use example: and if that's sound (which it should be enough), i tested grabbing the info out of it thusly: public static void Test () {
// instantiating a test node
GDScript readerScript = GD.Load<GDScript>("res://Src/Externals/EzDialogueReader.gd");
Node exampleNode = (Node)readerScript.New();
// setting up a quick lambda to ensure the custom resource retains its props
// this'd be whatever func you connected the signal to
Callable myCallable = Callable.From((Resource dialogueResponse) => {
GD.PrintT(
dialogueResponse.Get("text"),
dialogueResponse.Get("choices")
);
});
// doin' it (just setting up the signal to call our lambda)
exampleNode.Connect("dialogue_generated", myCallable);
exampleNode.Call("test_call");
} and the output: from there you can use something like There's some more info in these here: |
I'm using C# for my project, despite the addon being written in gdscript, and have been successful up until it comes time to implement the dialogue_generated signal, as it recognizes the
DialogueResponse
asVariant
type. This renders the output, as far as I can tell, non-functional.Is this intended behavior (meaning that the addon is incompatible with C#) or is it a bug? Are there any known workarounds or is a partial C# rewrite necessary to fix the issue?
It is my understanding that the purpose of this addon is to primarily function as a personal tool, and secondarily as a community tool, thus I don't see C# support being high on its priority list. Is there any framework for a potential C# support update being PR'ed to this repo?
The text was updated successfully, but these errors were encountered: