Errors with a simple net #4

Activity

1. forresto commented on May 30, 2014

   

   forresto

   on May 30, 2014

   Member

   More actions

   I'll update visualize to use the new version of the-graph (custom element) and klay (autolayout) next week. This should fix these issues.
2. forresto commented on Jun 2, 2014

   

   forresto

   on Jun 2, 2014

   Member

   More actions

   It looks like https://github.com/noflo/fbp doesn't parse P1 as a valid component name.

   POne(C1) OUT -> IN PTwo(C2)
   PTwo OUT -> IN PThree(C3)
   

   works.
3. forresto commented on Jun 2, 2014

   

   forresto

   on Jun 2, 2014

   Member

   More actions

   Actually,

   P1(C1) OUT -> IN P2(C2)
   P2() OUT -> IN P3(C3)
   

   and

   P1(C1) OUT -> IN p2(C2)
   p2 OUT -> IN P3(C3)
   

   work as well. @bergie something in the parser that keeps @oleksandr's second line (
   P2 OUT -> IN P3(C3)
   ) from working ?
4. jpaulm commented on Sep 23, 2014

   

   jpaulm

   on Sep 23, 2014

   More actions

   @oleksandr I just tried your original text, and got a message saying conn.src is undefined .

   Added [0] after the OUT in the 2nd line, and got edges.forEach is not a function . !!!
5. bergie commented on Sep 23, 2014

   

   bergie

   on Sep 23, 2014

   Member

   More actions

   Sounds like a bug in the .fbp parser. I'll transfer that example to a unit test a bit later
6. jpaulm commented on Oct 2, 2014

   

   jpaulm

   on Oct 2, 2014

   More actions

   @bergie Should this be posted under https://github.com/noflo/fbp/issues ? If so, we could post it there and close this one.
7. oleksandr commented on Oct 5, 2014

   

   oleksandr

   on Oct 5, 2014

   Author

   More actions

   @bergie In the Go's version of FBP parser using PEG I've noticed that order of expressions in the grammar matters :)