file selector callbacks
The callback functions passed as arguments to the “openFileSelector”
emission should always be executed, i.e. even if the selector is
closed without any selection.
This feature/bug is crucial for situations in which a selection of some
path is mandatory in order for an extension to proceed
(e.g. the pxl browser must have given a proper path in order to work; an
operation without any is still possible by closing the selector and not
selecting anything which eventually leads to errors. The easiest
solution is that the selector executes the callbacks at each “close”).
P.S. - Target version is 1.0.1 because the pxl browser, which might be installed this week, will depend on it.
- If this fix is unwanted or too time-consuming (dT>~ minutes), this should not be a show stopper and/or I will implement a different but rather ugly solution to my problem.
(from redmine: issue id 2021, created on 2014-12-15 by root, closed on 2015-10-08)
- Changesets:
- Revision 2348 by Fabian Heidemann on 2015-10-08T14:44:28Z:
[fileselector] fix #2021: the file selector always fires the callback. The first argument is null, if it is just closed- Revision 2348 by Fabian Heidemann on 2015-10-08T14:44:28Z:
[fileselector] fix #2021: the file selector always fires the callback. The first argument is null, if it is just closed