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

Integer events seems to be messed up #76

Open
Jaytheway opened this issue Oct 6, 2021 · 0 comments
Open

Integer events seems to be messed up #76

Jaytheway opened this issue Oct 6, 2021 · 0 comments

Comments

@Jaytheway
Copy link

If you have a top graph input event of type int connected to a member processor input event of type int, the values passed in are not exactly what you'd expect.

dummy event is an input of a member processor, to which the main graph's input is connected. Here's the console output of the values from 0 to 10 sent from the Main graph to the connected member processor input event:

image

Main graph event:

event int Dummy [[name: "main graph", min: 0, max: 10, init: 5, step: 1]];

Dummy processor:

processor DummyProc
{
	input event int DummyEvent [[min: 0, max: 10, init: 4]];
	output event int DummyOut;

	event DummyEvent(int i)
	{
		console << "dummy event " << i <<"\n";
	}
}

Another small point, all of the events of the Main graph are automatically fired right after the patch compilation, I'm assuming it is to initialize the init values, even if the init value is not specified in annotations?

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

1 participant