add a "box group options" feature and events trigger like: if this happen - then do this

[diieg707]

Is your feature request related to a problem or use case?

FEATURE REQUEST:
add a "box group options" in box group context menu and inside this options window add event selectors like this:

TYPE dropdown
process
or box

the design inside this option window would be something like this:

on top is one event, on botton is another event

with this feature it would increase the interaction inside a box group.

Describe the solution you'd like

...

Describe alternatives you've considered

No response

[bastik-1001]

Is there a reason to limit your request to box groups?

For me, box groups are a way to organize things or just a visual representation of them having something in common. Your request should still work if something happens in box A, do something in box B, whenever or not they are in a group.

Did you think it would be too confusing if the user can pair up box A with any other box, like Z255?

It seems useful to have something you describe, it's just that I don't understand why sandboxes need to be grouped.

[diieg707]

Is there a reason to limit your request to box groups?

For me, box groups are a way to organize things or just a visual representation of them having something in common. Your request should still work if something happens in box A, do something in box B, whenever or not they are in a group.

Did you think it would be too confusing if the user can pair up box A with any other box, like Z255?

It seems useful to have something you describe, it's just that I don't understand why sandboxes need to be grouped.

The idea behind this (box group option) is to make (programs in boxes inside the group) and boxes within the group interact with each other.

your questions:
Your request should still work if something happens in box A, do something in box B, whenever or not they are in a group.

answer:
following the representation i did in this (box group option), is only showed boxes that are inside this group, if a box is removed from the group the selector in the option should be selected NOT FOUND OR NULL.

question 2
Did you think it would be too confusing if the user can pair up box A with any other box, like Z255?

the user can pair up any boxes, as long as they don't use this event trigger option it will continue as it is, it won't affect them

[DavidXanatos]

hehehe... that looks complicated, and it looks like a never ending story, add more events, add more triggers, i want to download a file from the internet on trigger a, I want to upload a file on trigger b, etc.....

How about leveraging the QJSEngine we are using for trouble shooting to add the ability to fully script sandbox behavior in a complex way, its more work to begin with but its infinitely flexible.

[diieg707]

hehehe... that looks complicated, and it looks like a never ending story, add more events, add more triggers, i want to download a file from the internet on trigger a, I want to upload a file on trigger b, etc.....

How about leveraging the QJSEngine we are using for trouble shooting to add the ability to fully script sandbox behavior in a complex way, its more work to begin with but its infinitely flexible.

responding to your first statement, there should be a checkmark saying which trigger event is the currently in use, only one event should be checked for use.

secondly, will this "leveraging the QJSEngine" thing make it possible to create event triggers inside a group? like i if something happens in (process [in given box] / box) something should be done in another (process [in given box] / box) - "all of this inside a group"

[DavidXanatos]

There will be no check boxes, no lists, just one large text field to write some java script code which will govern this operations.

[diieg707]

There will be no check boxes, no lists, just one large text field to write some java script code which will govern this operations.

that's good,