Skip to content

Integer events seems to be messed up #76

Open
@Jaytheway

Description

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions