diff options
| author | Patrick Monnerat <[email protected]> | 2019-02-17 17:36:11 +0100 |
|---|---|---|
| committer | raveit65 <[email protected]> | 2019-03-31 12:30:00 +0200 |
| commit | 1d5a8b7aa497c6d3d3257887f95832eda397347c (patch) | |
| tree | 65471eef27198f9eeb9cf5c3c7f79fb05c13a729 /po | |
| parent | 75906bebc8b7ce8adef7040d5bebde8ff7f59090 (diff) | |
| download | python-caja-1d5a8b7aa497c6d3d3257887f95832eda397347c.tar.bz2 python-caja-1d5a8b7aa497c6d3d3257887f95832eda397347c.tar.xz | |
Make Caja.OperationHandle usable.
The Caja.OperationHandle.handle property is added: this gives access to the
effective handle taking the form of a non-zero signed integer that can be
stored in a void pointer. Trying to set this property with an invalid value
raises an exception.
Upon update_file_info_full call, the new Caja.OperationHandle is preset with
a "unique" non-null value generated from an atomic counter. When the python
method returns, the handle value is transmitted to Caja whatever it is:
this fixes the problem of Caja expecting a non-null handle when
CAJA_OPERATION_IN_PROGRESS is returned.
Ref: https://github.com/mate-desktop/python-caja/issues/36
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions