f-flow icon indicating copy to clipboard operation
f-flow copied to clipboard

Foblex Flow - is an Angular library designed to simplify the creation and manipulation of dynamic flow. Provides components for flows, nodes, and connections, automating node manipulation and inter-no...

Results 32 f-flow issues
Sort by recently updated
recently updated
newest added

### Description Is there a way to disable multiple selection for nodes / groups ? ### Steps to Reproduce N/A ### Expected Result When user tries to select multiple nodes,...

help
completed

### Description Hi, I'm currently using the "Node from the Palette" feature to create new nodes, and I have two requests/issues: - When I drop a new node with the...

I have a externalItem similar to this, but instead of dragging the new item to a position in the canvas I want to click in the item and then click...

help
completed

## Description Added `fitToScreen(PointExtensions.initialize(50, 50), true)` example. I'm not sure but this detail is might be important newcomers. ## Type of change - [x] Documentation update ## Checklist: - [x]...

### Description If I use multiple flows on same page, dragging external item works only on first flow. There are few issues: - Dragging basically works also on second flow,...

bug

### Description I am not able to perform any click event on top of the node, Pointer events are not working. ### Steps to Reproduce I am using the following...

not reproduced

### Description To group multiple nodes together, Foblex Flow provides the concept of fGroup. However, in my current data structure, I have: ``` { "nodes": [], "groups": [], "connections": []...

help

### Description I am using fExternalItem drag-and-drop functionality from example: https://flow.foblex.com/examples/f-visual-programming-flow But I opened vp-flow component in full screen mode: ![Image](https://github.com/user-attachments/assets/b501fbf3-3d45-4430-884b-856f76a20e96) after it I am not longer see the placeholder...

bug
completed

### Description **"It would be great to have a feature that allows us to limit connection types. For example, an output could have a property like `fNodeOutput = ["tool", "input_text"]`,...

feature request
not planned