-
Type: Improvement
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Core, Events / Works
Listeners reacting of documentModified can get fired several times or even create loops.
The typical problem is a Studio listener fired indirectly by a built-in listener like the one computing pictures, thumbs, video conversions ...
Inside the platform we manage that via direct exclusion but :
- it can not scale : it is already a mess
- external developers and Studio users can not do that anyway
1.
|
Add information about source EventListener inside the EventContext | Open | Unassigned | |
2.
|
Give direct visibility about modified fields | Open | Unassigned |