Details
-
Task
-
Resolution: Fixed
-
P2: Important
-
6.5
-
None
-
e6101e618 (dev), 1623c946d (dev), bf8c065c5 (dev), 1a523ef6c (6.4), dac3f2614 (6.5), caf65e564 (6.4), adaddf81b (6.5), 3b5aea849 (dev), 284347912 (6.5), a80d031a7 (6.4), 179cd8929 (6.5)
Description
Try to create MultiEffect as QQEM nodes & project. This could be helpful in many ways:
- Locate bugs and issues with QQEM and MultiEffect.
- Unify their API and behavior.
- Serve "MultiEffect would suit my use case, if it only [add any change or addition]" cases. So users would have clear starting point when they need something just a bit different than MultiEffect.
The API should match MultiEffect API as much as possible for easy transition. Consider adding this "CustomMultiEffect" into MultiEffect testbed.