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.

Sign up for GitHub

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

Jump to bottom

MakePoint receives number, array but not "inline arrays" #12

Open
automata opened this issue Apr 29, 2014 · 4 comments
Open

MakePoint receives number, array but not "inline arrays" #12

automata opened this issue Apr 29, 2014 · 4 comments
Labels
bug question

Comments

@automata
Copy link
Member

MakeRange 0..10 => X MakePoint works as well 100 => X MakePoint but [0,50,100] => X MakePoint doesn't. Sounds that's ok on MakePoint.coffee. The same to arcs, rectangles and other "primatives".

How to support both number and array in inPorts/outPorts? It works checking inPorts/outPorts type but it's reflected on UI, right @forresto?
@automata automata changed the title MakePoint receives number, type:array but not inline arrays MakePoint receives number, array but not "inline arrays" Apr 29, 2014
@forresto
Copy link
Member

"Inline array" from node inspector, or JSON?

@forresto
Copy link
Member

With the node inspector we would have to hack noflo-ui to support multiple
types. But we should have a mechanism there for custom input widgets
anyhow. Especially point objects are a pain to type.

@automata
Copy link
Member Author

automata commented May 3, 2014

From the node inspector. Should we open an issue on noflo-ui about "custom input widgets"?

@forresto
Copy link
Member

forresto commented May 4, 2014

A larger question here: noflo/noflo-ui#184

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@automata @forresto