-
New Feature
-
Resolution: Done
-
Major
-
0.8.0.Final
-
None
-
None
-
NEW
-
NEW
UpdatedLockStatusEvent only includes the "lock" status and whether the "lock" is owned by the current User. This works well with the single-document interface based editors we have (to date) since the event is only raised by the LockManager associated with the "visible" Editor and hence associated event-sinks (only BasicFileMenuBuilderImpl at the time of writing) don't care about the locked "path" since they assume if they receive the event they must be "visible". Event-sinks on "invisible" (hidden) editors don't really care what the lock status is - and indeed erroneously handle UpdatedLockStatusEvents - as they are refreshed "onFocus".
With a multiple-document interface I have a different LockManager per "document" however all documents are "visible" and hence I can have multiple UpdatedLockStatusEvents raised. I need to be able to disambiguate between changes in locks for different paths.